| 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
| ||
|
Date: Sat, 16 Dec 2006 15:59:52 +1100 From: "Dave Airlie" <airlied@...il.com> To: jdow <jdow@...thlink.net> Cc: "Alexey Dobriyan" <adobriyan@...il.com>, "James Porter" <jameslporter@...il.com>, linux-kernel@...r.kernel.org Subject: Re: Binary Drivers On 12/16/06, jdow <jdow@...thlink.net> wrote: > From: "Alexey Dobriyan" <adobriyan@...il.com> > > > On Fri, Dec 15, 2006 at 09:20:58PM +0000, James Porter wrote: > >> I think some kernel developers take to much responsibility, is there a > >> bug in a > >> binary driver? Send it upstream and explain to the user that it's a > >> closed > >> source driver and is up to said company to fix it. > >> > >> For what it's worth, I don't see any problem with binary drivers from > >> hardware > >> manufacturers. > > > > Binary drivers from hardware manufacturers are crap. Learn it by heart. > > So are the Linux drivers in some cases. My ATI Radeon Mobility video > in my laptop is an example. > Open drivers aren't magic.. if the vendor doesn't give us the information how specific chips are screwed, there isn't anything we can do about it, ATI don't support the open drivers for anything but RN50s from Dell and their support is quite brutal even on those (every patch is a dirty hack...), the thing is with the open drivers we can say hey ATI that is a dirty hack, with the closed ones they just stick it in and ship it.. Dave. - 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/
Powered by blists - more mailing lists