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:34:52 +1100 [thread overview]
Message-ID: <1109054092.5327.94.camel@gaston> (raw)
In-Reply-To: <9e473391050221220564235858@mail.gmail.com>
On Tue, 2005-02-22 at 01:05 -0500, Jon Smirl wrote:
> On Tue, 22 Feb 2005 16:13:36 +1100, Benjamin Herrenschmidt
> <benh@kernel.crashing.org> wrote:
> > What we can/should provide, is a ncie helper to do the job once the
> > driver decides to have a go at it. I think userspace is the right
> > solution, similar to the firmware loader helpers, as I wrote earlier.
> > There are a few issues related on trying to run these before / is
> > mounted or during the sleep process, but those are things I plan to work
> > on & fix sooner or later. (Which is also why it has to be an
> > asynchronous API, so that the helper can call back "later" when the
> > helper has been found).
>
> Can a userspace solution solve the problem of cards that need to be
> posted when they are coming out of suspend?
Yes, though they'll come up a bit later than the rest of the world if
the driver can't resume them itself (which is what should happen
normally, running the BIOS on resume is a hack).
Also, as I wrote earlier, what we care about now is the API in the form
of a helper. It fits well to have that helper just do something similar
to the firmware loader, running the stuff in userspace, but that isn't
mandatory, we could change later to be in-kernel, partially, or even
have a CONFIG option wether to have the emulator in kernel or not :)
The driver doesn't have to care if we provide a suitable API. And
userspace helper is a good enough implementation to start with.
Ben.
prev parent reply other threads:[~2005-02-22 6:35 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
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 [this message]
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=1109054092.5327.94.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.