Re: Agere Hermes source-code: copyright situation

[Dave]

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.

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/