netdev - Re: alx unification project dead

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <CAB=NE6Uco7tMVFdYtm8gWC66exhAaf4s=PdKuvz+1j7Dg_PpZg@mail.gmail.com>
Date:	Mon, 1 Jul 2013 14:24:27 -0700
From:	"Luis R. Rodriguez" <mcgrof@...not-panic.com>
To:	piruthiviraj natarajan <piruthiviraj@...il.com>
Cc:	"backports@...r.kernel.org" <backports@...r.kernel.org>,
	"unified-drivers@...ts.infradead.org" 
	<unified-drivers@...ts.infradead.org>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: alx unification project dead

On Wed, Jun 19, 2013 at 5:12 PM, piruthiviraj natarajan
<piruthiviraj@...il.com> wrote:
> On Thu, Jun 20, 2013 at 3:05 AM, Luis R. Rodriguez
> <mcgrof@...not-panic.com> wrote:
>> Given no one worked on pushing this driver upstream... Johannes Berg
>> has posted alx for integration upstream, and his changes pushed the
>> driver under the GPLv2. This project is now dead.
>>
> Is there a possiblity for this driver to move to Linux kernel?

Its now merged upstream as part of the Linux kernel but that driver
was modified a bit to get cleaned up given the Linux alx upstreaming
effort was dropped. The driver was cleaned up by Johannes Berg and
relicensed to GPLv2 or later. I just kicked out a backports release
that lets you use the new upstreamed driver:

https://www.kernel.org/pub/linux/kernel/projects/backports/2013/06/18/backports-20130618.tar.bz2

Please try that!

The QCA alx team, or anyone wishing to fix bugs, should use the new
upstreamed driver for future fixes / enhancements / etc.

> There are practically users who don't care about FreeBSD anyway.

This is not true! FreeBSD has many users and lets recall that the
reason we wanted to work on this approach was to help pave the way as
an approach to help kill proprietary drivers, which are simply
grotesque and the reason why tons of original driver code is simply an
engineering reckless mess. Device driver development *cannot* and
*should not* be left up to corporations to lead. This effort failed
simply because we lacked assigned resources to work on this both on
the FreeBSD and on the final stretch of Linux upstreaming, the general
groundwork and ideas are there though and as far as I can tell I think
a few companies got the hint and hopefully are looking into this as a
future venue. BSD folks can simply use the external unified tree now
to port the driver to BSD but given the license divergence the alx
driver on Linux will remain GPLv2 or later and fixes / enhancements as
well, as such the drivers will unfortunately diverge.

The ideas expressed on this e-mail are my own and in no way shape or
form represent who I work for.

  Luis
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html