* Re: [PATCH kernel 2.6.32-rc5] pcnet_cs: add cis of PreMax PE-200 ethernet pcmcia card
@ 2009-10-25 2:10 Ken Kawasaki
2009-10-25 2:13 ` Ben Hutchings
2010-03-05 0:02 ` Ben Hutchings
0 siblings, 2 replies; 6+ messages in thread
From: Ken Kawasaki @ 2009-10-25 2:10 UTC (permalink / raw)
To: netdev; +Cc: ben
Hi,
>> > Random question: are CIS files copyrightable?
>>
>> The CIS contains the IRQ, ioport-range, voltage information etc
>> like the PCI config space.
>> So I think it is not copyrightable.
>> but Sierra Wireless provided this CIS by GPL.
>[...]
>If it is subject to copyright - which apparently they think it is - then
>when redistributing under GPL we must be able to provide the 'preferred
>form for modification'. So that leads to the question, is this blob or
>hex file the preferred form?
(1)The CIS contains data only,
does not contain the code to be executed.
(2)Sierra Wireless provided the binary of the CIS only.
(3)These CIS are stable and does not need to be modified.
(3)The content of the CIS can be seen by the dump_cis utility.
So if someone want to modify the CIS , I think it is OK
to use hex editor.
Best Regards
Ken
^ permalink raw reply [flat|nested] 6+ messages in thread* Re: [PATCH kernel 2.6.32-rc5] pcnet_cs: add cis of PreMax PE-200 ethernet pcmcia card
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
1 sibling, 0 replies; 6+ messages in thread
From: Ben Hutchings @ 2009-10-25 2:13 UTC (permalink / raw)
To: Ken Kawasaki; +Cc: netdev
[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]
On Sun, 2009-10-25 at 11:10 +0900, Ken Kawasaki wrote:
> Hi,
>
> >> > Random question: are CIS files copyrightable?
> >>
> >> The CIS contains the IRQ, ioport-range, voltage information etc
> >> like the PCI config space.
> >> So I think it is not copyrightable.
> >> but Sierra Wireless provided this CIS by GPL.
> >[...]
>
> >If it is subject to copyright - which apparently they think it is - then
> >when redistributing under GPL we must be able to provide the 'preferred
> >form for modification'. So that leads to the question, is this blob or
> >hex file the preferred form?
>
>
> (1)The CIS contains data only,
> does not contain the code to be executed.
> (2)Sierra Wireless provided the binary of the CIS only.
> (3)These CIS are stable and does not need to be modified.
> (3)The content of the CIS can be seen by the dump_cis utility.
>
> So if someone want to modify the CIS , I think it is OK
> to use hex editor.
That sounds reasonable. Thanks.
Ben.
--
Ben Hutchings
The obvious mathematical breakthrough [to break modern encryption] would be
development of an easy way to factor large prime numbers. - Bill Gates
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH kernel 2.6.32-rc5] pcnet_cs: add cis of PreMax PE-200 ethernet pcmcia card
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
1 sibling, 1 reply; 6+ messages in thread
From: Ben Hutchings @ 2010-03-05 0:02 UTC (permalink / raw)
To: Ken Kawasaki; +Cc: netdev, David Woodhouse
[-- Attachment #1: Type: text/plain, Size: 1710 bytes --]
On Sun, 2009-10-25 at 11:10 +0900, Ken Kawasaki wrote:
> Hi,
>
> >> > Random question: are CIS files copyrightable?
> >>
> >> The CIS contains the IRQ, ioport-range, voltage information etc
> >> like the PCI config space.
> >> So I think it is not copyrightable.
> >> but Sierra Wireless provided this CIS by GPL.
> >[...]
>
> >If it is subject to copyright - which apparently they think it is - then
> >when redistributing under GPL we must be able to provide the 'preferred
> >form for modification'. So that leads to the question, is this blob or
> >hex file the preferred form?
>
>
> (1)The CIS contains data only,
> does not contain the code to be executed.
> (2)Sierra Wireless provided the binary of the CIS only.
> (3)These CIS are stable and does not need to be modified.
> (3)The content of the CIS can be seen by the dump_cis utility.
>
> So if someone want to modify the CIS , I think it is OK
> to use hex editor.
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.
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 --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: [PATCH kernel 2.6.32-rc5] pcnet_cs: add cis of PreMax PE-200 ethernet pcmcia card
2010-03-05 0:02 ` Ben Hutchings
@ 2010-03-05 11:21 ` Ken Kawasaki
2010-03-05 12:01 ` Ken Kawasaki
0 siblings, 1 reply; 6+ messages in thread
From: Ken Kawasaki @ 2010-03-05 11:21 UTC (permalink / raw)
To: Ben Hutchings; +Cc: netdev, David Woodhouse
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 /lib/firmware/cis/src/xxx.cis"
instead of "IHEX /lib/firmware/cis/xxx.cis".
In that case, the "pack_cis" tool should be included in the kernel-tree.
Ken.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re:[PATCH kernel 2.6.32-rc5] pcnet_cs: add cis of PreMax PE-200 ethernet pcmcia card
2010-03-05 11:21 ` Ken Kawasaki
@ 2010-03-05 12:01 ` Ken Kawasaki
2010-03-05 12:46 ` Ben Hutchings
0 siblings, 1 reply; 6+ messages in thread
From: Ken Kawasaki @ 2010-03-05 12:01 UTC (permalink / raw)
To: Ben Hutchings; +Cc: netdev, David Woodhouse
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.
Ken.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Re:[PATCH kernel 2.6.32-rc5] pcnet_cs: add cis of PreMax PE-200 ethernet pcmcia card
2010-03-05 12:01 ` Ken Kawasaki
@ 2010-03-05 12:46 ` Ben Hutchings
0 siblings, 0 replies; 6+ messages in thread
From: Ben Hutchings @ 2010-03-05 12:46 UTC (permalink / raw)
To: Ken Kawasaki; +Cc: netdev, David Woodhouse
[-- 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 --]
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2010-03-05 12:46 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 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).