On Thu, 2005-12-08 at 15:13 -0500, Dave Neuer wrote:
> On 12/8/05, Lee Revell <[email protected]> wrote:
> > 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
> >
> > 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
-
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]
