On Thu, 2005-06-02 at 13:49 -0400, Nathanael Nerode wrote:
> Andres Salomon wrote:
[...]
> >
> > I haven't bothered looking at other drivers in the tree that support
> > firmware loading; are paths hardcoded in there, or is the firmware
> > location simply a module/kernel arg?
> Hardcoded, consist
Andres Salomon wrote:
> Yes, that's what I was thinking. Vendors will be taking care of
> firmware file installation; kbuild should be handling it when running
> modules_install. Perhaps a firmware_install target that takes care of
> the various firmware blobs?
Sounds good.
> I can do that, if n
On Thu, 2005-06-02 at 10:37 -0400, Nathanael Nerode wrote:
> Taking off debian-legal, since this is so not legal discussion anymore.
>
> Andres Salomon wrote:
> > > I think they said they'd accept a patch which loaded the firmware but fell
> > > back to firmware built into the kernel if it wasn't
Taking off debian-legal, since this is so not legal discussion anymore.
Andres Salomon wrote:
> > I think they said they'd accept a patch which loaded the firmware but fell
> > back to firmware built into the kernel if it wasn't present, as a
> > "transitional" requirement. Ugh squared. But I ca
On Tue, 31 May 2005 22:32:30 -0400, Nathanael Nerode wrote:
> Andres Salomon wrote:
>> As I remember, upstream (jgarzik/davem) was not overly interested in such
>> a patch to tg3. Is this still the case, or are they amenable to such
>> changes?
>
> Upstream was not interested in legal niceties li
On Tue, May 31, 2005 at 11:24:12AM -0400, Andres Salomon wrote:
> On Sun, 29 May 2005 05:48:55 -0400, Nathanael Nerode wrote:
> [...]
> > Great! This license is totally distributable. I'm not sure,
> > unfortunately,
> > what counts as "equivalent" to hexadecimal. I think that's the only
> >
Andres Salomon wrote:
> As I remember, upstream (jgarzik/davem) was not overly interested in such
> a patch to tg3. Is this still the case, or are they amenable to such
> changes?
Upstream was not interested in legal niceties like including copyright
statements, either. I suppose both are still t
On Sun, 29 May 2005 05:48:55 -0400, Nathanael Nerode wrote:
[...]
> Great! This license is totally distributable. I'm not sure, unfortunately,
> what counts as "equivalent" to hexadecimal. I think that's the only problem.
>
> If it was just "permission to distribute, unmodified, in any form"
On Sun, May 29, 2005 at 05:48:55AM -0400, Nathanael Nerode wrote:
> Before you move the whole driver to non-free, you should know that I have
> made
> a version of the driver which loads the firmware from files if it is
> available (many tg3 users don't *need* the firmware), and I believe that i
Sven Luther wrote:
> The text of the new licence proposal is as follows :
>
> > +/* xxx.h: Broadcom tg3 network driver.
> > + *
> > + * Copyright (c) 2004, 2005 Broadcom Corporation
> > + *
> > + * This program is free software; you can redistribute it and/or modify
> > + * it under the terms of t
On 5/25/05, Sven Luther <[EMAIL PROTECTED]> wrote:
> It would then follow that you need to specify an appropriate licence for
> distribution of the non-free firmware blob, which was ok i believe in the
> original proposal :
>
> Permission is hereby granted for the distribution of this firmware da
Hi Sven,
On Wed, May 25, 2005 at 09:28:23PM +0200, Sven Luther wrote:
> It seems our crusade to solve the dubious licencing of firmware inside the
> linux kernel source is starting to show is fruits. After the QLogic feedback
> Andres Salomon reported in a previous mail, it is now Broadcom which
On Wed, May 25, 2005 at 12:59:27PM -0700, Michael K. Edwards wrote:
> Under US law as I understand it (IANAL), the text in my follow-up to
> Andres's QLogic thread is cleaner. I would not recommend pretending
> that the embedded firmware image is exclusively "data"; it is a
> separately copyrighte
Under US law as I understand it (IANAL), the text in my follow-up to
Andres's QLogic thread is cleaner. I would not recommend pretending
that the embedded firmware image is exclusively "data"; it is a
separately copyrighted work whose bytes are treated as data by the
driver. The driver is part of
Hello all,
It seems our crusade to solve the dubious licencing of firmware inside the
linux kernel source is starting to show is fruits. After the QLogic feedback
Andres Salomon reported in a previous mail, it is now Broadcom which is coming
back to us with a licence proposal.
Keep in mind that
15 matches
Mail list logo
