-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
(I've already reported this previously as post scriptum
to a different bugreport, so it might have slipped through
unnoticed...)
The linux kernel configuration help text for the LSI fusion MPT
driver (CONFIG_FUSION) provides this information:
[...]
If you have Fusion MPT hardware and want to use it, you can say
Y or M here to add MPT (base + ScsiHost) drivers.
<Y> = build lib (fusion.o), and link [static] into the kernel [2]
proper
<M> = compiled as [dynamic] modules [3] named: (mptbase.o,
mptscsih.o)
[2] In order enable capability to boot the linux kernel
natively from a Fusion MPT target device, you MUST
answer Y here! (currently requires CONFIG_BLK_DEV_SD)
[...]
This is at least misleading: It _is_ possible to boot from
a SCSI drive connected to a LSI Fusion MPT controller and have
the device driver loaded as module: just use an initial ramdisk
which contains the necessary modules and load them in linuxrc
There is nothing special here: I do this all the time with
all kind of hardware: RAID controllers, SCSI controllers,
IDE controllers (ok, modular IDE is now broken with 2.4.2x,
but it used to work in the good old times), even diskless
root fs is possible using initrd (as you all know)
When I first tried to figure if Linux did support the LSI1030
controller, this comment made me quite insecure: I did not want
to compile a custom kernel just for this controller and wondered,
what might be so special about this driver.
But it turned out this wasn't necessary. You can have a modular
kernel and boot from your harddisk connected to a fusion MPT
controller quite fine, using the initial ramdisk method. No
special customized kernel needed! :-)
With linux-2.4.21-rc6-ac1 (my current test system), just the
following modules are needed (order is important):
scsi_mod
mptbase
mptscsih
sd_mod
and any other module (like filesystem driver) you need to
access your root fs.
I just thought this might be of interest for you...
Perhaps the comment could be changed so it doesn't confuse
people (like me), who are actually reading the documentation... ;-)
- - andreas
- --
Andreas Haumer | mailto:[email protected]
*x Software + Systeme | http://www.xss.co.at/
Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0
A-1100 Vienna, Austria | Fax: +43-1-6060114-71
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE+264ZxJmyeGcXPhERAoN8AJwLe8zMHNN/yCq5gj5BuZ0amFwH3QCdFi0Y
8fOSlS6LCg4J5W2YgCuFpH4=
=e0mr
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
Delaney, Pam wrote:
> Hello Andreas,
>
> Thanks for the heads up.
> The remarks are obsolete and need to be stricken.
> They will be removed from my code base.
>
Thank you!
And many thanks for your work on this driver!
It's really a fine piece of software, well documented,
a joy to read the source code (IMHO)!
- - andreas
- --
Andreas Haumer | mailto:[email protected]
*x Software + Systeme | http://www.xss.co.at/
Karmarschgasse 51/2/20 | Tel: +43-1-6060114-0
A-1100 Vienna, Austria | Fax: +43-1-6060114-71
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQE+3HQMxJmyeGcXPhERAnkcAJ9eL+/ayz1x4i+uw0EoOEQtkqiPlACeJTMM
8VwX27LLd3PSYh1pCWR7WHE=
=/waB
-----END PGP SIGNATURE-----