Porting to NuBus PowerMacs
    a sun 
    asun at saul7.u.washington.edu
       
    Thu Jan 14 15:09:07 EST 1999
    
    
  
   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.  :-)
oh my. i hadn't noticed that. thanks for pointing it out to me. i
guess a plain eieio() is sometimes not good enough... no doubt, the
designers of certain unmentionable devices were being directed by some
cosmic purpose that we, the uninitiated, can only vaguely envision and
hope to understand.
luckily, my trusty g3 upgrade card handily curtails my pursuit into
the ineffable nature of such visionaries. i guess i'll have to add a
CONFIG_601 to deal with certain "third-party" devices though. that
way, we can have just as much fun as the other architectures with
processor-specific tweaks.
-a
asun at u.washington.edu
[[ 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 ]]
    
    
More information about the Linuxppc-dev
mailing list