From: Ben Hutchings <ben@decadent.org.uk>
To: Joe Jin <joe.jin@oracle.com>
Cc: Alexander Indenbaum <baum@tehutinetworks.net>,
Andy Gospodarek <andy@greyhouse.net>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Guru Anbalagane <guru.anbalagane@oracle.com>,
"greg.marsden@oracle.com" <greg.marsden@oracle.com>,
DuanZhenzhong <zhenzhong.duan@oracle.com>,
Jaswinder Singh Rajput <jaswinder@infradead.org>
Subject: Re: [NETWORK] Firmware file for tehuti
Date: Fri, 17 Dec 2010 14:04:51 +0000 [thread overview]
Message-ID: <1292594691.3136.840.camel@localhost> (raw)
In-Reply-To: <4D0B0B70.9050306@oracle.com>
[-- Attachment #1: Type: text/plain, Size: 826 bytes --]
On Fri, 2010-12-17 at 15:04 +0800, Joe Jin wrote:
> Hi,
>
> Regarding firmware for driver tehuti, it request firmware name is
> tehuti/firmware.bin,
> but from kernel source found no such file but have tehuti/bdx.bin.ihex,
> so the firmware
> should be bdx.bin rather than firmware.bin?
Yes it should. I'm sorry for this mistake.
My first version of the patch to use request_firmware() used
"tehuti/firmware.bin". I then found Jaswinder's patch at
<http://git.infradead.org/users/jaswinder/firm-jsr-2.6.git?a=commitdiff;h=e41f3e5f8c5110871e376a2566b8eea2932b813b>,
which used the name "tehuti/bdx.bin". For some reason I changed the
name of the firmware file in my patch to match that, but not the code.
Ben.
--
Ben Hutchings
Once a job is fouled up, anything done to improve it makes it worse.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
next prev parent reply other threads:[~2010-12-17 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-17 7:04 [NETWORK] Firmware file for tehuti Joe Jin
2010-12-17 14:04 ` Ben Hutchings [this message]
2010-12-18 0:09 ` Joe Jin
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=1292594691.3136.840.camel@localhost \
--to=ben@decadent.org.uk \
--cc=andy@greyhouse.net \
--cc=baum@tehutinetworks.net \
--cc=greg.marsden@oracle.com \
--cc=guru.anbalagane@oracle.com \
--cc=jaswinder@infradead.org \
--cc=joe.jin@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=zhenzhong.duan@oracle.com \
/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.