public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Jon Smirl <jonsmirl@gmail.com>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Dave Airlie <airlied@linux.ie>,
	dri-devel@lists.sourceforge.net, xorg@lists.freedesktop.org,
	Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: POSTing of video cards (WAS: Solo Xgl..)
Date: Tue, 22 Feb 2005 14:38:48 -0500	[thread overview]
Message-ID: <d120d50005022211384a83726d@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0502221111410.2378@ppc970.osdl.org>

On Tue, 22 Feb 2005 11:19:10 -0800 (PST), Linus Torvalds
<torvalds@osdl.org> wrote:
> 
> 
> On Mon, 21 Feb 2005, Jon Smirl wrote:
> >
> > I was working on the assumption that all PCI based, VGA class hardware
> > that is not the boot device needs to be posted.
> 
> I don't think that's true. We certainly don't _want_ it to be true in the
> long run - and even now there are cards that we can initialize fully
> without using the BIOS at all.
> 
> > And that the posting should occur before the drivers are
> > loaded.
> 
> Personally, I'd much rather let the driver be involved in the decision.
> 
> That may mean that the probe routine knows how to initialize the card, but
> it may mean that it does an "exec_usermodehelper()" kind of thing.
> Actually, I'd prefer it if this was largely up to "udev": if the driver
> notices that it can't initialize the card, why not just enumerate it
> enough that "udev" knows about it (that's pretty much automatic), and let
> the driver just ignore the card until some (possibly much later) date when
> the user level scripts have found it and initialized it.
> 
> That would imply that the driver have some "re-attach" entrypoint (which
> migth be a ioctl, but might also be just a /sysfs file access), which is
> the user-lands way of saying "try again - I've now initialized the
> hardware".
> 

This sounds awfully like firmware loader that seems to be working just
fine for a ranfe of network cards and other devices.

-- 
Dmitry

  reply	other threads:[~2005-02-22 19:39 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 [this message]
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
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=d120d50005022211384a83726d@mail.gmail.com \
    --to=dmitry.torokhov@gmail.com \
    --cc=airlied@linux.ie \
    --cc=benh@kernel.crashing.org \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=dtor_core@ameritech.net \
    --cc=jonsmirl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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