All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Stefan Reinauer <stepan@suse.de>
Cc: Sven Luther <sven.luther@wanadoo.fr>,
	Jon Smirl <jonsmirl@yahoo.com>,
	Michel DXnzer <michel@daenzer.net>,
	Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: Problem with radeon new ROM probe code
Date: Thu, 25 Sep 2003 15:41:27 +0200	[thread overview]
Message-ID: <1064497287.694.8.camel@gaston> (raw)
In-Reply-To: <20030925121025.GA30733@suse.de>


> Whether it's an Open Firmware card or not can be read from the PCI
> headers stored in the ROM. Check the romheaders utility from OpenBIOS
> CVS ( http://www.openbios.org/ )
> 
> Look at the code here:
> http://cvs.openbios.org/cgi-dom/viewcvs.cgi/utils/romheaders.c?rev=1.2&content-type=text/vnd.viewcvs-markup
> 
> The program prints whether the rom is OpenFirmware, x86 or HP PA-Risc.
> Note that graphics cards can theoretically contain ROM images for both
> x86 and OF in one chip.

Yup, "Mac" cards can contain in theory both OF and x86 BIOS drivers, though
I yet have to find a vendor doing that....

Thanks for the pointers to code, I'll dig that out.

Regards,
Ben.




-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

      reply	other threads:[~2003-09-25 13:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-24 12:06 Problem with radeon new ROM probe code Benjamin Herrenschmidt
2003-09-24 15:18 ` Michel Dänzer
2003-09-24 17:44   ` Benjamin Herrenschmidt
     [not found]     ` <20030924181257.78090.qmail@web14914.mail.yahoo.com>
2003-09-25  5:39       ` Sven Luther
2003-09-25 12:10         ` Stefan Reinauer
2003-09-25 13:41           ` Benjamin Herrenschmidt [this message]

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=1064497287.694.8.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=jonsmirl@yahoo.com \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=michel@daenzer.net \
    --cc=stepan@suse.de \
    --cc=sven.luther@wanadoo.fr \
    /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.