From: Greg KH <greg@kroah.com>
To: Abhay_Salunke@Dell.com
Cc: marcel@holtmann.org, linux-kernel@vger.kernel.org, akpm@osdl.org,
Matt_Domsch@Dell.com
Subject: Re: [patch 2.6.12-rc3] dell_rbu: Resubmitting patch for new DellBIOS update driver
Date: Mon, 6 Jun 2005 11:16:09 -0700 [thread overview]
Message-ID: <20050606181608.GA10988@kroah.com> (raw)
In-Reply-To: <367215741E167A4CA813C8F12CE0143B3ED3AB@ausx2kmpc115.aus.amer.dell.com>
On Mon, Jun 06, 2005 at 11:27:53AM -0500, Abhay_Salunke@Dell.com wrote:
> > The firmware class creates a sysfs file. That is what I am referring
> to
> > here.
> >
> By doing a copy of the image to the sysfs file are we trying to do the
> automatic actions done by the hotplug scripts manually?
Ok, it seems everyone is way confused here. This is what I was thinking
of when I suggested using the firmware code:
- module loads and registers with firmware core doing the
"request_firmware_nowait" call.
- a hotplug event gets generated that everyone just ignores
(because it isn't really a big deal.)
- At some point, the user copies the firmware to the sysfs file
because they want to update their bios.
- the module is then told that firmware is present and it does
something with it.
Note, that between step 2 and 3, it could be _days_ or _months_. No
need to touch any hotplug scripts at all.
Does this make more sense now? It seems pretty simple to me...
thanks,
greg k-h
next prev parent reply other threads:[~2005-06-06 18:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 16:27 [patch 2.6.12-rc3] dell_rbu: Resubmitting patch for new DellBIOS update driver Abhay_Salunke
2005-06-06 18:16 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-07 14:47 Abhay_Salunke
2005-06-07 15:01 ` Greg KH
2005-06-06 20:22 Abhay_Salunke
2005-06-06 20:35 ` Greg KH
2005-06-06 20:01 Abhay_Salunke
2005-06-06 20:12 ` Greg KH
2005-06-06 18:54 Abhay_Salunke
2005-06-06 19:22 ` Greg KH
2005-06-03 19:57 Abhay_Salunke
2005-06-03 20:33 ` Greg KH
2005-06-03 19:00 Abhay_Salunke
2005-06-03 19:29 ` Greg KH
2005-06-03 13:30 Abhay_Salunke
2005-06-03 16:53 ` Marcel Holtmann
2005-06-03 18:03 ` Greg KH
2005-06-02 22:25 Abhay_Salunke
2005-06-02 22:45 ` Marcel Holtmann
2005-06-02 22:50 ` Andrew Morton
2005-06-03 5:19 ` Greg KH
2005-05-23 15:36 Abhay_Salunke
2005-05-23 15:50 ` 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=20050606181608.GA10988@kroah.com \
--to=greg@kroah.com \
--cc=Abhay_Salunke@Dell.com \
--cc=Matt_Domsch@Dell.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.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 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.