linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave <kilroyd@googlemail.com>
To: Greg KH <greg@kroah.com>
Cc: TJ <linux@tjworld.net>, Andrey Borzenkov <arvidjaar@mail.ru>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"Casual J. Programmer" <casualprogrammer@googlemail.com>,
	linux-wireless@vger.kernel.org
Subject: Re: Agere Hermes source-code: copyright situation
Date: Thu, 02 Oct 2008 00:00:10 +0100	[thread overview]
Message-ID: <48E400FA.2090305@gmail.com> (raw)
In-Reply-To: <20081001200039.GA29874@kroah.com>

Greg KH wrote:
> On Wed, Oct 01, 2008 at 05:40:29PM +0100, TJ wrote:
>> On Wed, 2008-10-01 at 14:13 +0400, Andrey Borzenkov wrote:
>>>On Wednesday 01 October 2008, Greg KH wrote:
>>>> On Mon, Sep 29, 2008 at 09:49:34AM +0400, Andrey Borzenkov wrote:
>>>>> I have here driver that can be built for two different types of
>>>>> hardware from basically the same sources (this is port of old Agere
>>>>> drivers for Hermes-I/Hermes-II chipsets).
>>>> 
>>>> Cool, do you have a link to the code, I'd be glad to add it to
>>>> drivers/staging/ if it's not in a fully-mergable state yet to get wider
>>>> users for it.
>>>
>>> You can look at it here: http://arvidjaar.newmail.ru/wlags49.tar.bz
>>>
>>> I doubt that it is suitable for inclusion at current state if ever.
>>> This is taken directly from Agere 2.4 sources; the only parts that were
>>> touched are kernel glue and wireless extensions interface.
>>>
>>> And it is not GPL'ed, of course. I attach E-Mail I received a while
>>> back with answere from Agere legal department.
>>
>> I'm attaching the original email I sent to Agere and their response for
>> the record, hoping it helps clarify the legal position.
> 
> Very nice, thanks for forwarding this on.
> 
> As the license is BSD, that means we can place it in the kernel tree.
> Do you all mind if I add it to the drivers/staging/ directory so you can
> work on cleaning it up within the main kernel tree infrastructure?

(cc'ing linux-wireless)

FYI, Hermes I hardware is already covered by the orinoco driver. WPA and firmware download functionality (which is supported by the Agere driver, but not orinoco in 2.6.27) is already in the wireless queue for 2.6.28.

This leaves Hermes-II (and USB?) hardware which orinoco does not support, but could if someone had access to a card for development.


Regards,

Dave.


       reply	other threads:[~2008-10-01 23:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200809290949.35749.arvidjaar@mail.ru>
     [not found] ` <20081001031907.GA19181@kroah.com>
     [not found]   ` <200810011413.17059.arvidjaar@mail.ru>
     [not found]     ` <1222879229.17264.4.camel@hephaestion>
     [not found]       ` <20081001200039.GA29874@kroah.com>
2008-10-01 23:00         ` Dave [this message]
2008-10-02  2:37           ` Agere Hermes source-code: copyright situation Andrey Borzenkov
2008-10-02 17:44             ` Dave
2008-10-02 20:00             ` Greg KH
2008-10-02 20:31               ` Dan Williams
2008-10-02 20:37                 ` Greg KH
2008-10-02 21:28                   ` Dan Williams

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=48E400FA.2090305@gmail.com \
    --to=kilroyd@googlemail.com \
    --cc=arvidjaar@mail.ru \
    --cc=casualprogrammer@googlemail.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linux@tjworld.net \
    /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).