From: Jesse Barnes <jbarnes@sgi.com>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: fbdev <linux-fbdev-devel@lists.sourceforge.net>,
benh@kernel.crashing.org
Subject: Re: [PATCH] Provide control of active VGA device on PCI systems
Date: Tue, 22 Feb 2005 10:50:43 -0800 [thread overview]
Message-ID: <200502221050.43534.jbarnes@sgi.com> (raw)
In-Reply-To: <9e473391050219230764b0dfd2@mail.gmail.com>
On Saturday, February 19, 2005 11:07 pm, Jon Smirl wrote:
> New version to previous patch. This one adds the hotplug event mentioned
> before.
>
> To achieve secondary card reset:
> Load a framebuffer driver.
> Driver causes hotplug add event
> reset=x environment parm indicates reset, primary cards is false
> run user space reset program
> read VBIOS content using existing API
> turn off all VGA devices, sysfs vga=3
> reset the card
> restore original VGA devices. sysfs vga=4
> set sysfs no_reset=1 to prevent further resets
>
> Tomorrow I'll clean up a user space reset app and post it.
Nice, if this is combined with Ben's suggestion of using a firmware loader
type model to deal with POSTing, it seems like we're in pretty good shape.
Can you add documentation for this API to
Documentation/filesystems/sysfs-<foo>.txt (maybe the pci file or a new file)
so that userspace people will be able to figure out how to use it?
Also, how does one know if a card is 'primary' or not? I.e. some BIOSes will
POST all cards, some will POST only one, and some will POST none...
Thanks,
Jesse
-------------------------------------------------------
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-22 18:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 5:50 [PATCH] Provide control of active VGA device on PCI systems Jon Smirl
2005-02-20 7:07 ` Jon Smirl
2005-02-22 18:50 ` Jesse Barnes [this message]
2005-02-22 20:57 ` Benjamin Herrenschmidt
2005-02-22 21:02 ` Jesse Barnes
2005-02-22 21:27 ` Benjamin Herrenschmidt
2005-02-22 21:42 ` Jon Smirl
2005-02-20 8:23 ` Benjamin Herrenschmidt
2005-02-20 16:35 ` Jon Smirl
2005-02-22 4:07 ` James Simmons
2005-02-24 6:14 ` Jon Smirl
2005-02-22 4:13 ` James Simmons
2005-02-22 4:47 ` 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=200502221050.43534.jbarnes@sgi.com \
--to=jbarnes@sgi.com \
--cc=benh@kernel.crashing.org \
--cc=jonsmirl@gmail.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/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.