mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Zenaan Harkness <zen@freedbms.net>
To: linux-kernel@vger.kernel.org
Cc: "debian-devel@lists.debian.org" <debian-devel@lists.debian.org>
Subject: [Fwd: Re: drivers DB and id/ info registration]
Date: Wed, 26 May 2004 15:08:13 +1000	[thread overview]
Message-ID: <1085548092.2909.60.camel@zen8100a.freedbms.net> (raw)

I think we need to somehow make it easy for manufacturers to submit
information about their hardware - something centralized, kernel- and
distro- neutral, that can be widely advertised to manufacturers.

Here is what I've found so far for id DBs, and it seems a bit all over
the place:

PCI
==============================
http://pciids.sourceforge.net/

Which has a submit new entry form, which asks for ID, Name, Comment and
Email only, here:
http://pciids.sourceforge.net/iii/?sub=1

Printers
==============================
http://www.linuxprinting.org/kpfeifle/LinuxKongress2002/Tutorial/VIII.Foomatic-Contribution/VIII.tutorial-handout-foomatic-contribution.html
Which has a forum for submission, and a list of information to
describe the printer, seems aimed at users:
      * Manufacturer's name
      * Model name
      * Mechanism type (as laser, inkjet, dot matrix, ...)
      * Color or black-and-white?
      * Maximum resolution claimed by the manufacturer and obtained by
        you with free software
      * Connection types (Parallel, USB, Ethernet, ...)
      * Maximum paper size
      * Special functionality (multi-function device, finishers, ...)
      * Type of consumables/refills (as "one black and one color
        cartridge", "toner/drum unit", ... not only "cartridge(s)")
      * How did you get it to work? Which driver(s) did you use and with
        which option settings? Which driver do you recommend? Did you
        apply special tricks (as hacking the driver's code, using an
        additional filter, ...) to get the printer to work?
      * Also reporting that a printer does not work at all is important
        for us, users should be warned before they buy a "Paperweight".
      * What is your impression of the results? Categorize your printer
        in one of the levels described on the database introduction page
        (http://www.linuxprinting.org/database.html).
Also has suggestions to manufacturers further below.

USB
==============================
http://www.linux-usb.org/usb.ids
http://www.linux-usb.org/
Various links, mailing lists, a working devices list, etc.
Also a link to Linux USB Guide:
http://www.linux-usb.org/USB-guide/book1.html
No clear submission for manufacturers.

Firewire
==============================
Can't readily find anything with google.

=========
So, does it make sense to create a centralized repository, and/ or an
FAQ for manufacturers.

I really think it needs to be easy for manufacturers to supply
information. I have no doubt that there must be a standardized process
at MS whereby manufacturers can submit device, id, name and other driver
information directly to microsoft and have it included in the next
service pack. I'm guessing here though, but it does seem like we in the
free software community are playing catch up, and that that is in some
way simply an organizational problem.

All thoughts, suggestions, further links to add to the above list, etc,
very much appreciated.

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

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-26  5:08 Zenaan Harkness [this message]
2004-05-26  5:26 ` Zenaan Harkness
2004-05-26  5:42 ` Cef (LKML)
2004-05-26 18:29 ` Greg KH
2004-05-26 19:34   ` Zenaan Harkness
2004-05-26 19:52     ` Valdis.Kletnieks
2004-05-26 19:55     ` Greg KH
2004-05-26 20:08       ` Zenaan Harkness
2004-05-27  0:26         ` Greg KH

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=1085548092.2909.60.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®