From: "Raoul Bhatia [IPAX]" <r.bhatia@ipax.at>
To: linux-scsi@vger.kernel.org
Cc: lnxgnome@hopnet.net, wakko@animx.eu.org
Subject: Re: AIC94xx SAS question.
Date: Mon, 28 Apr 2008 11:35:49 +0200 [thread overview]
Message-ID: <48159A75.6020400@ipax.at> (raw)
In-Reply-To: <48140F9F.1070109@hopnet.net>
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@ipax.at
Technischer Leiter
IPAX - Aloy Bhatia Hava OEG web. http://www.ipax.at
Barawitzkagasse 10/2/2/11 email. office@ipax.at
1190 Wien tel. +43 1 3670030
FN 277995t HG Wien fax. +43 1 3670030 15
____________________________________________________________________
next prev parent reply other threads:[~2008-04-28 9:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-21 23:19 AIC94xx SAS question Wakko Warner
2008-04-26 4:58 ` Keith Hopkins
2008-04-26 14:56 ` Wakko Warner
2008-04-26 15:56 ` James Bottomley
2008-04-29 1:46 ` Wakko Warner
2008-04-27 5:31 ` Keith Hopkins
2008-04-28 9:35 ` Raoul Bhatia [IPAX] [this message]
2008-04-29 2:04 ` Wakko Warner
2008-04-29 7:41 ` Raoul Bhatia [IPAX]
2008-04-29 1:53 ` Wakko Warner
-- strict thread matches above, loose matches on Subject: below --
2008-04-22 22:10 Wakko Warner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48159A75.6020400@ipax.at \
--to=r.bhatia@ipax.at \
--cc=linux-scsi@vger.kernel.org \
--cc=lnxgnome@hopnet.net \
--cc=wakko@animx.eu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.