From: Willy Tarreau <w@1wt.eu>
To: linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Position Statement on Linux Kernel Modules
Date: Mon, 23 Jun 2008 15:09:17 +0200 [thread overview]
Message-ID: <20080623130917.GB1369@1wt.eu> (raw)
In-Reply-To: <20080623112934.GC5713@hp0.dynamicro.ca>
On Mon, Jun 23, 2008 at 07:29:34AM -0400, Greg Louis wrote:
> On 20080622 (Sun) at 2201:18 -0700, Greg KH wrote:
> >
> > If there are any kernel developers who want to add their names to this
> > statement, please let me know by private email and I will be glad to add
> > it.
> >
> > Position Statement on Linux Kernel Modules
> > June 2008
> >
> > We, the undersigned Linux kernel developers...
>
> Do you think it might be a good idea to start a similar list, in the
> form of a petition to manufacturers, for end users? The hope would be
> that the number of petitioners grow big enough to let us effectively
> rebut the argument that nobody outside the developer community really
> cares.
>
> (Of course, the best way to rebut that argument would be for end-users
> to vote with their feet, but for a lot of us, me included, that's not a
> practical option.)
The problem is exactly what you describe in your last sentence. Hardware
manufacturers are well aware of that and make no effort to provide correct
drivers when they (think they) have a monopoly in certain areas.
What would be needed would be a public list of alternative hardware for
known existing hardware. When big manufacturers will see their hardware
listed there in the "bad" column, with their small competitors on the
same line in the "good" column and with a lower price, they may start
to think a little bit. Also, small manufacturers could use this for
marketting purposes, because they would be listed as direct competitors
for other well-established products.
It should be made with notebooks too. It's a shame to see how you're
nearly forced to have an nvidia graphics card in a notebook nowadays.
It is needed to put a bad reputation to products which embed closed
hardware, and to give a good one to other ones.
If such a list is exhaustive and public, it may become a reference for
new buyers.
Willy
next prev parent reply other threads:[~2008-06-23 13:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-23 5:01 Greg KH
2008-06-23 10:00 ` Jiri Kosina
2008-06-23 14:24 ` Greg KH
2008-06-23 11:29 ` Greg Louis
2008-06-23 13:09 ` Willy Tarreau [this message]
2008-06-24 11:33 ` Greg Louis
2008-06-24 15:02 ` David Newall
2008-06-23 18:12 ` Greg KH
2008-06-23 18:15 ` Måns Rullgård
2008-06-23 13:02 Matthew
2008-06-23 13:21 ` Willy Tarreau
2008-06-25 22:45 ` jdow
2008-06-25 23:11 ` Willy Tarreau
2008-06-28 3:28 ` jdow
2008-06-23 18:11 ` Greg KH
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=20080623130917.GB1369@1wt.eu \
--to=w@1wt.eu \
--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®