linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: LinuxPPC-Dev Liste <linuxppc-dev@lists.linuxppc.org>
Cc: Paul Mackerras <paulus@cs.anu.edu.au>
Subject: Linux vs. new PowerMacs
Date: Wed, 6 Jan 1999 15:45:51 +0100	[thread overview]
Message-ID: <19990106154551.031473@mail.mipsys.com> (raw)


For those who haven't yet read the developer note of the new machines,
here are some infos that may be of interest to get Linux running on those
new machines:

 - Grackle is still here. It's externally clocked at 66MHz using an Apple
custom-made arbitrer, but this should be configured once for all by OF,
so I don't think we have to worry about that. It's driving the
66MHz/32bits graphic PCI slot and the bridge below.

 - There's a PCI-PCI bridge between the 66MHz bus and the 33MHz 32/64
bits bus. It looks like the data patch from the CPU to this PCI is 32
bits wide. The bridge is a DEC/Intel 21154 connected to Grackle.

 - The main IC is still Paddington (like the iMac) with a slightly
improved bmac+, according to Apple it's software compatible and more
efficient. The modem is on it's SCC channel A, so I guess we should be
able to support it, it's ATA channels (ATA-3) drive the CDROM and the
ZIP, VIA and CUDA are there too for I2C, power and ADB, the NVRAM looks
similar to what it was in the iMac and the Sound is also Burgundy which
is, I think, yet another AWACS derivative.

 - There's a new PCI-based UltraDMA/33 (ATA/ATAPI-4) controller. I've not
seen any infos or spec about this, I don't know if it's a custom Apple
chip or a standard one, but there are great chances that this is a
standard one. We should be able to use it as-is in PIO mode like any ATA
controller, DMA may be a little bit more tricky.

 - FireWire is a standard PCI-based chip

 - USB is a standard PCI-based chip, I guess it's similar to the one used
in the iMac but I have not seen any more infos about it in the dev. note.

 - Video: The new ATI will probably not be supported "as-is" by atyfb,
this will probably be the "hard part". We can still use "ofonly" video in
the meantime.

Looks like there are great chances that we get Linux running on the
machine quite quickly, isn't it ? ;-)

-- 
           E-Mail: <mailto:bh40@calva.net>
BenH.      Web   : <http://calvaweb.calvacom.fr/bh40/>





[[ 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@lists.linuxppc.org ]]

             reply	other threads:[~1999-01-06 14:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-01-06 14:45 Benjamin Herrenschmidt [this message]
1999-01-06 16:08 ` Linux vs. new PowerMacs Geert Uytterhoeven
1999-01-07  3:25 ` Jason haas

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=19990106154551.031473@mail.mipsys.com \
    --to=bh40@calva.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paulus@cs.anu.edu.au \
    /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).