The kernel driver makes a call to userspace for a named firmware binary to which udev (or equivalent) responds with the appropriate file.

On Sep 27, 2013 5:33 PM, "Paul D. DeRocco" <> wrote:
What causes the firmware to be loaded? I'm trying to figure out why it's
happening so late. I've built a non-GUI system based on
gumstix-console-image, but replaced networkmanager with ifupdown, and I've
created a systemd unit to run "ifup -a" right at the very end of the boot
process, but it won't initialize my WiFi because the firmware doesn't
appear to be loaded until even later. The kernel message comes even after
the logon prompt. The ethernet starts correctly, and as soon as I've
logged on, I can type "ifup -a" and the WiFi starts up correctly.

Perhaps I should be triggering my ifup from a udev rule, but I've been
unable to figure out how to do that.


Ciao,               Paul D. DeRocco

October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
gumstix-users mailing list