From: Gene Heskett <gene.heskett@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/5] Add mkcis - a program that can create .cis from text description
Date: Thu, 23 Sep 2010 12:55:09 -0400 [thread overview]
Message-ID: <201009231255.09443.gene.heskett@gmail.com> (raw)
In-Reply-To: <1285255752.10687.20.camel@i7.infradead.org>
On Thursday, September 23, 2010, David Woodhouse wrote:
>On Thu, 2010-09-23 at 19:19 +0400, Dmitry Eremin-Solenikov wrote:
>> For CIS files (describing hardware on PCMCIA and some other busses)
>> binary file isn't the 'preferred for for modification' in most cases.
>> pcmcia-cs project have developed pack_cis program which can be used
>> (and was used most probably) to generate .cis files from simple text
>> descriptions. Import this code to the kernel under the name of mkcis.
>
>This is useful, thanks -- but NACK. The firmware/ directory of the
>kernel will hopefully die soon, and is no longer what's actually shipped
>by many distributions.
>
>We should be concentrating on the linux-firmware.git repository instead.
Unfortunately, a perusal of that git repo fails to find the amd-microcode
tree, which contains a .bin file that brings my early 4 core phenom up to
revision 65.
I picked that up and have been carrying it forward from a message's link
from this list about 2 years ago, and have been carrying it locally since.
However, I have not seen it mentioned as being used in a dmesg parse since
2.6.35-early-rc.
Is there a good reason for this late apparent lack of using this resource?
Thanks.
--
Cheers, Gene
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
If Microsoft built cars, If you were involved in a crash, you would have
no idea what happened.
next prev parent reply other threads:[~2010-09-23 16:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-23 15:19 [PATCH 1/5] Makefile.fwinst: include Makefile.lib Dmitry Eremin-Solenikov
2010-09-23 15:19 ` [PATCH 2/5] Add mkcis - a program that can create .cis from text description Dmitry Eremin-Solenikov
2010-09-23 15:29 ` David Woodhouse
2010-09-23 15:36 ` Dmitry Eremin-Solenikov
2010-09-23 15:54 ` David Woodhouse
2010-09-23 16:58 ` Wolfram Sang
2010-09-23 16:55 ` Gene Heskett [this message]
2010-09-23 15:19 ` [PATCH 3/5] firmware: enable usage of mkcis Dmitry Eremin-Solenikov
2010-09-23 15:19 ` [PATCH 4/5] firmware: replace ihex files with text descriptions for CIS files Dmitry Eremin-Solenikov
2010-09-23 15:19 ` [PATCH 5/5] Documentation: add an utility to parse CIS files to readable form Dmitry Eremin-Solenikov
2010-09-23 15:45 ` [PATCH 1/5] Makefile.fwinst: include Makefile.lib Sam Ravnborg
-- strict thread matches above, loose matches on Subject: below --
2010-09-24 16:49 [PATCH 0/5] Add programs to work with CIS files Dmitry Eremin-Solenikov
2010-09-24 16:49 ` [PATCH 2/5] Add mkcis - a program that can create .cis from text description Dmitry Eremin-Solenikov
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=201009231255.09443.gene.heskett@gmail.com \
--to=gene.heskett@gmail.com \
--cc=linux-kernel@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