the CD image. I haven't looked
at recent images, but I know in the past the boot process was
different on CD compared to after the install.
Brad Boyer
f...@allandria.com
so shouldn't it be possible to only run this code when the appropriate
entries are present in the right data structures?
I didn't look at a lot of the other serial drivers, but some other mac
drivers have recently been updated to no longer have MACH_IS_MAC checks
due to being converted to platform drivers.
Brad Boyer
b...@allandria.com
private? I seem to see quite a bit of that as well.
Thank you for your advice.
Brad Boyer
f...@allandria.com
d this because it was G3/G4 only for a while
until they rewrote it to not use the little-endian mode.
Brad Boyer
f...@allandria.com
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
This driver is for m68k based Macintosh systems, not PowerPC based ones. I'm
copying the linux-m68k list on this reply so it is seen there as well.
Brad Boyer
f...@allandria.com
On Tue, Mar 09, 2010 at 01:46:20PM -0800, Michael Beardsworth wrote:
> From: Michael Bea
lly it would enable better user-space
device detection as well.
I got the framework built against an older kernel, but it wasn't enough
to be useful at that point. This set of patches could help quite a bit.
Brad Boyer
f...@allandria.com
___
ctually sleeping.
I don't think this is the most likely explanation since you said you
can kill your process, but I thought I should mention it.
Brad Boyer
f...@allandria.com
___
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
t you
get if the lookup fails on a name returned by a readdir. I suspect
that creating hard links is failing in some way. In particular, the
"hidden dir" mentioned in the log is used to save the real files for
hard links.
As a quick explanation, HFS+ doesn't have a real concept of ha
. using m or Z with a memory address. I tried replacing m/Z but no change
> Is there some guideline ?
> gcc documentation says Z is obsolete. Is m/Z replaceable ?
No idea. I don't remember ever seeing 'Z' used in anything. Maybe somebody
else remembers what it used to mean.
he
moment. They also are all custom chips that wouldn't be used anywhere
else. The other thing we need to keep in mind is that if we do it right
we can share drivers across m68k and powerpc in some cases. I imagine
some of the embedded powerpc boards are using chips that are common in
other
f_parse_and_map(). It takes a device node and index into
the interrupt list for that device and gives a virtual IRQ number.
Brad Boyer
f...@allandria.com
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
u think that's not realistic.
It seems to me that an interrupt per-byte (which this design would
imply on the older DMA engines) would make the DMA less useful.
Brad Boyer
[EMAIL PROTECTED]
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
> > 604e.
>
> The BeBox had a dual 603.
I remember going to a talk by some of the Be engineers, and I think they
said that the 603 had terrible SMP performance. My understanding was that
Motorola recommended the 604 for SMP configurations but the 603 was much
cheaper and mostly work
end up being in multiple files, it's more fragile to change
what is mapped in these blocks.
Brad Boyer
[EMAIL PROTECTED]
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
While I'm wasting your time, I picked up an ADB infrared wireless
> keyboard. I think it works. But not under Linux. Should it?
If it acts like a normal ADB keyboard, it should work. Does it need a
special driver with the MacOS? If so, then it
e older PMU chips. Some
of them are very timing sensitive, and sleep in particular is basically
a pile of steps that got hacked until they worked on older systems.
Brad Boyer
[EMAIL PROTECTED]
___
Linuxppc-dev mailing list
Linuxppc-dev
s called sys_read. You
should be able to find it in fs/read_write.c. Other system call
implementations are scattered around to be with code related to that
call. Most of the file related ones can be found someplace under the
fs directory.
Brad Boyer
.c is m68k only,
so you should probably leave that alone as well. It probably doesn't need
that header, but the change should really come from the 68k side of things.
Brad Boyer
[EMAIL PROTECTED]
___
Linuxppc-dev mailing list
Linuxppc-dev@ozlabs.org
https://ozlabs.org/mailman/listinfo/linuxppc-dev
18 matches
Mail list logo