userland firmware loader?
From: Brian Fundakowski Feldman (green_at_FreeBSD.org)
Date: 07/10/04
- Previous message: Bernd Walter: "Re: USB locking"
- Next in thread: Poul-Henning Kamp: "Re: userland firmware loader?"
- Reply: Poul-Henning Kamp: "Re: userland firmware loader?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 9 Jul 2004 19:23:56 -0400 To: arch@FreeBSD.org
I'm writing a driver that uses a 100KB firmware file and could need to
read it again, after initialization, to reset the device (or to load
more). Since this device is primarily found in CardBus form, I think
it makes a lot of sense to be able to get the firmware file at any time
but without specific user intervention.
Is this something devd should be doing? It wouldn't be very hard to
provide an API with somewhat sysctl-like semantics via a device_*()
function to return data to userland, and a new newbus device method to
recieve data. Does this seem like something that should be done so
that many drivers don't waste space in the kernel with firmware images,
and don't need firmware via a separate kld module, without having to
reimplement it separately in each driver that could use this
functionality?
Alternately, I could just not be seeing where this kind of functionality
already exists. The usio driver in /etc/usbd.conf does something a
little like what I want to do, but it's not generic and only does it
based on a "load" event instead of a "give me firmware" event.
Thanks,
-- Brian Fundakowski Feldman \'[ FreeBSD ]''''''''''\ <> green@FreeBSD.org \ The Power to Serve! \ Opinions expressed are my own. \,,,,,,,,,,,,,,,,,,,,,,\ _______________________________________________ freebsd-arch@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-arch To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
- Previous message: Bernd Walter: "Re: USB locking"
- Next in thread: Poul-Henning Kamp: "Re: userland firmware loader?"
- Reply: Poul-Henning Kamp: "Re: userland firmware loader?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- Re: [PATCH][2.6][2/14] documentation update
... add udev.txt which describes how to use dvb and udev/sysfs ... The firmware
can be loaded automatically via the hotplug manager ... +- For the dvb-ttpci driver/av7110 card
you can download the firmware files from ... +file you probably know from the 2.4 DVB releases
driver. ... (Linux-Kernel) - Re: Fedora 5 - Intel Pro/Wireless LAN 2100 3B Mini PCI adapter woes.
... Guide to install the Intel PRO Wireless 2100 Driver for Linux ...
The ipw2100 binary firmware image. ... (comp.os.linux.networking) - Re: [RFC] binary firmware and modules
... via modinfo and could be used e.g. when packaging a kernel. ... given an example
via the QLogic gla2xxx driver. ... just don't know what firmware we'll need until
runtime. ... firmware file list is reasonable; but I think the model is a bad one. ...
(Linux-Kernel) - Re: Problem: NIC transmit timeouts
... I've seen two causes for this: 1) driver bug, 2) firmware bug. ... Another
fun aspect of case 2) is that since its PCI traffic related, ... the MTT register,
and the equivalent of the ICH ... (Linux-Kernel) - [PATCH, RFT] starfire net driver update
... The firmware is needed to ... * include the firmware with this driver.
... #ifdef HAVE_NETDEV_POLL ... #define RxComplType RxComplType3 ...
(Linux-Kernel)