From: David Miller <davem@davemloft.net>
To: joy@entuzijast.net
Cc: sparclinux@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: kernel 2.6.26.3 qla2xxx oopsing on Fire 280R
Date: Tue, 09 Sep 2008 15:59:51 -0700 (PDT) [thread overview]
Message-ID: <20080909.155951.129856467.davem@davemloft.net> (raw)
In-Reply-To: <20080909.155716.106283970.davem@davemloft.net>
From: David Miller <davem@davemloft.net>
Date: Tue, 09 Sep 2008 15:57:16 -0700 (PDT)
> From: Josip Rodin <joy@entuzijast.net>
> Date: Wed, 10 Sep 2008 00:00:38 +0200
>
> > On Tue, Sep 09, 2008 at 02:30:12PM -0700, David Miller wrote:
> > > I assume you use this device for your too filesystem, in which case
> > > the firmware has to be in the initial ramdisk.
> > >
> > > The qla2xxx firmware isn't in the firmware tree, it's in the filesystem
> > > somewhere, and that gets put into the initial ramdisk you build for
> > > a particular kernel image. For this reason CONFIG_FIRMWARE_IN_KERNEL
> > > won't make any difference.
> > >
> > > This takes a bit of skill to get working properly, I hate it too. It's
> > > really unfriendly to users and even kernel developers. These drivers
> > > should "just work" when you build them, rather than require contortions
> > > such as this.
> >
> > Exactly. And this *has* worked, up to now. I would run update-initramfs and
> > it would assemble the initial ramdisk and all was well.
>
> I wonder if the new firmware code looks for firmware under a different
> directory in the initramfs or filesystem, such as /lib/firmware/${KERNEL_VERSION}/
> and this is what is burning you.
>
> Wish I could be more help, this stuff is just as perplexing to me :-/
I wonder if you have to do some "make firmware_install" or similar now.
next prev parent reply other threads:[~2008-09-09 22:59 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-04 9:39 kernel 2.6.26.3 qla2xxx oopsing on Fire 280R Josip Rodin
2008-09-08 21:13 ` Andrew Vasquez
2008-09-08 21:23 ` David Miller
2008-09-08 21:49 ` Andrew Vasquez
2008-09-08 23:08 ` David Miller
2008-09-08 23:42 ` Josip Rodin
2008-09-09 1:35 ` Andrew Vasquez
2008-09-09 1:49 ` Josip Rodin
2008-09-09 1:53 ` Josip Rodin
2008-09-09 2:01 ` Andrew Vasquez
2008-09-09 14:39 ` Josip Rodin
2008-09-09 15:00 ` Josip Rodin
2008-09-09 21:30 ` David Miller
2008-09-09 22:00 ` Josip Rodin
2008-09-09 22:57 ` David Miller
2008-09-09 22:59 ` David Miller [this message]
2008-09-10 0:05 ` Josip Rodin
2008-09-10 0:30 ` David Miller
2008-09-11 11:37 ` Josip Rodin
2008-09-11 21:57 ` Josip Rodin
2008-09-11 22:01 ` David Miller
2008-09-11 22:15 ` Andrew Vasquez
2008-09-12 5:19 ` [PATCH scsi-rc-fixes] qla2xxx: Defer enablement of RISC interrupts until ISP initialization completes Andrew Vasquez
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=20080909.155951.129856467.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=joy@entuzijast.net \
--cc=linux-scsi@vger.kernel.org \
--cc=sparclinux@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox