just for the records Keith Hopkins wrote: > SuSE loads the driver as a module and the firmware in initrd. I haven't > tried initramfs, nor compiling it into the kernel. > > I unpacked my current initrd, and in it I found: > > lib/firmware/aic94xx-seq.fw > + some ql firmware that I don't need. > > I'm not sure if the driver compiled for SuSE "just knows" to look in > /lib/firmware, or how it finds the file. It might have something to do > with the firmware_class module in SuSE. > I do remember that I needed to load 'edd' before 94xx, or it would not > init the firmware. this is a default behaviour of this and many other drivers. > As for compiling the driver in the kernel, and putting the firmware in > initrd/initramfs, you would have to force the init of the 94xx module to > be after the initrd/initramfs was initialized, loaded and mounted. I > have not checked to see if that is currently possible. in the end, there is no big deal in putting the firmware into the initramfs. some distributions may work out of the box, some might require a little tuning of an initramfs hook. which leads me to my question: why are you absolutly against an initramfs image? properly configured - and that is not a big deal in current versions of mkinitramfs and current distributions - there are few possibilities to break the setup. if you require assistance, i can help. cheers, raoul -- ____________________________________________________________________ DI (FH) Raoul Bhatia M.Sc. email. r.bhatia@xxxxxxx Technischer Leiter IPAX - Aloy Bhatia Hava OEG web. http://www.ipax.at Barawitzkagasse 10/2/2/11 email. office@xxxxxxx 1190 Wien tel. +43 1 3670030 FN 277995t HG Wien fax. +43 1 3670030 15 ____________________________________________________________________ -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
