FreeBSD source tree https://cgit-dev.freebsd.org/src-test2/atom?h=release%2F7.0.0_cvs 2008-02-24T05:45:17Z 2008-02-24T05:45:17Z cvs2svn cvs2svn@FreeBSD.org 2008-02-24T05:45:17Z urn:sha1:a9c219fa3cec18ef9f30edec6fa106bf0e2d423d 'RELENG_7_0_0_RELEASE'. This commit was manufactured to restore the state of the 7.0-RELEASE image. 2006-08-26T18:40:25Z Matt Jacob mjacob@FreeBSD.org 2006-08-26T18:40:25Z urn:sha1:77b1a4d66af2809eaf8c68cd852d53c52c8329c8 2006-07-09T17:50:20Z Matt Jacob mjacob@FreeBSD.org 2006-07-09T17:50:20Z urn:sha1:9a5af41076070ffd3bd3cfd053cbed3653bb63e5 loading for the QLogic cards. Because isp(4) exists before the root is mounted, it's not really possible for us to use the kernel's linker to load modules directly from disk- that's really too bad. However, the this is still a net win in in that the firmware has been split up on a per chip (and in some cases, functionality) basis, so the amount of stuff loaded *can* be substantially less than the 1.5MB of firmware images that ispfw now manages. That is, each specific f/w set is now also built as a module. For example, QLogic 2322 f/w is built as isp_2322.ko and Initiator/Target 1080 firmware is built as isp_1080_it.ko. For compatibility purposes (i.e., to perturb folks the least), we also still build all of the firmware as one ispfw.ko module. This allows us to let 'ispfw_LOAD' keep on working in existing loader.conf files. If you now want to strip this down to just the firmware for your h/w, you can then change loader.conf to load the f/w you specifically want. We also still allow for ispfw to be statically built (e.g., for PAE and sparc64). Future changes will look at f/w unloading and also role switching that then uses the kernel linker to load different ips f/w sets. MFC after: 2 months 2001-01-06T14:00:42Z David E. O'Brien obrien@FreeBSD.org 2001-01-06T14:00:42Z urn:sha1:c68159a6d8eede11766cf13896d0f7670dbd51aa 2000-06-18T05:08:36Z Matt Jacob mjacob@FreeBSD.org 2000-06-18T05:08:36Z urn:sha1:24e83068e703782f3ddb2a03913ee1f064d98218