From: Jon Smirl <jonsmirl@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
fbdev <linux-fbdev-devel@lists.sourceforge.net>,
Greg KH <greg@kroah.com>
Subject: Re: Problem: how to sequence reset of PCI hardware
Date: Mon, 21 Feb 2005 12:27:13 -0500 [thread overview]
Message-ID: <9e47339105022109276261e845@mail.gmail.com> (raw)
In-Reply-To: <421A142A.1060302@pobox.com>
On Mon, 21 Feb 2005 12:02:34 -0500, Jeff Garzik <jgarzik@pobox.com> wrote:
> Jon Smirl wrote:
> > On Mon, 21 Feb 2005 03:37:45 -0500, Jeff Garzik <jgarzik@pobox.com> wrote:
> >
> >>You either need to execute the video BIOS to initialize the hardware
> >>registers, or initialize the hardware registers themselves.
> >
> >
> > That is what the user mode reset program does.
> >
> > The problem is, how do I get it to run before calling the device's
> > probe function? Most of the framebuffer drivers assume that the
> > hardware has already been reset in their probe code.
>
> <shrug> You do precisely what you just said: run it before the
> device's probe function.
>
> That typically means either initramfs addition or using 'install
> <module> command...' in /etc/modprobe.conf.
How does install module work if one driver is servicing several adapters?
What if one adapater is in the card at boot and another shows up via hotplug?
>
> Jeff
>
>
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-02-21 17:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-21 7:24 Problem: how to sequence reset of PCI hardware Jon Smirl
2005-02-21 8:37 ` Jeff Garzik
2005-02-21 16:52 ` Jon Smirl
2005-02-21 17:02 ` Jeff Garzik
2005-02-21 17:27 ` Jon Smirl [this message]
2005-02-21 17:33 ` Jon Smirl
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=9e47339105022109276261e845@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=greg@kroah.com \
--cc=jgarzik@pobox.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).