From: Kevin K <k_krieser@sbcglobal.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Driver model.. expel legacy drivers?
Date: Sat, 14 Oct 2006 20:24:46 -0500 [thread overview]
Message-ID: <73CDF2F1-EC0A-431D-9B29-10251FAD21B7@sbcglobal.net> (raw)
In-Reply-To: <45317814.8000709@comcast.net>
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
next prev parent reply other threads:[~2006-10-15 1:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-14 3:18 John Richard Moser
2006-10-14 7:56 ` Adrian Bunk
2006-10-14 11:19 ` James Courtier-Dutton
2006-10-14 15:04 ` John Richard Moser
2006-10-14 18:54 ` Horst H. von Brand
2006-10-14 20:48 ` John Richard Moser
2006-10-15 15:31 ` Jan Engelhardt
2006-10-14 21:14 ` Kevin K
2006-10-14 21:44 ` John Richard Moser
2006-10-15 0:03 ` Alan Cox
2006-10-14 23:51 ` John Richard Moser
2006-10-15 1:24 ` Kevin K [this message]
2006-10-15 1:51 ` Alistair John Strachan
2006-10-15 14:33 ` Alan Cox
2006-10-16 9:39 ` Kasper Sandberg
2006-10-16 14:13 ` Lee Revell
2006-10-16 19:04 ` Lennart Sorensen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=73CDF2F1-EC0A-431D-9B29-10251FAD21B7@sbcglobal.net \
--to=k_krieser@sbcglobal.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®