linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: matroxfb, anybody? (More details...)
Date: Mon, 1 Feb 1999 16:55:38 +0100	[thread overview]
Message-ID: <19990201165538.009774@mail.mipsys.com> (raw)


On Mon, Feb 1, 1999, Geert Uytterhoeven
<Geert.Uytterhoeven@cs.kuleuven.ac.be> wrote:

>Since BootX creates a fake OF device tree, I suspect it to appear in the
tree.
>Can you use your Mystique under MacOS? This is of course a prerequisite for
>BootX seeing your board.

OF in the machine's ROM (not the card's ROM) should make _any_ PCI board
visible provided that it contains correct config-space registers with a
vendorID and a deviceID, which is required for all PCI cards anyway. The
board itself can optionally contain OF code which can then change things
in the device-tree but you will (should) always at least have a device
tree entry, even if you have no OF code on the board.

BootX will make the fake OF tree from MacOS Name Registry, which is
itself a translated version of OF tree (plus or minus a couple of things
since MacOS drivers can change it).

However, I've read somewhere that there is actually a difference between
Matrox boards with and without OF code: the OF code will set the board to
use big-endian pixels. It may also change a couple of other things, so
you can not rely on the state of the board at driver initialisation. You
will probably also have differences with or without Gabriel PReP
bootloader since it will be able to run any x86 bios code that lives here.


-- 
           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-02-01 15:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-02-01 15:55 Benjamin Herrenschmidt [this message]
1999-02-01 16:25 ` matroxfb, anybody? (More details...) Geert Uytterhoeven
1999-02-02 15:10   ` Owen Waller
1999-02-02 20:03     ` Geert Uytterhoeven
  -- strict thread matches above, loose matches on Subject: below --
1999-02-02 12:53 Petr Vandrovec Ing. VTEI
1999-02-04  5:49 ` dhiltgen@toocool.calpoly.edu
1999-02-04 22:52   ` Takashi Oe
1999-02-01 18:32 Petr Vandrovec Ing. VTEI
1999-02-01 17:38 Petr Vandrovec Ing. VTEI
1999-02-01 17:15 ` Geert Uytterhoeven
1999-02-01 20:32   ` Owen Waller
1999-02-01 12:51 Petr Vandrovec Ing. VTEI
1999-02-01 12:08 ` Geert Uytterhoeven
1999-02-01 16:30   ` Owen Waller
1999-02-01 16:18     ` Geert Uytterhoeven
1999-02-01 19:14     ` Benjamin Herrenschmidt
1999-02-01 20:30       ` Owen Waller
1999-02-02 15:04       ` Owen Waller
1999-02-01 10:34 Petr Vandrovec Ing. VTEI
1999-02-01 10:04 ` Geert Uytterhoeven
1999-02-01 12:35 ` Owen Waller
1999-02-02 10:37   ` dhiltgen@toocool.calpoly.edu
1999-01-30 10:00 matroxfb, anybody? dhiltgen@toocool.calpoly.edu
1999-01-30 15:32 ` Owen Waller
1999-01-30 23:34   ` matroxfb, anybody? (More details...) dhiltgen@toocool.calpoly.edu
1999-01-31  9:38     ` Gerd Knorr
1999-01-31 14:24       ` Geert Uytterhoeven
1999-02-06 15:22         ` Gerd Knorr
1999-01-31 14:36     ` Geert Uytterhoeven

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=19990201165538.009774@mail.mipsys.com \
    --to=bh40@calva.net \
    --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).