From: "BERTRAND Joël" <joel.bertrand@systella.fr>
To: sparclinux@vger.kernel.org
Subject: Re: [2.6.29.4] Blade 2000
Date: Fri, 29 May 2009 09:58:54 +0000 [thread overview]
Message-ID: <4A1FB1DE.4020006@systella.fr> (raw)
In-Reply-To: <4A1C36B5.6040707@systella.fr>
BERTRAND Joël a écrit :
> Hello,
>
> I have made some minor modifications in bbc_i2c driver to add en
> entry in /proc directory. ALl mofications have been made against
> 2.6.29.4 but I haven't verified that this kernel was bootable.
>
> I have built my own bbc_i2c driver as a module. 2.6.29.4 kernel
> hangs just after qla2xxx initialization. I don't think that this driver
> try to upload firmware. This firmware is built into the kernel.
>
> CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
> # CONFIG_STANDALONE is not set
> # CONFIG_PREVENT_FIRMWARE_BUILD is not set
> CONFIG_FW_LOADER=y
> CONFIG_FIRMWARE_IN_KERNEL=y
> CONFIG_EXTRA_FIRMWARE="ql2200_fw.bin"
> CONFIG_EXTRA_FIRMWARE_DIR="/lib/firmware"
>
> Root rayleigh:[/lib/firmware] > ls
> edgeport emi62 keyspan_pda ql2100_fw.bin ql2300_fw.bin ql2400_fw.bin
> emi26 ess korg ql2200_fw.bin ql2322_fw.bin yamaha
> Root rayleigh:[/lib/firmware] >
>
> Configuration:
>
> Blade 2000, 2 GB, 2*UIII+/900, Creator3D, internal NIC + 2*3Com NIC.
>
> Is it a known trouble ?
Nobody ? I have tried 2.6.29.1 with exactly the same bug. 2.6.28.7
worked fine.
Regards,
JKB
next prev parent reply other threads:[~2009-05-29 9:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 18:36 [2.6.29.4] Blade 2000 BERTRAND Joël
2009-05-29 9:58 ` BERTRAND Joël [this message]
2009-06-04 22:39 ` David Miller
2009-06-05 7:49 ` BERTRAND Joël
2009-06-05 7:59 ` David Miller
2009-06-11 10:38 ` David Miller
2009-06-11 10:56 ` BERTRAND Joël
2009-06-11 16:32 ` BERTRAND Joël
2009-06-12 0:06 ` David Miller
2009-06-12 7:25 ` BERTRAND Joël
2009-06-14 12:40 ` BERTRAND Joël
2009-07-17 17:23 ` David Miller
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=4A1FB1DE.4020006@systella.fr \
--to=joel.bertrand@systella.fr \
--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 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.