From: David Miller <davem@xxxxxxxxxxxxx>
Date: Tue, 09 Sep 2008 15:57:16 -0700 (PDT)
> From: Josip Rodin <joy@xxxxxxxxxxxxxx>
> 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.
--
To unsubscribe from this list: send the line "unsubscribe sparclinux" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
