From: Benjamin Herrenschmidt <bh40@calva.net>
To: Christian.Bauer@uni-mainz.de
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Endianess problems in linuxppc kernel
Date: Thu, 29 Apr 1999 12:41:56 +0200 [thread overview]
Message-ID: <19990429124156.011678@mail.mipsys.com> (raw)
In-Reply-To: <199904281818.UAA01127@student.physik.uni-mainz.de>
On Wed, Apr 28, 1999, Christian Bauer <Christian.Bauer@uni-mainz.de> wrote:
>CC: linuxppc-dev@lists.linuxppc.org
>----------
>
>>Do you know which Apple chip is this, so it can be added to the pciutils
>>database?
>
>The device tree has this to say:
>
>Devices:device-tree:bandit:ohare
This is Ohare, one of the evolutions of Apple's Grand Central.
Some Device IDs I know are:
0x0002 for Grand Central
0x0007 for Ohare
0x0010 for Heathrow mac-io (PowerBook G3 Series, PowerMac G3s).
0x0017 for Paddington mac-io (iMac, PowerMac G3s).
>Maybe the host bridge also does byte swapping on the frame buffer??
Hum, the bridge is a bandit, I don't think bandit can swap anything. But
you may be using the wrong frame buffer apperture.
--
Perso. e-mail: <mailto:bh40@calva.net>
Work e-mail: <mailto:benh@misys.com>
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. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-04-29 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-28 18:13 Endianess problems in linuxppc kernel Christian Bauer
1999-04-29 10:41 ` Benjamin Herrenschmidt [this message]
1999-04-29 17:24 ` Ryuichi Oikawa
-- strict thread matches above, loose matches on Subject: below --
1999-04-28 19:23 Christian Bauer
1999-04-28 9:56 Christian Bauer
1999-04-28 11:11 ` Geert Uytterhoeven
1999-04-28 12:21 ` Paul Mackerras
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=19990429124156.011678@mail.mipsys.com \
--to=bh40@calva.net \
--cc=Christian.Bauer@uni-mainz.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.