From: Marcel Holtmann <marcel@holtmann.org>
To: Dmitry Torokhov <dtor_core@ameritech.net>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Simon Kelley <simon@thekelleys.org.uk>
Subject: Re: [OOPS/HACK] atmel_cs and the latest changes in sysfs/symlink.c
Date: Mon, 26 Apr 2004 15:09:51 +0200 [thread overview]
Message-ID: <1082984991.28880.145.camel@pegasus> (raw)
In-Reply-To: <200404260732.46315.dtor_core@ameritech.net>
Hi Dmitry,
> This is wrong... What if you have several devices that are needed firmware?
> You are not only loading a specific firmware but do it for a specific device.
> You may also want to do something else with it...
>
> I think until pcmcia either provides or allows to create devices on pcmcia
> bus you can just fixup the name breakage like I did for atmel driver and
> leave it be. The device is not registered and not used in any way except to
> provide "unique" name for fimrware loader, at list in atmel_cs that is the
> case.
as you said the only real goal of the device in request_firmware() is to
provide us with a unique path to the "loading" and "data" files. The
advantage of having the device linked is currently not used by the
firmware.agent script and I don't think that it ever will be used.
However you can take a look at 2.4, where the device parameter is only a
string. So what is wrong with letting request_firmware() create a dummy
and temporary device that is not related to any hardware?
Regards
Marcel
next prev parent reply other threads:[~2004-04-26 13:10 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-23 6:42 [OOPS/HACK] atmel_cs and the latest changes in sysfs/symlink.c Dmitry Torokhov
2004-04-23 12:25 ` Marcel Holtmann
2004-04-23 13:02 ` Dmitry Torokhov
2004-04-23 14:26 ` Marcel Holtmann
2004-04-23 16:55 ` Dmitry Torokhov
2004-04-23 17:16 ` Greg KH
2004-04-23 18:50 ` Marcel Holtmann
2004-04-23 19:46 ` Greg KH
2004-04-23 20:35 ` Russell King
2004-04-23 21:02 ` Marcel Holtmann
2004-04-23 15:31 ` Greg KH
2004-04-23 17:19 ` Greg KH
2004-04-23 18:03 ` Greg KH
2004-04-24 6:44 ` Dmitry Torokhov
2004-04-25 2:49 ` Greg KH
2004-04-25 21:48 ` Dmitry Torokhov
2004-05-04 21:04 ` Greg KH
2004-05-05 7:08 ` Dmitry Torokhov
2004-05-07 23:25 ` Greg KH
2004-04-26 10:19 ` Vojtech Pavlik
2004-04-23 19:55 ` Russell King
2004-04-23 20:14 ` Marcel Holtmann
2004-04-23 20:39 ` Russell King
2004-04-25 21:53 ` Dmitry Torokhov
2004-04-25 22:58 ` Russell King
2004-04-26 10:35 ` Marcel Holtmann
2004-04-26 12:32 ` Dmitry Torokhov
2004-04-26 13:09 ` Marcel Holtmann [this message]
2004-04-27 5:57 ` Dmitry Torokhov
2004-04-26 12:26 ` Dmitry Torokhov
2004-04-23 15:28 ` 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=1082984991.28880.145.camel@pegasus \
--to=marcel@holtmann.org \
--cc=dtor_core@ameritech.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=simon@thekelleys.org.uk \
/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