public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kasper Sandberg <lkml@metanurb.dk>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: John Richard Moser <nigelenki@comcast.net>,
	Kevin K <k_krieser@sbcglobal.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Driver model.. expel legacy drivers?
Date: Mon, 16 Oct 2006 11:39:46 +0200	[thread overview]
Message-ID: <1160991586.10100.6.camel@localhost> (raw)
In-Reply-To: <1160922815.5732.54.camel@localhost.localdomain>

On Sun, 2006-10-15 at 15:33 +0100, Alan Cox wrote:
> Ar Sad, 2006-10-14 am 19:51 -0400, ysgrifennodd John Richard Moser:
> > > 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?
> 
> Every vendor of products for Microsoft Windows (which is still the
> primary market for all their hardware) has to provide drivers or work
> with pre-existing drivers. The harder Microsoft makes it (in financial
> terms) for them to produce drivers the more incentive they have to use
> the existing standards or to create new ones.
that makes very much sense, theres just one thing i dont understand.

when there is an established standard, how can it EVER be in a companys
best interrest to develop a new product that doesent use it, and thereby
requires the development of new drivers, the distributing of those
drivers, and all that sort?
> 
> Alan
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


  reply	other threads:[~2006-10-16  9:40 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-14  3:18 Driver model.. expel legacy drivers? 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
2006-10-15  1:51               ` Alistair John Strachan
2006-10-15 14:33             ` Alan Cox
2006-10-16  9:39               ` Kasper Sandberg [this message]
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=1160991586.10100.6.camel@localhost \
    --to=lkml@metanurb.dk \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=k_krieser@sbcglobal.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigelenki@comcast.net \
    /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