All of lore.kernel.org
 help / color / mirror / Atom feed
From: dirk@steuwer.de
To: <rdunlap@xenotime.net>
To: <riel@redhat.com>
To: <wli@holomorphy.com>
To: <linux-kernel@vger.kernel.org>
To: <arjan@infradead.org>
To: <diegocg@gmail.com>
Subject: AW: Re: Linux in a binary world... a doomsday scenario
Date: Thu, 08 Dec 2005 17:35:41 +0100	[thread overview]
Message-ID: <10607050.147171134059741405.JavaMail.servlet@kundenserver> (raw)

>
>El Thu, 08 Dec 2005 16:49:46 +0100,
>dirk@steuwer.de escribió:
>
>> How about interconnecting it with the bugtracker?
>
>bugzilla is probably the best example of why human-managed "databases"
>are never 100% accurate and need lots of mainteinance 8) (take a look
>at mozilla's or kernel's bugzilla...). I'm tracking manually some 
>of the new devices supported in http://wiki.kernelnewbies.org/LinuxChanges
>but there're so many changes under drivers/* that god knows how many
>things I am missing. Expecting that people will maintain a wiki or a
>buzgilla or anything similar properly is like expecting that people
>will document or compile-test their patches before submitting them :P
>
>I think that the infrastructure for building such database automatically
>is already there: In the same way MODULE_DEVICE_TABLE is used by hotplug
>& friends to load the right module you can use MODULE_DEVICE_TABLE to
>build a database of the devices supported by a kernel compiled with
>"make allmodconfig", parse it and put it in a web page.


OK this would get all device ids into the database, but it would not say anything about how well the device is supported. It could be anything from the moment you add it / partial support /  pick this - excellent hardware choice random for newbie

So how about the kernel testing discussion months ago. Should there be a progam that people/developers could run, if they wanted to, that collects information from the current kernel and before sending it to kernel.org it asks the user about how happy he is with the hardware currently connected/installed to the machine.

Alternatively/Additionally you have an automated database and people keep adding things in a wikimanner to it, with some apropriate structure to it.

But still, if even bugzilla is not the perfect tool, can it be improved?

regards,
Dirk

             reply	other threads:[~2005-12-08 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-08 16:35 dirk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-12-08 15:49 AW: Re: Linux in a binary world... a doomsday scenario dirk
2005-12-08 19:38 ` Lee Revell
     [not found]   ` <161717d50512081213oab71f63ncd9ecb3d721c83fc@mail.gmail.com>
2005-12-08 20:26     ` Lee Revell

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=10607050.147171134059741405.JavaMail.servlet@kundenserver \
    --to=dirk@steuwer.de \
    --cc=rdunlap@xenotime.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.