| 1 |
On Thu, Feb 21, 2013 at 09:44:12PM +0100, Ulrich Mueller wrote: |
| 2 |
> >>>>> On Thu, 21 Feb 2013, Greg KH wrote: |
| 3 |
> |
| 4 |
> > Has anyone asked the upstream linux-firmware developers about these |
| 5 |
> > files? |
| 6 |
> |
| 7 |
> I don't know. I haven't, for my part. But maybe we should first try |
| 8 |
> to produce a more complete list, instead of reporting each file |
| 9 |
> separately? Given that most of the files are being distributed since |
| 10 |
> years, another few days cannot matter. |
| 11 |
|
| 12 |
Such a list would be wonderful to have. |
| 13 |
|
| 14 |
> > thanks for the detailed descriptions, much appreciated. |
| 15 |
> |
| 16 |
> > I think this is something that the Board needs to decide, after |
| 17 |
> > discussing it with our lawyers, it's not something that non-legal |
| 18 |
> > people (like myself) should be saying is the definitive answer. |
| 19 |
> |
| 20 |
> I fully agree. And IANAL, so anything that I say about license issues |
| 21 |
> should be taken with a grain of salt. |
| 22 |
|
| 23 |
I am willing to work with lawyers, who know these type of things quite |
| 24 |
well, to get upstream straightened out, given that I was the one who |
| 25 |
originally added firmware files to the kernel, oh so many years ago, |
| 26 |
causing this problem... |
| 27 |
|
| 28 |
This should be a cross-distro issue/solution, so I suggest working with |
| 29 |
the Linux Foundation on this. Anyone object to me doing that? |
| 30 |
|
| 31 |
thanks, |
| 32 |
|
| 33 |
greg k-h |
Archives