From: Ben Hutchings <ben@decadent.org.uk>
To: Ken Kawasaki <ken_kawasaki@spring.nifty.jp>
Cc: netdev@vger.kernel.org, David Woodhouse <dwmw2@infradead.org>
Subject: Re: Re:[PATCH kernel 2.6.32-rc5] pcnet_cs: add cis of PreMax PE-200 ethernet pcmcia card
Date: Fri, 05 Mar 2010 12:46:19 +0000 [thread overview]
Message-ID: <1267793179.2819.328.camel@localhost> (raw)
In-Reply-To: <20100305210151.b27ce31a.ken_kawasaki@spring.nifty.jp>
[-- Attachment #1: Type: text/plain, Size: 1186 bytes --]
On Fri, 2010-03-05 at 21:01 +0900, Ken Kawasaki wrote:
> Hi,
>
> > The CIS files under firmware/ are, according to firmware/WHENCE,
> > 'developed by the pcmcia-cs project'. So I had a look at what's left of
> > the pcmcia-cs project and its last release, and found that it includes:
> >
> > - the tool 'pack_cis' which compiles a text version of CIS to the
> > standard binary format
> > - text versions of most of the CIS files
> >
> > Since the text versions contain comments which are excluded from the
> > binary format, I believe they should be considered the 'preferred form
> > for modification' and included in the linux-2.6 and linux-firmware trees
> > along with the binaries.
> >
>
> Actually, it is better to build CIS by "pack_cis firmware/cis/src/xxx.cis"
> instead of "IHEX firmware/cis/xxx.cis".
>
> In that case, the "pack_cis" tool should be included in the kernel-tree.
We don't include other firmware-building tools in the tree, even where
they are free software. Why this one?
Ben.
--
Ben Hutchings
Q. Which is the greater problem in the world today, ignorance or apathy?
A. I don't know and I couldn't care less.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
prev parent reply other threads:[~2010-03-05 12:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-25 2:10 [PATCH kernel 2.6.32-rc5] pcnet_cs: add cis of PreMax PE-200 ethernet pcmcia card Ken Kawasaki
2009-10-25 2:13 ` Ben Hutchings
2010-03-05 0:02 ` Ben Hutchings
2010-03-05 11:21 ` Ken Kawasaki
2010-03-05 12:01 ` Ken Kawasaki
2010-03-05 12:46 ` Ben Hutchings [this message]
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=1267793179.2819.328.camel@localhost \
--to=ben@decadent.org.uk \
--cc=dwmw2@infradead.org \
--cc=ken_kawasaki@spring.nifty.jp \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).