public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heikki Orsila <shdl@zakalwe.fi>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [RFC] New driver information
Date: Fri, 16 Feb 2007 15:58:51 +0200	[thread overview]
Message-ID: <20070216135851.GA7939@zakalwe.fi> (raw)

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?

I suggest to add following macro:

MODULE_SPECIFICATION(terms, source);

where "terms" is one of

 * MODULE_SPEC_ANY_PARTY_NDA
	- specification available to any party for an NDA
 * MODULE_SPEC_ANY_PARTY
	- specification available in public, or at least available 
	  without NDA to any party
 * MODULE_SPEC_RESTRICTED
	- none of the above

and "source":

 * contact address for nda specs
 * any public source for a public specification (http://, email address, 
   ...)
 * empty string otherwise

I realise this macro somewhat circumvents the purpose of Documentation/ 
directory but the idea is to have a direct 1:1 mapping between drivers 
and specification sources so that it would be easy to collect statistics 
of "open" hardware by using grep et al.

What do you think? Useless annotations or useful information?

-- 
Heikki Orsila			Barbie's law:
heikki.orsila@iki.fi		"Math is hard, let's go shopping!"
http://www.iki.fi/shd

             reply	other threads:[~2007-02-16 13:58 UTC|newest]

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

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=20070216135851.GA7939@zakalwe.fi \
    --to=shdl@zakalwe.fi \
    --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