From: harry eaton <haceaton@aplcomm.jhuapl.edu>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: Where do we go from here?
Date: Tue, 16 Mar 1999 17:38:22 -0500 [thread overview]
Message-ID: <36EEDD5E.AE93A13@aplcomm.jhuapl.edu> (raw)
In-Reply-To: 199903161932.NAA24349@lists.linuxppc.org
L. S. wrote:
> With Apple Computers coming into the arena of Linux(PPC) territory, and since
> LinuxPPC is playing on Apple's territory, and since Power Macintoshes--unlike
> IBM compatibles--are closed systems, what will happen when Apple changes
> hardware architectures to a degree that the specifications for Apple hardware
> are out of reach for LinuxPPC developers or reverse-enginneered so late that
> Apple is miles ahead with their Mach/BSD/Mac OS?
Well lets see. That was the position we were in prior to today, and I don't
think Apple is exactly miles ahead. Ahead yes, but not by miles. Today Steve
Jobs broke down and actually revealed some hardware info (or near as I can tell,
there's new revelations there). I'm talking here about:
http://www.publicsource.apple.com/ Get it while it lasts (I'm not talking about
using this code, just looking at it for register bit definitions etc.). Hurry
hurry, before Apple does one of its famous reversals.
The good stuff seems to mostly be in the file with the link name "kernel".
h.
[[ 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. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-03-16 22:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-16 19:33 Where do we go from here? L. S.
1999-03-16 21:27 ` Hollis R Blanchard
1999-03-16 21:31 ` Cort Dougan
1999-03-16 22:38 ` harry eaton [this message]
1999-03-16 23:39 ` Peter Bierman
1999-03-17 3:31 ` Arun Rodrigues
-- strict thread matches above, loose matches on Subject: below --
1999-03-16 23:11 Michael Millsap
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=36EEDD5E.AE93A13@aplcomm.jhuapl.edu \
--to=haceaton@aplcomm.jhuapl.edu \
--cc=linuxppc-dev@lists.linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).