linux-kernel - AIC94xx SAS question.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date:	Tue, 22 Apr 2008 18:10:35 -0400
From:	Wakko Warner <wakko@...mx.eu.org>
To:	linux-kernel@...r.kernel.org
Subject: AIC94xx SAS question.

Please keep me in CC.

This is a general question and probably doesn't matter which kernel
(although the one in question is 2.6.23 vanilla)

I know that this device requires firmware to operate which has to be loaded
when the driver is loaded.

I'd like to have this driver compiled into the kernel.  My question is:

Can either of these be done:
1) Embed the firmware into the driver so that it can be used before the
rootfs id mounted.
2) Can the firmware be loaded in an initr{d,amfs}?  I personnaly despise
initr{d,amfs} and if this option is used, I'd prefer it not to be kernel
specific (as in having the driver for the card in the initr{d,amfs}) this
way a kernel upgrade wouldn't change the initr{d,amfs}.  I know there are
tools for this kind of thing, but I find it quite pointless to have the
driver in 2 places (in the init{r,amfs} and in /lib/modules)  I also realize
that "disks are cheap" blah blah, but that's not the point.

I sent this to the linux-scsi list but didn't get too many helpful responces

-- 
 Lab tests show that use of micro$oft causes cancer in lab animals
 Got Gas???
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/