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

  • Next message: Warner Losh: "Re: cvs commit: src/sys/modules/iwi Makefile src/sys/dev/iwi if_iwi.c if_iwi" 
    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"

  • Next message: Warner Losh: "Re: cvs commit: src/sys/modules/iwi Makefile src/sys/dev/iwi if_iwi.c if_iwi"

    Relevant Pages

    • Re: [GIT *] Allow request_firmware() to be satisfied from in-kernel, use it in more drivers.
      ... This whole "working device" argument is total bullshit. ... If the driver was a module before, it needed a module load to become ... If you could load the module, you could load the firmware. ...
      (Linux-Kernel)
    • 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 2/3] firmware: Add CONFIG_BUILTIN_FIRMWARE option
      ... the kernel handles device nodes and on how udev maps them to real ... Please keep in mind that when we created request_firmwaremost of the driver model developers still thought that having class devices was a good idea. ... That has changed and to represent firmware loading in a clean and race free environment where you could load multipl firmwares at the same time for the same driver, ... firmware files inside the kernel. ...
      (Linux-Kernel)