From: Jon Smirl <jonsmirl@gmail.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
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 01:52:02 -0500 [thread overview]
Message-ID: <9e47339105022122526338b2c9@mail.gmail.com> (raw)
In-Reply-To: <1109053960.5326.91.camel@gaston>
Does the kernel need to keep a bit that says the device has been
posted, don't do it again? Should removing/inserting a driver cause a
repost? I was going to add bit in pci_dev that tracks the reset status
so that it will persist across unloads. Do we have code to tell if
hardware needs a reset without the tracking bit?
On the x86 DRM will run without fbdev loaded. So DRM needs to also be
able to do the post and well as fbdev. Or we can just leave the old
drivers alone and only implement this in a merged fbdev/drm driver?
When current X loads it's going to reset the cards again, that may
stomp anything the driver has set up.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2005-02-22 6:52 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 [this message]
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=9e47339105022122526338b2c9@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=airlied@linux.ie \
--cc=alexdeucher@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=dri-devel@lists.sourceforge.net \
--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