From: Dirk Steuwer <dirk@steuwer.de>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux Hardware Quality Labs (was: Linux in a binary world... a doomsday scenario)
Date: Thu, 8 Dec 2005 09:23:58 +0000 (UTC) [thread overview]
Message-ID: <loom.20051208T101830-768@post.gmane.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0512080044350.28203@shell4.speakeasy.net>
Vadim Lobanov <vlobanov <at> speakeasy.net> writes:
>
> On Thu, 8 Dec 2005, Nicolas Mailhot wrote:
>
> > Felix Oxley wrote:
> > A good exhaustive online centralised hardware database, blessed and
> > maintained by kernel people, will have influence with or without a logo.
>
> I don't think this is quite right.
>
> The beauty of having a simple and easily-recognizable logo plastered on
> a website or product box or what have you is exactly that -- simplicity.
> That's a good thing, because it means that the person looking to
> purchase some bit of hardware can merely look for that one sign, and
> it'll be "guaranteed" to work.
>
> Simplicity is a very good thing, in this case -- the easier it is for a
> consumer to check/notice/comprehend something, the more likely they are
> to use it and put value into that process. This leads to greater
> mindshare for that logo. And besides, there are some cases where an
> online database does not help you much: for example, if you find
> yourself shopping in a brick-and-mortar store.
>
> An online database is definitely a very useful thing to have, for those
> who know to look for it, and who can look at it. But aside from that, a
> simple logo is what the vast majority of people wishing to purchase
> hardware would benefit from the most.
>
Sorry for posting this in the other thread, so heres my list again, (i'm pretty
much in favour of felix' scenario):
- get all open operating system folks to join
- have an approval organisation, that everyone is happy with
- lets call it "free driver" support
- create apropriate Logos for each operating system i.e. "Penguin-Logo"
with "free driver since kernel-a.b.c.d" or "BSD-Daemon-Logo" with "free driver
since a.b"
- the hardware version numer (usb-device id, pci-id)? will be held in a
database.
If in doubt people can look it up there. In case future kernels will
drop support, it can be marked there as well.
A yearly logo is too much
confusion, since hardware support for open drivers stays pretty long in
the kernel. (Imagine you license in december - you only got a month...)
Maybe educate people that support for kernel 2.6.x.y series means a
penguin logo on blue ground.
If dramatic changes to the kernel are introduced, which all
drivers affect call the kernel 2.8.x.y an educate people about a new linux
in town and create a penguin logo on yellow ground
- hardware vendors pay someone, or provide source code themselves
to be reviewed by apropriate kernel folks/bsd board...
- small licence fee and endless advertising possiblilities pay for
organisation folks and hosting.
Keeping up database records could help kernel developers:
There could be a log file attached to each device stating the
current affairs about support in varying OSs
Felix had a good senario for financing this, it should be an independend body
providing legal/licensing and marketing support. And the kernel folks should do
the technical review.
dirk
next prev parent reply other threads:[~2005-12-08 9:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-07 23:53 Felix Oxley
2005-12-08 7:43 ` Nicolas Mailhot
2005-12-08 8:53 ` Vadim Lobanov
2005-12-08 9:23 ` Dirk Steuwer [this message]
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=loom.20051208T101830-768@post.gmane.org \
--to=dirk@steuwer.de \
--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
Powered by JetHome