linux-hotplug.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: Rework of request firmware
Date: Sun, 20 Mar 2005 17:16:58 +0000	[thread overview]
Message-ID: <1111339018.21516.51.camel@localhost.localdomain> (raw)
In-Reply-To: <9e473391050319200625032789@mail.gmail.com>

On Sun, 2005-03-20 at 10:35 -0500, Jon Smirl wrote:
> On Sun, 20 Mar 2005 14:37:16 +0100, Kay Sievers <kay.sievers@vrfy.org> wrote:
> > What is the concept of a "post"? Does it receive data for the kernel to
> > use? What is the overlap with firmware loading here? You just need to
> > run a program from userspace, right?
> 
> Post is the commonly used term for what you do to hardware when it is
> first turned on to get it running. For example the system BIOS posts
> all the devices in the system.

Ok, the Power On Self Test. That sounds a bit specfic for something that
is a generic configuration request.

> The system BIOS does not post secondary video cards. For these cards
> when the driver is first loaded I have to run a program that takes the
> video BIOS ROM on the card and runs it in vm86/emu86. The ROM contents
> are already exposed in sysfs. If I don't do this the hardware will not
> respond. The system BIOS does this for you in real mode on the primary
> card during the boot process. Another time the video BIOS needs to be
> run is when graphics cards are being resumed. The posting program
> needs to run in user space and be triggered from the probe function.

Ah, ok. Sounds reasonable and like a nice trick too, to run x86 hardware
on other platforms. :)

> I initially started to add support for post as a standalone service
> but received complaints on lkml that the code needed was almost
> identical to request_firmware(). 

Well running a configuration program is just a very small subset
compared to copying data into the kernel, but anyway...

> BenH has also pointed out that the
> synchronous request_firmware() will deadlock in many cases during the
> resume process.

I believe that and events may get lost too in such situations.

Thanks,
Kay



-------------------------------------------------------
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_ide95&alloc_id\x14396&op=click
_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2005-03-20 17:16 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-20  4:06 Rework of request firmware Jon Smirl
2005-03-20 13:37 ` Kay Sievers
2005-03-20 15:35 ` Jon Smirl
2005-03-20 16:47 ` Jon Smirl
2005-03-20 17:16 ` Kay Sievers [this message]
2005-03-20 17:19 ` David Zeuthen
2005-03-20 17:39 ` Kay Sievers
2005-03-20 17:52 ` Kay Sievers
2005-03-20 17:52 ` Darren Salt
2005-03-20 18:00 ` Kay Sievers
2005-03-20 18:24 ` Jon Smirl
2005-03-20 19:02 ` Jon Smirl
2005-03-20 19:17 ` Kay Sievers
2005-03-20 19:27 ` Kay Sievers
2005-03-20 19:50 ` Jon Smirl
2005-03-20 20:25 ` Kay Sievers
2005-03-20 20:39 ` Jon Smirl
2005-03-21  2:37 ` Kay Sievers
2005-03-22  0:29 ` Linas Vepstas
2005-03-22  2:25 ` Kay Sievers
2005-03-22  3:06 ` Jon Smirl
2005-03-22  8:27 ` Roman Kagan
2005-03-22 10:45 ` Kay Sievers
2005-03-22 10:55 ` Kay Sievers
2005-03-22 14:37 ` Jon Smirl
2005-03-22 17:53 ` Linas Vepstas
2005-03-22 18:09 ` Linas Vepstas
2005-03-22 18:43 ` Jon Smirl
2005-03-23  1:08 ` Greg KH

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=1111339018.21516.51.camel@localhost.localdomain \
    --to=kay.sievers@vrfy.org \
    --cc=linux-hotplug@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).