From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: "Abhay_Salunke@dell.com" <Abhay_Salunke@dell.com>
Cc: greg@kroah.com, linux-kernel@vger.kernel.org, akpm@osdl.org,
Matt_Domsch@dell.com, ranty@debian.org
Subject: Re: [patch 2.6.12-rc3] modifications in firmware_class.c to support nohotplug
Date: Fri, 10 Jun 2005 14:57:11 -0500 [thread overview]
Message-ID: <d120d50005061012571c2e58a0@mail.gmail.com> (raw)
In-Reply-To: <367215741E167A4CA813C8F12CE0143B3ED3BC@ausx2kmpc115.aus.amer.dell.com>
On 6/10/05, Abhay_Salunke@dell.com <Abhay_Salunke@dell.com> wrote:
> I tired to do the following
> 1. echo 0 > /sys/class/firmware/timeout
> 2. modify the firmware.agent by commenting echo -1 when file is not
> present as below.
>
> if [ -f "$FIRMWARE_DIR/$FIRMWARE" ]; then
> echo 1 > $SYSFS/$DEVPATH/loading
> cp "$FIRMWARE_DIR/$FIRMWARE" $SYSFS/$DEVPATH/data
> echo 0 > $SYSFS/$DEVPATH/loading
> else
> # echo -1 > $SYSFS/$DEVPATH/loading
> Fi
> 3. load the dell_rbu driver : see dell_rbu code snipped below
>
> device_initialize(&rbu_device);
>
> strncpy(rbu_device.bus_id,"dell_rbu", BUS_ID_SIZE);
>
I think if you add:
kobject_set_name(&rbu_device.kobj, "%s", rbu_device.bus_id,"dell_rbu");
it will work much better. Also, are you initializing rbu_device with
all 0 to begin with?
--
Dmitry
next prev parent reply other threads:[~2005-06-10 19:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-10 19:45 [patch 2.6.12-rc3] modifications in firmware_class.c to support nohotplug Abhay_Salunke
2005-06-10 19:57 ` Dmitry Torokhov [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-09 21:11 Abhay_Salunke
2005-06-08 16:35 Abhay_Salunke
2005-06-08 16:23 Abhay_Salunke
2005-06-08 16:26 ` Greg KH
2005-06-08 17:06 ` Dmitry Torokhov
2005-06-08 16:04 Abhay_Salunke
2005-06-08 16:09 ` Greg KH
2005-06-08 15:56 Abhay Salunke
2005-06-08 15:17 Abhay Salunke
2005-06-08 15:56 ` Dmitry Torokhov
2005-06-08 16:02 ` Greg KH
2005-06-08 16:09 ` Dmitry Torokhov
2005-06-08 16:19 ` 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=d120d50005061012571c2e58a0@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=Abhay_Salunke@dell.com \
--cc=Matt_Domsch@dell.com \
--cc=akpm@osdl.org \
--cc=dtor_core@ameritech.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ranty@debian.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