linux-kernel - Re: Driver model.. expel legacy drivers?

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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <73CDF2F1-EC0A-431D-9B29-10251FAD21B7@sbcglobal.net>
Date:	Sat, 14 Oct 2006 20:24:46 -0500
From:	Kevin K <k_krieser@...global.net>
To:	linux-kernel@...r.kernel.org
Subject: Re: Driver model.. expel legacy drivers?

On Oct 14, 2006, at 6:51 PM, John Richard Moser wrote:

>
>> Microsoft are also being very helpful. They are making it harder and
>> harder for people to use drivers not microsoft-signed which in turns
>> pushes up costs for development and as a result encourages more
>> standardization of driver interfaces to take place.
>
> huh?
>

My assumption is that vendors may make fewer gratuitious interface  
changes so the hardware is more likely to work with existing, signed,  
drivers.  If changes aren't made, existing Linux drivers are more  
likely to work with new revisions of hardware.

My experience in the past for hardware, such as USB based flash  
memory readers, is that when they came out you seemed to always need  
a proprietary driver, and Linux drivers needed hints for different  
readers.  It seems better these days, with things like USB keys  
generally working in both Windows and relatively modern distributions  
without much effort.llin
-
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/