Update QLogic ISP 24xx/25xx chips firmware to 8.07.00.MFC after: 1 month
sys/dev: further adoption of SPDX licensing ID tags.Mainly focus on files that use BSD 2-Clause license, however the tool Iwas using misidentified many licenses so this was mostly a manual - error
sys/dev: further adoption of SPDX licensing ID tags.Mainly focus on files that use BSD 2-Clause license, however the tool Iwas using misidentified many licenses so this was mostly a manual - errorprone - task.The Software Package Data Exchange (SPDX) group provides a specificationto make it easier for automated tools to detect and summarize well knownopensource licenses. We are gradually adopting the specification, notingthat the tags are considered only advisory and do not, in any way,superceed or replace the license texts.
show more ...
Update 25xx chips firmware from 7.03.00 to 8.03.00.While the same update is also available for 24xx chips, it seems havea problem with disabling virtual ports -- firmware handles the request,but
Update 25xx chips firmware from 7.03.00 to 8.03.00.While the same update is also available for 24xx chips, it seems havea problem with disabling virtual ports -- firmware handles the request,but does not respong on it, causing timeout in driver.MFC after: 1 month
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.
Update Qlogic 23XX firmware from 3.03.26 to 3.03.28
Update firmware for QLogic 22xx from 2.02.06 to 2.02.08.
Remove residual verbosity.firmware_register() already reports errors.
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.
Switch to using FC-Tape firmware.Sponsered by: SpectralogicMFC after: 1 week
Roll to the latest 2400/2500 firmware available from the public QLogicwebsite.Sponsored by: SpectralogicMFC after: 1 week
Update firmware to more recent versions.MFC after: 3 months
Don't spam dmesg with "registered firmware ..." when module is compiledinto kernel, unless there is a verbose boot flag set. There is no realneed to have this information printed.MFC after: 1 we
Don't spam dmesg with "registered firmware ..." when module is compiledinto kernel, unless there is a verbose boot flag set. There is no realneed to have this information printed.MFC after: 1 week
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
Make ispfw(4) play nice with individual firmware modules.- Do not let individual KLD module unregister firmware image loaded by ispfwor vice versa.- Make 'kldunload ispfw' actually unregister all
Make ispfw(4) play nice with individual firmware modules.- Do not let individual KLD module unregister firmware image loaded by ispfwor vice versa.- Make 'kldunload ispfw' actually unregister all firmware images loaded byispfw, not just 'isp_1040'.- Print which KLD module actually loaded the firmware image.- Remove unused return value from do_load_fw() and do_unload_fw() and removeduplicate sys/param.h while I am here.
The MODULE_NAME should "ispfw" unless overriden, not "isp".
Use 2K Login f/w.
Add QLogic 2400 (4Gb) firmware.
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
Add 2322 firmware.
Update 2300 f/w. This will probably be the lastupdate here before we switch to the new f/w loadingframework.
Fix -Wunder and make the sbus code really compile only on sparc64.
Roll firmware to the latest version. There are a bunch of featuresin alternate f/w versions that will be pursued at some points.MFC after: 1 month
Remember to snag firmware for the DELL OEM (6312) cardMFC after: 2 days
Start each of the license/copyright comments with /*-, minor shuffle of lines
Do a pass over all modules in the kernel and make them return EOPNOTSUPPfor unknown events.A number of modules return EINVAL in this instance, and I have leftthose alone for now and instead taugh
Do a pass over all modules in the kernel and make them return EOPNOTSUPPfor unknown events.A number of modules return EINVAL in this instance, and I have leftthose alone for now and instead taught MOD_QUIESCE to accept thisas "didn't do anything".
12