public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Mailhot <nicolas.mailhot@laposte.net>
To: Felix Oxley <lkml@oxley.org>
Cc: linux-kernel@vger.kernel.org,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	Arjan van de Ven <arjan@infradead.org>,
	Jesse Barnes <jesse.barnes@intel.com>,
	Pekka Enberg <penberg@cs.helsinki.fi>,
	Jon Masters <jonmasters@gmail.com>,
	Grahame White <grahame@regress.homelinux.org>,
	Benjamin LaHaise <bcrl@kvack.org>,
	"Randy.Dunlap" <rdunlap@xenotime.net>,
	Lars Marowsky-Bree <lmb@suse.de>,
	"linux-os ((Dick Johnson))" <linux-os@analogic.com>,
	Rik van Riel <riel@redhat.com>, Dirk Steuwer <dirk@steuwer.de>,
	Andrea Arcangeli <andrea@suse.de>,
	Lee Revell <rlrevell@joe-job.com>
Subject: Re: Linux Hardware Quality Labs (was: Linux in a binary world... a doomsday scenario)
Date: Thu, 08 Dec 2005 08:43:35 +0100	[thread overview]
Message-ID: <4397E427.2070702@laposte.net> (raw)
In-Reply-To: <6DAD0850-4943-416E-9E7B-095C6B412DD0@oxley.org>

Felix Oxley wrote:

> Unlike previous lists of equipment that works with Linux, this would of
> course have to be centrally administered.
> Simply, hardware manufacturers would be able to use the LHQL logo
> (whatever it looks like or is called) once their kit had been certified,
> the primary requirement for which would be either that a  fully featured
> open source driver was available or that all the relevant documentation
> had been put in to the public domain so that anybody could write one.

I think the current focus on the logo idea is pretty sad. The only real
"feature" a logo adds is it will have to be maintained by Someone Else.
Which is always nice. Except when the real info is in the kernel
maintainers heads, as is the real love of free software, being
maintained by Someone Else means it'll fail.

A good exhaustive online centralised hardware database, blessed and
maintained by kernel people, will have influence with or without a logo.

A pretty logo/HQL program without kernel people involvement will fail
quickly.

The problem with maintaining your own database is its a lot of work (as
Lee Revell pointed). However, if kernel people don't want the system to
be abused, distorted, etc they'll have to make this effort.

Kernel people complain users don't buy the right hardware, but they
don't bother pointing out which hardware is good. I'm pretty sure when
*they* buy new systems they don't do the long hours of googling and ML
analysis they'd want the users to perform (because right now that's what
needed to find out which hardware is linux-friendly)

Also, kernel people use the power of the internet all day round but put
their faith in a paper logo. Which is pretty ridiculous. Give users a
good database and they won't need the paper thingy (not to mention
drivers are completed after hardware ships, so all the already-packaged
hardware won't get a linux logo by magic)

Regards,

-- 
Nicolas Mailhot

  reply	other threads:[~2005-12-08  7:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-07 23:53 Linux Hardware Quality Labs (was: Linux in a binary world... a doomsday scenario) Felix Oxley
2005-12-08  7:43 ` Nicolas Mailhot [this message]
2005-12-08  8:53   ` Vadim Lobanov
2005-12-08  9:23     ` Dirk Steuwer
2005-12-08  9:57       ` Chris White
2005-12-08 10:54         ` Dirk Steuwer
2005-12-09  1:48           ` Felix Oxley
2005-12-08 10:26   ` Felix Oxley
2005-12-08 10:46     ` Dirk Steuwer
2005-12-08 11:12       ` Felix Oxley
2005-12-08 10:51     ` Al Viro
2005-12-08 14:15 ` Dirk Steuwer
     [not found] ` <20051208153930.GB12808@kvack.org>
2005-12-09  1:09   ` Felix Oxley

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=4397E427.2070702@laposte.net \
    --to=nicolas.mailhot@laposte.net \
    --cc=andrea@suse.de \
    --cc=arjan@infradead.org \
    --cc=bcrl@kvack.org \
    --cc=dirk@steuwer.de \
    --cc=geert@linux-m68k.org \
    --cc=grahame@regress.homelinux.org \
    --cc=jesse.barnes@intel.com \
    --cc=jonmasters@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-os@analogic.com \
    --cc=lkml@oxley.org \
    --cc=lmb@suse.de \
    --cc=penberg@cs.helsinki.fi \
    --cc=rdunlap@xenotime.net \
    --cc=riel@redhat.com \
    --cc=rlrevell@joe-job.com \
    /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