sys/modules: normalize .CURDIR-relative paths to SRCTOPThis simplifies make output/logicTested with: `cd sys/modules; make ALL_MODULES=` on amd64MFC after: 1 monthSponsored by: Dell EMC Isilon
Rip off target mode support for parallel SCSI QLogic adapters.Hacks to enable target mode there complicated code, while didn't reallywork. And for outdated hardware fixing it is not really intere
Rip off target mode support for parallel SCSI QLogic adapters.Hacks to enable target mode there complicated code, while didn't reallywork. And for outdated hardware fixing it is not really interesting.Initiator mode tested with Qlogic 1080 adapter is still working fine.
show more ...
Update firmware images for Qlogic 24xx/25xx from 5.5.0 to 7.3.0.This also removes separate "_multi" images, since this funcationality isnow in base, and there is simply no new images without it fo
Update firmware images for Qlogic 24xx/25xx from 5.5.0 to 7.3.0.This also removes separate "_multi" images, since this funcationality isnow in base, and there is simply no new images without it for years.
Add 8Gb card firmware. Update some 2Gb and 4Gb f/w sets.Split 4Gb and 8Gb into pieces that can be either multi_idcapable or not.Reviewed by: scottl, kenApproved by: re
Don't build unused SBus front-ends for sun4v, don't build EBus front-endswhich are also likely to be irrelevant for sun4v (there's no SBus on sun4vand only some EBus devices). While at it fix some
Don't build unused SBus front-ends for sun4v, don't build EBus front-endswhich are also likely to be irrelevant for sun4v (there's no SBus on sun4vand only some EBus devices). While at it fix some style bugs according tostyle.Makefile(5) where appropriate.MFC after: 3 days
Add 2400 f/w support.
Convert isp(4) and ispfw(4) to use firmware(9) to manage firmwareloading for the QLogic cards.Because isp(4) exists before the root is mounted, it's not reallypossible for us to use the kernel's
Convert isp(4) and ispfw(4) to use firmware(9) to manage firmwareloading for the QLogic cards.Because isp(4) exists before the root is mounted, it's not reallypossible for us to use the kernel's linker to load modules directlyfrom disk- that's really too bad.However, the this is still a net win in in that the firmware hasbeen split up on a per chip (and in some cases, functionality)basis, so the amount of stuff loaded *can* be substantially lessthan 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 1080firmware is built as isp_1080_it.ko.For compatibility purposes (i.e., to perturb folks the least), wealso still build all of the firmware as one ispfw.ko module.This allows us to let 'ispfw_LOAD' keep on working in existingloader.conf files. If you now want to strip this down to justthe firmware for your h/w, you can then change loader.conf toload the f/w you specifically want.We also still allow for ispfw to be statically built (e.g., forPAE and sparc64).Future changes will look at f/w unloading and also role switchingthat then uses the kernel linker to load different ips f/w sets.MFC after: 2 months
Use a consistent style and one much closer to the rest of /usr/src
add ispfw module