netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Ken Kawasaki <ken_kawasaki@spring.nifty.jp>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH  kernel 2.6.32-rc5] pcnet_cs: add cis of PreMax PE-200 ethernet pcmcia card
Date: Sun, 25 Oct 2009 02:13:29 +0000	[thread overview]
Message-ID: <1256436809.2510.0.camel@localhost> (raw)
In-Reply-To: <20091025111000.2d97e595.ken_kawasaki@spring.nifty.jp>

[-- 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 --]

  reply	other threads:[~2009-10-25  2:13 UTC|newest]

Thread overview: 11+ 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2009-04-05  0:49 [PATCH] axnet_cs: fix phy_id detection for bogus Asix chip Ken Kawasaki
2009-04-18 23:44 ` [PATCH] pcnet_cs: add cis(firmware) of the Allied Telesis LA-PCM Ken Kawasaki
2009-04-26  7:29   ` [PATCH] 3c589_cs: add cis(firmware) of 3Com multifunction pcmcia card Ken Kawasaki
2009-09-13  8:22     ` [PATCH kernel 2.6.31] pcnet_cs: add cis of Linksys " Ken Kawasaki
2009-10-03 22:32       ` [PATCH kernel 2.6.32-rc1] pcnet_cs: add cis of National Semicondoctor's " Ken Kawasaki
2009-10-18  1:39         ` [PATCH kernel 2.6.32-rc5] pcnet_cs: add cis of PreMax PE-200 ethernet " Ken Kawasaki
2009-10-21 19:18           ` Dan Williams
2009-10-22 11:10             ` Ken Kawasaki
2009-10-24 20:33               ` Ben Hutchings
2009-10-30  5:51           ` 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=1256436809.2510.0.camel@localhost \
    --to=ben@decadent.org.uk \
    --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).