Skip to contentSkip to conversation

Linux in a binary world... a doomsday scenario

DISCUSSION [email protected] 4 participants 5 messages Dec 8, 2005 1 message not in the archive

lore
Share & tools
lore
#0 lore raw
Quoted 18 lines
Quoted 2 lines · Dirk Steuwer

For a hardwaredatabase i like to see a structure. Kernel developers are required to enter the support into the database, when submitting the

driver.

Quoted 3 lines

Ongoing status will be logged there as well. Status and devices can only be

entered by kernel developers.

[Please don't remove the CC list]

This sounds like the typical nightmare that never is 100% accurate and needs lots of mainteinance (developers not updating the wiki, etc) as Lee Revell pointed out.

Quoted 5 lines

IMO the one way of creating such database is automating it. If you could get a list of the device IDs supported by drivers you could (?) use the pciid/usbid/whatever list to build a user-readable database of the devices supported by the linux tree. Maybe it won't 100% perfect but...

Yes, i can see the problem.
How about interconnecting it with the bugtracker?
If there is a bug, and if it is related to some hardware, it is logged in the database as broken for that kernel version. If the bug is fixed, support status is ok again. All that needs to be done is entering the device once into the database, status is broken by default, and take it from there?
Then it gets some goals (similar to bugs) assigned if it is a complex device. i.e. for a graphic device:
* 2d graphic support
* 3d graphic support
* framebuffer
* vesa

one can close goals similarly to bugs, and if a second tester find something broken, it gets filed as a bug.
As i see it the system has to be simple to use and if used, provide an advantage to kernel developers. This makes sure it will get used and could provide an instant status about linux hardware support.

regards,
Dirk

#1 lore raw
Quoted 1 line · El Thu, 08 Dec 2005 16:49:46 +0100, [email protected] 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.

#3 lore raw
In reply to [email protected]
Quoted 5 lines · On Thu, 2005-12-08 at 16:49 +0100, [email protected] wrote:

Yes, i can see the problem.
How about interconnecting it with the bugtracker?
If there is a bug, and if it is related to some hardware, it is logged in the database as broken for that kernel version. If the bug is fixed, support status is ok again.

Quoted 8 lines

All that needs to be done is entering the device once into the database, status is broken by default, and take it from there? Then it gets some goals (similar to bugs) assigned if it is a complex device. i.e. for a graphic device:
* 2d graphic support
* 3d graphic support
* framebuffer
* vesa

This is a grave oversimplification of how it would work. Look at sound hardware, vendors come out with new devices so fast that it would be a full time job to keep that ALSA wiki 100% accurate. At least half the bugs that users report aren't real bugs. There are gazillions of small variations of the same device. Vendors are deceptive at best and lie through their teeth at worst. A "Sound Blaster Live! SB0410" could use a COMPLETELY different and VASTLY inferior chipset to a "Sound Blaster Live! SB0350". They release two devices with identical PCI ids but different hardware. And they don't tell us word one about their plans. Often the users know a lot better than the developers do what devices are supported to what degree. Etc.

If we followed your scheme 95% of supported hardware would be listed as broken.

Lee

#5 lore raw
In reply to a message not in the archive
Quoted 16 lines · Dave Neuer
Quoted 15 lines · Lee Revell
Quoted 13 lines · On Thu, 2005-12-08 at 16:49 +0100, [email protected] wrote:

Yes, i can see the problem.
How about interconnecting it with the bugtracker?
If there is a bug, and if it is related to some hardware, it is logged in the database as broken for that kernel version. If the bug is fixed, support status is ok again.
All that needs to be done is entering the device once into the database, status is broken by default, and take it from there? Then it gets some goals (similar to bugs) assigned if it is a complex device. i.e. for a graphic device:
* 2d graphic support
* 3d graphic support
* framebuffer
* vesa

Quoted 7 lines
Quoted 4 lines

If we followed your scheme 95% of supported hardware would be listed as broken.

Lee

Well, let's start proposing solutions that will work then.

I like the idea of a centralized database, split up by subsystem, that's maintained by the developers in a similar way to the ALSA soundcard matrix. If a user finds an inaccuracy in the soundcard matrix or discovers a new hardware model that works they submit a bug report against the soundcard matrix, ideally containing a patch against the XML.

It HAS to live alongside the code in the same version control system as the code itself so it won't drift.

Lee

#2 lore raw
In reply to Diego Calleja

Diego Calleja <[email protected]> wrote:

[...]

Quoted 5 lines

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.

What use is it to me when I'm going to buy ShinyCard-9900, and the database tells me that RandomChip 2530a is supported? The packages rarely tell you what chips are in the cards, moreover there have been cases of /very similar/ card versions (i.e., SomeThing-990 and SomeThing-990+, or Card-897a and Card-897b) being /totally/ different inside). The only reliable way to find out if it works is a test drive. Distributions like Ubuntu are invaluable here.

Signature · 4 lines
Dr. Horst H. von Brand                   User #22616 counter.li.org
Departamento de Informatica                     Fono: +56 32 654431
Universidad Tecnica Federico Santa Maria              +56 32 654239
Casilla 110-V, Valparaiso, Chile                Fax:  +56 32 797513