Porting to NuBus PowerMacs

[David A. Gatwood]

On Tue, 12 Jan 1999, a sun wrote:

> heh. am i correct in assuming then that just using memory barriers
> just won't cut it for a certain device that seems to have a bunch of
> delay()'s sprinkled throughout it? strangely, this same piece of
> hardware seems to be necessary to get the newer tech g3 extension and
> the mklinux booter happy... any insights there?

Actually, on looking at it, there is the use of memory barriers.  The real
change is in the code for the memory barriers (and possibly in other
places, too... not certain).  See 

.../osfmk/src/mach_kernel/ppc/proc_reg.h:440

in the MkLinux sources.  :-)


Later,
David

David A. Gatwood                         Visit globegate's internet
dgatwood at globegate.utm.edu                  talker, Deep Space 36
http://globegate.utm.edu                telnet globegate.utm.edu:9624

-----BEGIN GEEK CODE BLOCK-----
Version 3.1
GCS/CC/FA/H/L/MC/M/MU/PA/TW d-@ s:>- a-- C++ ++>$ UBLAS*++ ++>$
P+?>$ L++ +>$ !E--- W++ +>$ N++(++ +)>++ +$ !o? K-? !w--- !O
M++>$ !V-- PS+>$ !PE- Y+>$ PGP+>$ t++ +>$ 5+>++ ++$ !X- !R tv+>$
b++>$ !DI !D- G++(++ +)>$ e>++ ++ h--! r--- !y-
------END GEEK CODE BLOCK------


[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to  Cc linuxppc-dev  if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request at lists.linuxppc.org ]]