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:52:12 +0000	[thread overview]
Message-ID: <1111341133.21516.88.camel@localhost.localdomain> (raw)
In-Reply-To: <9e473391050319200625032789@mail.gmail.com>

On Sun, 2005-03-20 at 11:47 -0500, Jon Smirl wrote:
> On Sun, 20 Mar 2005 14:37:16 +0100, Kay Sievers <kay.sievers@vrfy.org> wrote:
> > I still would like to see clearly defined list of requirements for:
> >   o async userspace data-requests into the kernel
> >   o async userspace configuration-requests from the kernel
> 
> Here's another model that might be more general...
> 
> accept_user_data() -- adds the data/status attributes to the device sysfs entry
> 
> request_helper(completion, environment string) -- causes
> ACTION=helper, the environment string is added onto the normal
> environment for an event from this device class. Only async version.
> 
> In the completion routine...
> release_user_data() -- deletes the attributes, frees the data
> 
> This model addresses both the need to receive data and run helpers
> that don't need data.

Ok, let's collect what's need to get that:

o Emit events for devices to request a userspace-action on that
  device like copying data into a sysfs file or run a userspace
  program to setup this device.
  -Is this limited to physical devices?

o Events can happen anytime, no only on device creation time.

o We need an efficient way for the dumb hotplug-multiplexer to recognize
  that kind of events to prevent the execution of just another script
  for every hotplug event.

o The events should act asynchronously and the kernel should detect or is
  to be notified that the request has finished.
  -Do we need any timeout here?

o For data-loading-requests like the firmware case we need to be able to
  request more than one file for one single device.

o The DEVPATH of the request should be the device itself, that asks for data
  or setup.
  -Should the requests create a own child at the device directory or just
   attributes there?
  -How should attributes be named if we have multiple request for the
   same device?

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:52 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
2005-03-20 17:19 ` David Zeuthen
2005-03-20 17:39 ` Kay Sievers
2005-03-20 17:52 ` Kay Sievers [this message]
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=1111341133.21516.88.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).