From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Tim Gardner <rtg.canonical@gmail.com>,
tim.gardner@canonical.com, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org,
Sri Deevi <Srinivasa.Deevi@conexant.com>,
Palash Bandyopadhyay <Palash.Bandyopadhyay@conexant.com>
Subject: Re: [GIT PULL] linux-firmware: cx23885: update to Version 2.06.139
Date: Tue, 04 Dec 2012 14:35:45 -0200 [thread overview]
Message-ID: <50BE2661.5070603@redhat.com> (raw)
In-Reply-To: <1354597630.17107.42.camel@deadeye.wl.decadent.org.uk>
Em 04-12-2012 03:07, Ben Hutchings escreveu:
> On Mon, 2012-12-03 at 11:13 -0700, Tim Gardner wrote:
>> Ben - what is your policy on extracting firmware from Windows drivers?
>
> I suppose the policy should be that the driver's licence must allow
> extracting and then distributing the result. Which I wouldn't expect
> ever to be the case, in practice.
>
> Your commit message refers to the Hauppuage driver package at
> <http://steventoth.net/linux/hvr1800/HVR-12x0-14x0-17x0_1_25_25271_WHQL.zip>. I didn't find any licence text, other than 'All rights reserved', in either that or the currently distributed version of the same driver <http://www.wintvcd.co.uk/drivers/HVR-12x0-14x0-17x0-33x0-44x0_1_48_29272_SIGNED.zip>.
>
>> It seems like it ought to be OK, and they _are_ the same files that are
>> covered under the license in WHENCE.
>
> I'm not sure how you can say they are the same files, as you're
> proposing to change the contents. The copyright on the current files
> belongs to the chipset vendor, Conexant, and Hauppuage *presumably* used
> firmware supplied by Conexant, but either of them might have chosen a
> different licence for the versions in this driver package.
We shouldn't be replacing the firmwares that Conexant explicitly gave us
the rights to re-distribute by something else extracted from the
Windows drivers without redistribution rights.
Also, AFAIKT, with regards to the firmwares used on ivtv, there is a
license variant that Hauppauge gave to some distros in the past, after
getting Conexant's agreement for that. The terms used there explicitly
forbids redistribution.
So, if any of the existing firmware doesn't work, we should ask
Conexant (c/c) to send us a firmware that works, under the same terms
they gave us in the past, e. g. with redistribution rights.
Regards,
Mauro
prev parent reply other threads:[~2012-12-04 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 18:13 [GIT PULL] linux-firmware: cx23885: update to Version 2.06.139 Tim Gardner
2012-12-04 5:07 ` Ben Hutchings
2012-12-04 16:06 ` Tim Gardner
2012-12-04 16:35 ` Mauro Carvalho Chehab [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=50BE2661.5070603@redhat.com \
--to=mchehab@redhat.com \
--cc=Palash.Bandyopadhyay@conexant.com \
--cc=Srinivasa.Deevi@conexant.com \
--cc=ben@decadent.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=rtg.canonical@gmail.com \
--cc=tim.gardner@canonical.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 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).