public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Burgess <jburgess@uklinux.net>
To: mmurray@deepthought.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: accessing ROM on Rage 128 chips in aty128fb
Date: Mon, 31 Mar 2003 19:17:16 +0100	[thread overview]
Message-ID: <3E88862C.10205@uklinux.net> (raw)

  Martin Murray (mmurray@deepthought.org) wrote:

 > Why does the linux PCI code not set up a mapping for the ROM
 > automatically?

It expects the BIOS to do it. You can force it to try with the option 
"pci=rom"

Assuming this is the active grahpics card, then you should be able to 
access the rom via the legacy VGA address range 0xc0000...0xc7fff which 
should be shown in /proc/iomem.

Try:
dd if=/dev/mem skip=768 bs=1k | od -x | more

In these days of integrated peripherals the graphics bios might not even 
be attached to the VGA controller. The VGA device in my i810 system 
doesn't even report an expansion rom.

 > and found that the X driver maps the ROM through configuration
 > space.

I'm fairly sure the XFree code falls back to the VGA region as well if 
it can't find anything else. I think this is true on my machine, the X 
log says:
... Primary V_BIOS Segment is 0xc000

	Jon




             reply	other threads:[~2003-03-31 18:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-31 18:17 Jon Burgess [this message]
2003-04-02 17:21 ` accessing ROM on Rage 128 chips in aty128fb Martin Murray
2003-04-02 17:42   ` Jon Burgess
  -- strict thread matches above, loose matches on Subject: below --
2003-03-30 23:59 Martin Murray

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=3E88862C.10205@uklinux.net \
    --to=jburgess@uklinux.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmurray@deepthought.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