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
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
