From: Hans de Goede <hdegoede@redhat.com>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: "Arend Van Spriel" <arend.vanspriel@broadcom.com>,
linux-wireless <linux-wireless@vger.kernel.org>,
"Rafał Miłecki" <rafal@milecki.pl>
Subject: Re: brcmfmac: don't warn user if requested nvram fails
Date: Sun, 30 Apr 2017 21:39:43 +0200 [thread overview]
Message-ID: <3ca61682-7267-c87b-2c3e-e4c185134cba@redhat.com> (raw)
In-Reply-To: <20170427003616.GD28800@wotan.suse.de>
Hi,
On 27-04-17 02:36, Luis R. Rodriguez wrote:
> On Tue, Apr 11, 2017 at 10:53:57AM +0200, Hans de Goede wrote:
<snip>
>>>> Right, sorry. For the pcie device I'm looking at the
>>>> name is brcmfmac4356-pcie.txt and I would like to propose
>>>> to first check for "brcmfmac4356-<pci-subsys-vid>-<pci-subsys-pid>.txt"
>>>>
>>>>> So who is going to provide these nvram files. We can not
>>>>> maintain that as there are too many variants and they are under control
>>>>> of the OEM/ODM.
>>>>
>>>> Users / people like me who are interested in using certain
>>>> devices with Linux. The idea is to at least make it possible to
>>>> have these devices just work. E.g. I would like a user to be
>>>> able to insert a USB-stick with a live Fedora 27 and then
>>>> have everything just work on the GPD win.
>>>>
>>>> To make this happen I will submit the nvram file from the
>>>> Windows install on the GPDwin to linux-firmware as
>>>> "brcmfmac4356-<pci-subsys-vid>-<pci-subsys-pid>.txt"
>>>> and yes I've checked that there are sensible values in
>>>> the subsys ids.
>>>
>>> I suppose the "nvram file from the Windows install" than has a
>>> redistributable license?
>>
>> IANAL but I fail to see how the contents of this file is
>> anything but functional and as such not copyright-able.
>
> We take licensing serious on linux-firmware, a IANAL is no excuse for
> being sloppy.
I don't mean to be sloppy. As I already stated I plan to make it
clear in the commit msg that there is no license info for the nvram
file and that in my non expert opinion that is not a problem.
If people disagree then we will likely need to ask an actual lawyer
for advice and see from there,
Regards,
Hans
next prev parent reply other threads:[~2017-04-30 19:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-06 12:14 brcmfmac: don't warn user if requested nvram fails Hans de Goede
2017-04-07 21:43 ` Arend Van Spriel
2017-04-08 9:53 ` Hans de Goede
2017-04-10 21:50 ` Arend Van Spriel
2017-04-11 8:53 ` Hans de Goede
2017-04-27 0:36 ` Luis R. Rodriguez
2017-04-30 19:39 ` Hans de Goede [this message]
2017-05-01 8:57 ` Arend van Spriel
2017-06-26 18:16 ` Rafał Miłecki
2017-04-27 0:45 ` Luis R. Rodriguez
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=3ca61682-7267-c87b-2c3e-e4c185134cba@redhat.com \
--to=hdegoede@redhat.com \
--cc=arend.vanspriel@broadcom.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@kernel.org \
--cc=rafal@milecki.pl \
/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).