linux-kernel - Re: Free Linux Driver Development!

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20070130214759.GA12477@kroah.com>
Date:	Tue, 30 Jan 2007 13:47:59 -0800
From:	Greg KH <greg@...ah.com>
To:	Roland Dreier <rdreier@...co.com>
Cc:	Jeff Garzik <jeff@...zik.org>, linux-kernel@...r.kernel.org
Subject: Re: Free Linux Driver Development!

On Tue, Jan 30, 2007 at 01:38:06PM -0800, Roland Dreier wrote:
>  > > OK, but why isn't your army of volunteers fixing them?
>  > 
>  > Because nobody has hardware for them?
> 
> Greg said hardware wasn't necessary...

Someone has to have the hardware to test with.  Hence my "debug by
email" comment.

> Sure, popular hardware support is pretty good.  But there are still
> pretty serious gaps, for example Ralink wireless drivers are still not
> upstream even with the vendor trying to help (and I think Ralink
> wireless is a good example of how we can't really keep the promises
> Greg is making).

The Ralink wireless drivers are working to get their stuff upstream.  I
think there is only some wireless infrastructure needed to complete
before it gets into mainline, but you will have to ask them about this.

There was a wireless-mini-summit a week or so ago, so those developers
all know what is going on in that space right now.  They are facing a
number of different regulatory issues, combined with lack of
specifications from some vendors.  I don't think that the developers who
actually have specs are complaining about anything right now.

> And there's plenty of stuff in-tree with lots of users that's in
> pretty dire shape, like ISDN (and the fact that we still
> CONFIG_ISDN_I4L).  OK, it's not "modern" but Greg is also promising
> that we'll keep everything up-to-date with any upstream kernel
> changes, and there's obviously large chunks of the driver tree where
> that doesn't happen.

The ISDN maintainer has a large rewrite almost done, and anyone is
welcome to help him out if they are still using and needing that old
hardware.  As almost no one objects to the current code, I'm guessing
that there is no such real need :)

thanks,

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