mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zenaan Harkness <zen@freedbms.net>
To: debian-devel@lists.debian.org
Cc: linux-kernel@vger.kernel.org
Subject: Re: drivers DB and id/ info registration
Date: Wed, 26 May 2004 20:07:59 +1000	[thread overview]
Message-ID: <1085566079.2522.54.camel@zen8100a.freedbms.net> (raw)
In-Reply-To: <200405260918.51589@fortytwo.ch>

On Wed, 2004-05-26 at 17:18, Adrian 'Dagurashibanipal' von Bidder wrote:
> On Wednesday 26 May 2004 08.54, Javier Fernández-Sanguino Peña wrote:
> > On Wed, May 26, 2004 at 01:38:26PM +1000, Zenaan Harkness wrote:
> > > My biggest itch in our free software world is drivers.
> [...]
> > > Does it make sense to set up a centralized website/ DB where
> 
> I always jump when somebody wants to centralize things...

I know how you feel, although this is more from a manufacturers point of
view:

I develop widget X.

I contact microsoft and have X incorporated into windows.

I want to get it into free software kernels ... ???

> OTOH, one place to collect the info would probably be good. Or at least 
> (to start with) one place listing the various places where such info is 
> currently collected. Perhaps this is a case for a Wiki, and then you'll 
> see in what direction this develops.

Might be a good way to start.

> > > hardware manufacturers and individuals can submid hardware info,
> > > and that is widely advertised to hardware companies around the
> > > globe?
> >
> > Yes, it does. I'm not sure if it makes sense to have it
> > distribution-independent. End-users want to see which hardware is
> > supported by their operating system (the current release, not the
> > development release)

The primary intention here is to make it easy for the manufacturers, not
the end users (however a nice searchable interface for users would
assuredly be a side effect).

If I have a device that has multiple connection types (eg. parallel,
usb, ethernet), who do I contact in the free software world? It's
currently not easy/ known.

It could/ should include information (perhaps in wiki or some "user
submissions") about which kernels/ distros currently have support too,
since that is useful information.

> I guess this depends on what this site wishes to do. Should it be a 
> repository for end-users to get information, or should it be a resource 
> for distribution developers to go looking for device identification 
> information?

Primarily for manufacturers to provide/ submit information to.
Therefore the second primary target I guess would be developers.
Thirdly is users.

Thanks
Zenaan

       reply	other threads:[~2004-05-26 10:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1085542706.2908.25.camel@zen8100a.freedbms.net>
     [not found] ` <20040526065447.GA32304@dat.etsit.upm.es>
     [not found]   ` <200405260918.51589@fortytwo.ch>
2004-05-26 10:07     ` Zenaan Harkness [this message]
2004-05-26 11:35       ` Wouter Verhelst
2004-05-26 12:07         ` Zenaan Harkness
2004-05-26 12:44           ` Richard B. Johnson
2004-05-26 15:38           ` Randy.Dunlap
2004-05-26 11:53       ` Denis Vlasenko
2004-05-26 13:16         ` Zenaan Harkness
2004-05-26 22:26           ` Horst von Brand
2004-05-27  0:05             ` Zenaan Harkness

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=1085566079.2522.54.camel@zen8100a.freedbms.net \
    --to=zen@freedbms.net \
    --cc=debian-devel@lists.debian.org \
    --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

all inboxes | Powered by JetHome®