From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jesse Barnes <jbarnes@sgi.com>
Cc: Jon Smirl <jonsmirl@gmail.com>,
fbdev <linux-fbdev-devel@lists.sourceforge.net>
Subject: Re: [PATCH] Provide control of active VGA device on PCI systems
Date: Wed, 23 Feb 2005 07:57:47 +1100 [thread overview]
Message-ID: <1109105867.5411.128.camel@gaston> (raw)
In-Reply-To: <200502221050.43534.jbarnes@sgi.com>
On Tue, 2005-02-22 at 10:50 -0800, Jesse Barnes wrote:
> Nice, if this is combined with Ben's suggestion of using a firmware loader
> type model to deal with POSTing, it seems like we're in pretty good shape.
> Can you add documentation for this API to
> Documentation/filesystems/sysfs-<foo>.txt (maybe the pci file or a new file)
> so that userspace people will be able to figure out how to use it?
>
> Also, how does one know if a card is 'primary' or not? I.e. some BIOSes will
> POST all cards, some will POST only one, and some will POST none...
Well, that's something we need to figure out... While I do think the
POSTing must be under driver control, as I explained, there is still
that nasty notion of who has the stuff at 0xc0000 ... and if your
firmware runs the x86 BIOS but doesn't keep the shadow around, then you
are toast with a good deal of laptop chips.
The problem is that on some cards (ATIs for example), the BIOS will
modify the image in RAM at c0000 and will put in there various infos,
like panel type, PLL infos, etc... that can't always be obtained from
the "hard" ROM (especially the panel infos). The driver (raeonfb or X,
strace X and see it mmap'ing /dev/mem at c0000...) need those things.
Ben.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-22 20:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 5:50 [PATCH] Provide control of active VGA device on PCI systems Jon Smirl
2005-02-20 7:07 ` Jon Smirl
2005-02-22 18:50 ` Jesse Barnes
2005-02-22 20:57 ` Benjamin Herrenschmidt [this message]
2005-02-22 21:02 ` Jesse Barnes
2005-02-22 21:27 ` Benjamin Herrenschmidt
2005-02-22 21:42 ` Jon Smirl
2005-02-20 8:23 ` Benjamin Herrenschmidt
2005-02-20 16:35 ` Jon Smirl
2005-02-22 4:07 ` James Simmons
2005-02-24 6:14 ` Jon Smirl
2005-02-22 4:13 ` James Simmons
2005-02-22 4:47 ` Jon Smirl
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=1109105867.5411.128.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=jbarnes@sgi.com \
--cc=jonsmirl@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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).