From: "H. Peter Anvin" <hpa@zytor.com>
To: Oleg Verych <olecom@flower.upol.cz>
Cc: Oliver Neukum <oliver@neukum.org>,
linux-usb-devel@lists.sourceforge.net, Greg KH <greg@kroah.com>,
Dale Martenson <dmartenson@multitech.com>,
Al Borchers <alborchers@steinerpoint.com>,
LKML <linux-kernel@vger.kernel.org>,
mit-devel@lists.printk.net
Subject: Re: dlopen-like facility for conditional loading of symbols in modules (Re: Firmware for new ti_usb_3410_5052 devices)
Date: Sat, 03 Mar 2007 18:51:51 -0800 [thread overview]
Message-ID: <45EA3447.2080504@zytor.com> (raw)
In-Reply-To: <20070303133155.GM16509@flower.upol.cz>
Oleg Verych wrote:
>
> Maybe modules' dlopen() like facility would be better to handle static
> firmware or any other on-demand static data like ID tables etc.?
>
> I.e. some additional flag for an exported symbol (in a module), that
> this symbol maybe dynamically requested and used. As far as i can see,
> depmod generates static map, unresolved symbols must be in the kernel
> (System.map).
>
You can do this with request_module() and having your module overwrite a
hook.
> It will solve problem of having multiple unneeded firmware images if
> driver handles many devices and firmware is allowed to be in the
> kernel. No need in additional secure infrastructure.
>
This seems like a hacky way to accomplish what request_firmware() does
clearer!
-hpa
next prev parent reply other threads:[~2007-03-04 3:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1172824155.45e7e05b7980e@my.visi.com>
[not found] ` <20070303002707.GJ16509@flower.upol.cz>
[not found] ` <20070303002957.GA1966@kroah.com>
[not found] ` <200703030840.26982.oliver@neukum.org>
2007-03-03 13:31 ` dlopen-like facility for conditional loading of symbols in modules (Re: Firmware for new ti_usb_3410_5052 devices) Oleg Verych
2007-03-04 2:51 ` H. Peter Anvin [this message]
2007-03-04 15:03 ` Oleg Verych
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=45EA3447.2080504@zytor.com \
--to=hpa@zytor.com \
--cc=alborchers@steinerpoint.com \
--cc=dmartenson@multitech.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.net \
--cc=mit-devel@lists.printk.net \
--cc=olecom@flower.upol.cz \
--cc=oliver@neukum.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.