On Thu, 22 Aug 2013, Scott Holder wrote:
>
> The problem I'm having now is getting the mouse and keyboard to work.
Issues with ADB devices in X11 on m68k Macs should be no different on
linux-ppc on Old World Macs (i.e. pre-USB). So you could try searching or
asking on a Debian/PPC mailing li
On 8/21/2013 6:34 AM, Finn Thain wrote:
X11 worked on macs back when I was testing etch-m68k. The pixel formats
are not the weird ones found on ataris. The only Xorg driver available is
fbdev.
Not having any trouble with graphics. It's working about the same as it
did before. I don't have muc
Geert Uytterhoeven dixit:
>Anyone who has tried this on real iron? I haven't (on Amiga).
FWIW, that patch was in Debian linux-image-3.10-2-m68k
so everyone who successfully booted that counts.
Scott Holder booted it on his Macintosh AFAIR.
bye,
//mirabilos
--
«MyISAM tables -will- get corrupte
On Tue, Aug 13, 2013 at 9:57 AM, Michael Schmitz
wrote:
>> • this interrupt patch
>
> Having revived my Falcon, I should be in a position to test these.
Anyone who has tried this on real iron? I haven't (on Amiga).
The merge window may open this weekend (but I wouldn't be surprised
if there was
On Thu, Aug 22, 2013 at 3:37 PM, Joseph S. Myers
wrote:
> On Thu, 22 Aug 2013, Geert Uytterhoeven wrote:
>
>> > The vDSO support has been there in glibc ever since the NPTL port was
>> > first added. I've no idea why the kernel changes still haven't gone in.
>>
>> I didn't know that. Seems to be
On Thu, 22 Aug 2013, Geert Uytterhoeven wrote:
> > The vDSO support has been there in glibc ever since the NPTL port was
> > first added. I've no idea why the kernel changes still haven't gone in.
>
> I didn't know that. Seems to be recent work, cfr.
> https://github.com/Xilinx/glibc/blob/master
On Thu, Aug 22, 2013 at 1:44 PM, Joseph S. Myers
wrote:
> On Thu, 22 Aug 2013, Finn Thain wrote:
>> Losing a register also hurts performance. Someone suggested moving
>> get/set_thread_area to a VDSO (as well as the atomic ops). As I understand
>> it, this need not break the ABI and should be fast
Finn Thain dixit:
>Probably adding syscalls could fix the 32-bit time_t without breaking
>anything (given symbol versioning in libc).
No. You need to rebuild everything that depends on libc, too.
>Fixing everything (as in a new ABI) means simultaneous changes to kernel,
[…]
Yes, I know. Which i
On Thu, 22 Aug 2013, Finn Thain wrote:
> Losing a register also hurts performance. Someone suggested moving
> get/set_thread_area to a VDSO (as well as the atomic ops). As I understand
> it, this need not break the ABI and should be faster than the TLS system
> calls.
The vDSO support has been
On Thu, 22 Aug 2013, Thorsten Glaser wrote:
> Finn Thain dixit:
>
> we could do other sensible things (64-bit time_t, register passing of
> arguments, other legacy cleanup).
Probably adding syscalls could fix the 32-bit time_t without breaking
anything (given symbol versioning in libc).
Fixi
Finn Thain dixit:
>Losing a register also hurts performance. Someone suggested moving
Right, but at least m68k is not as register-starved as i386.
And when changing the ABI “anyway”, we could do other sensible
things (64-bit time_t, register passing of arguments, other
legacy cleanup).
>get/set_
11 matches
Mail list logo
