🚀 go-pugleaf

Nevin ":-]" Liber (nevin@CS.Arizona.EDU) wrote:
: In article <3vge4m$2o2@news.onramp.net>, johnmm@onramp.net wrote:

: > If you have access to real information about the internals of a Mac,
: > would you be so kind as to tell the MAC-Linux team where you found it?
: > They tried and failed.  Perhaps you don't understand just what level of
: > documentation is needed to implement an entire OS, not just a device
: > driver into MAC-OS.
: > 
: > : "Wah... I wanna write my own drivers!"  Of all the Mac programmers I
: > : have met or know... there are incredibly few cases that they have had
: > : need to access hardware directly.

The linux team does need to access the hardware directly.  

: Such as??  I have yet to see anyone post specific questions (although
: groups like comp.sys.mac.system would probably be more appropriate).  All
: I see is a bit of whining about how Apple won't just give away all its
: source code.

It's not just that.  The linux team needs the info on apple's asics 
(apple's proprietary chips) and apple wont give them the info.  This 
should all be moot when HRP machines ship.  I just hope apple dosent back 
out of the HRP standard but it wouldnt surprise me.  HAL in copland will 
make it very easy to set up the MacOS on HRP machines.


--


*******************************************************************************
Scott L. Parrish        Graduate Student
Dept. Of Zoology        parrisc@mail.auburn.edu         WAR EAGLE!
Auburn University       parrisc@freenet.fsu.edu, scottp@iris.ag.auburn.edu
*******************************************************************************