From: Vojtech Pavlik <vojtech@suse.cz>
To: Jon Smirl <jonsmirl@yahoo.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Jesse Barnes <jbarnes@engr.sgi.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Torrey Hoffman <thoffman@arnor.net>,
lkml <linux-kernel@vger.kernel.org>,
Alex Romosan <romosan@sycorax.lbl.gov>,
Dave Airlie <airlied@linux.ie>
Subject: Re: legacy VGA device requirements (was: Exposing ROM's though sysfs)
Date: Fri, 20 Aug 2004 06:53:57 +0200 [thread overview]
Message-ID: <20040820045356.GA594@ucw.cz> (raw)
In-Reply-To: <20040820044635.42969.qmail@web14925.mail.yahoo.com>
On Thu, Aug 19, 2004 at 09:46:35PM -0700, Jon Smirl wrote:
> Attached is a real world reason why we need a VGA control device.
> VesaFB loads and marks the VGA screen region as reserved. The driver
> does not attach to any device.
>
> My new radeon DRM driver load and says no one is using the radeon card,
> so it can drive it. Radeon loads and fails. It can attach the PCI
> device but it can't reserve the memory block.
>
> The short term fix for this is to make VesaFB aware of the PCI ROM
> patch. The PCI ROM patch makes it possible to identify the boot video
> device. Once VesaFB can identify the boot video device it can properly
> attach itself to both the device and memory. Then DRM radeon loads
> after vesafb it will find the PCI device already has a driver attached
> and revert back into stealth compatibility mode.
Well, the stealth compatibility mode is even uglier than VesaFB not
claiming the PCI device, so I don't think it's really worth it for this
reason.
You can just as well enable the stealth mode if you can't get the
resources.
> Long term we need the vga control device and a unified DRM/fbdev.
We really need that. And we need it to be able to kick VESAfb out using
sysfs when it loads. For that you'll need to make VESAfb grab the VGA
PCI device.
> The immediate work around is to use the radeonfb driver instead of
> vesafb. The radeonfb driver marks the PCI device in use and triggers
> stealth mode in radeon.
--
Vojtech Pavlik
SuSE Labs, SuSE CR
next prev parent reply other threads:[~2004-08-20 4:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1091207136.2762.181.camel@rohan.arnor.net>
2004-07-30 17:24 ` Exposing ROM's though sysfs Jon Smirl
2004-07-30 19:14 ` Vojtech Pavlik
2004-07-30 20:26 ` Jesse Barnes
2004-07-30 22:36 ` Alan Cox
2004-08-03 21:41 ` Benjamin Herrenschmidt
2004-08-04 0:55 ` Jesse Barnes
2004-08-04 0:59 ` Benjamin Herrenschmidt
2004-08-04 1:18 ` legacy VGA device requirements (was: Exposing ROM's though sysfs) Jesse Barnes
2004-08-13 15:53 ` Jon Smirl
2004-08-13 16:11 ` Jesse Barnes
2004-08-13 21:45 ` Alan Cox
2004-08-13 21:43 ` Alan Cox
2004-08-13 23:56 ` Jon Smirl
2004-08-14 15:27 ` Alan Cox
2004-08-14 16:36 ` Jon Smirl
2004-08-20 4:46 ` Jon Smirl
2004-08-20 4:53 ` Vojtech Pavlik [this message]
2004-08-20 5:03 ` Jon Smirl
2004-08-20 11:14 ` Alan Cox
2004-08-04 1:37 ` Exposing ROM's though sysfs Jon Smirl
2004-08-04 1:57 ` Benjamin Herrenschmidt
2004-08-04 2:16 ` Jesse Barnes
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=20040820045356.GA594@ucw.cz \
--to=vojtech@suse.cz \
--cc=airlied@linux.ie \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.org \
--cc=jbarnes@engr.sgi.com \
--cc=jonsmirl@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=romosan@sycorax.lbl.gov \
--cc=thoffman@arnor.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