Re: cvs commit: src/sys/modules/iwi Makefile src/sys/dev/iwi if_iwi.c if_iwireg.h if_iwivar.h
From: Warner Losh (imp_at_bsdimp.com)
Date: 11/21/05
- Previous message: Scott Long: "Re: cvs commit: src/sys/modules/iwi Makefile src/sys/dev/iwi if_iwi.c if_iwi"
- In reply to: Daniel Eischen: "Re: cvs commit: src/sys/modules/iwi Makefile src/sys/dev/iwi if_iwi.c if_iwireg.h if_iwivar.h"
- Next in thread: Warner Losh: "Re: cvs commit: src/sys/modules/iwi Makefile src/sys/dev/iwi if_iwi.c if_iwireg.h if_iwivar.h"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 21 Nov 2005 12:39:48 -0700 (MST) To: deischen@freebsd.org
> Not taking one side or the other... Can we use a common
> tool to convert firmware to a kld? Just pass it the
> symbol name or whatever else you need?
The answer is 'it depends'...
> I guess this makes the assumption that most firmware consists
> of just one object file.
The object files vary somewhat as to what is in the file. Some are S
records in text format, while otherrs are COFF or some other format in
binary form. I had assumed that each driver would want to parse
things out into a useful form in the conversion program to keep the
kernel portion as small as possible. This is inharently driver
dependent.
However, if we wanted to have a raw bits into the kernel conduit, then
we could have a tool, so long as it handled an arbitrary number of
files. Many drivers have a 'primary' and a 'secondary' firmware to
load. But presenting an array to the driver, or having the driver
load multiple files is a way around this.
Having the kernel loader be able to load arbitrary files would be even
better...
Warner
_______________________________________________
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: Scott Long: "Re: cvs commit: src/sys/modules/iwi Makefile src/sys/dev/iwi if_iwi.c if_iwi"
- In reply to: Daniel Eischen: "Re: cvs commit: src/sys/modules/iwi Makefile src/sys/dev/iwi if_iwi.c if_iwireg.h if_iwivar.h"
- Next in thread: Warner Losh: "Re: cvs commit: src/sys/modules/iwi Makefile src/sys/dev/iwi if_iwi.c if_iwireg.h if_iwivar.h"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
- Re: Dynamically loading binaries in Kernel mode.
... standard filesystem and unless you load it using standard export driver ...
Allocate kernel level memory that is big enough to ... receive the binary image of the
dynamic code ... (microsoft.public.development.device.drivers) - Re: Linux GPL and binary module exception clause?
... >> But also note how it's only the BINARY MODULE that is a derived work. ...
> a device driver containing a binary blob that was explicitly written as ... Clearly
it no longer depends on the kernel, and you can show that to ... And I think this argument
is _especially_ strong for things like firmware ... (Linux-Kernel) - Re: need RAID driver for install, but no floppy drive
... >> which in this case will be the install kernel. ... > driver
on the rescue floppy. ... How do I mount those Debian install ... it should work
when you try to load a driver off the floppy using the ... (Debian-User) - Re: [PATCH] request_firmware: skip timeout if userspace was not notified
... needs to be removed from the kernel, that's known for a very long ... your point
is that the firmware loader is ... or use a kernel module for the driver that needs
... kernel on boot if built in unless an initramfs is carefully ... (Linux-Kernel) - Re: Evil: TI ACX111 non-success
... Perhaps ndis returning 6 and failing to load is a result of the ... This chip
has two ranges, ... it seems this driver wants the FwRad16.bin image. ...
If you plan to load the ndis.ko and if_ndis.ko kernel modules AFTER ... (freebsd-current)