From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Alex Deucher <alexdeucher@gmail.com>,
Dave Airlie <airlied@linux.ie>,
dri-devel@lists.sourceforge.net,
Linux Kernel list <linux-kernel@vger.kernel.org>,
xorg@lists.freedesktop.org
Subject: Re: POSTing of video cards (WAS: Solo Xgl..)
Date: Tue, 22 Feb 2005 17:32:40 +1100 [thread overview]
Message-ID: <1109053960.5326.91.camel@gaston> (raw)
In-Reply-To: <9e4733910502212203671eec73@mail.gmail.com>
On Tue, 2005-02-22 at 01:03 -0500, Jon Smirl wrote:
> On Tue, 22 Feb 2005 16:13:36 +1100, Benjamin Herrenschmidt
> <benh@kernel.crashing.org> wrote:
> > On Mon, 2005-02-21 at 23:56 -0500, Alex Deucher wrote:
> > I think that the driver is the "chief" here and the one to know what to
> > do with the cards it drives. It can detect a non-POSTed card and deal
> > with it.
>
> What about the x86 case of VGA devices that run without a driver being
> loaded? Do we force people to load an fbdev driver to get the reset?
> The BIOS deficiency strategy works for these devices.
Do we need to deal with those at all ? (I mean _really_: do we care ?)
And even if we did, then we could have the vga "legacy" driver use the
firmware loader to "boot" them. And again, you seem to dismiss all my
other arguments...
Ben.
next prev parent reply other threads:[~2005-02-22 6:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0502201049480.18753@skynet>
[not found] ` <4218BAF0.3010603@tungstengraphics.com>
[not found] ` <21d7e997050220150030ea5a68@mail.gmail.com>
[not found] ` <9e4733910502201542afb35f7@mail.gmail.com>
[not found] ` <1108973275.5326.8.camel@gaston>
[not found] ` <9e47339105022111082b2023c2@mail.gmail.com>
[not found] ` <1109019855.5327.28.camel@gaston>
[not found] ` <9e4733910502211717116a4df3@mail.gmail.com>
2005-02-22 3:12 ` POSTing of video cards (WAS: Solo Xgl..) Benjamin Herrenschmidt
2005-02-22 4:42 ` Jon Smirl
2005-02-22 5:09 ` Benjamin Herrenschmidt
2005-02-22 19:19 ` Linus Torvalds
2005-02-22 19:38 ` Dmitry Torokhov
2005-02-22 20:46 ` Linus Torvalds
2005-02-22 4:56 ` Alex Deucher
2005-02-22 5:13 ` Benjamin Herrenschmidt
2005-02-22 6:03 ` Jon Smirl
2005-02-22 6:32 ` Benjamin Herrenschmidt [this message]
2005-02-22 6:42 ` Jon Smirl
2005-02-22 6:52 ` Jon Smirl
2005-02-22 6:57 ` Benjamin Herrenschmidt
2005-02-28 14:36 ` Pavel Machek
2005-02-28 16:06 ` Vladimir Dergachev
2005-02-28 16:47 ` Keith Packard
2005-02-22 6:05 ` Jon Smirl
2005-02-22 6:34 ` Benjamin Herrenschmidt
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=1109053960.5326.91.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=airlied@linux.ie \
--cc=alexdeucher@gmail.com \
--cc=dri-devel@lists.sourceforge.net \
--cc=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=xorg@lists.freedesktop.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