mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel Barkalow <barkalow@iabervon.org>
To: Heikki Orsila <shdl@zakalwe.fi>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] New driver information
Date: Fri, 16 Feb 2007 13:48:15 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0702161334170.20138@iabervon.org> (raw)
In-Reply-To: <20070216135851.GA7939@zakalwe.fi>

On Fri, 16 Feb 2007, Heikki Orsila wrote:

> I just read
> 
> 	http://kerneltrap.org/node/7729
> 
> and it occured to me that it would be informative to have a new device 
> driver macro. The motivation for the new macro would be 4 issues:
> 
> 	* Is it possible to get specifications for the device?
> 	* If yes, under what terms? (nda, public)
> 	* Where to get public specs?
> 	* How many closed and open drivers in the Linux source tree?

This doesn't make any sense as a driver macro, because it's per device, 
not per driver. E.g., the sdhci driver drives a number of devices, 
including both well-documented devices and devices whose only 
documentation is that the PCI ID matches (and they work with only a few 
quirks).

On the other hand, a kconfig-readable table of PCI, USB, etc IDs with this 
information isn't a bad idea, especially if the drivers actually depend on 
it (so that it has to be kept up to date, at least as far as the 
device/driver mapping).

      parent reply	other threads:[~2007-02-16 18:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-16 13:58 Heikki Orsila
2007-02-16 14:08 ` Thiago Galesi
2007-02-16 14:41   ` Maxim
2007-02-16 17:30 ` Adrian Bunk
2007-02-16 18:48 ` Daniel Barkalow [this message]

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=Pine.LNX.4.64.0702161334170.20138@iabervon.org \
    --to=barkalow@iabervon.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shdl@zakalwe.fi \
    /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®