public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Werner Almesberger <Werner.Almesberger@epfl.ch>
To: Mitchell Blank Jr <mitch@sfgoth.com>
Cc: Patrick van de Lageweg <patrick@bitwizard.nl>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Rogier Wolff <wolff@bitwizard.nl>
Subject: Re: [NEW DRIVER] firestream
Date: Thu, 23 Nov 2000 12:28:37 +0100	[thread overview]
Message-ID: <20001123122837.E599@almesberger.net> (raw)
In-Reply-To: <Pine.LNX.4.21.0011221031340.995-100000@panoramix.bitwizard.nl> <20001122092356.B53983@sfgoth.com>
In-Reply-To: <20001122092356.B53983@sfgoth.com>; from mitch@sfgoth.com on Wed, Nov 22, 2000 at 09:23:56AM -0800

Mitchell Blank Jr wrote:
>   * I don't like header files that define the registers of the chip - since
>     the header file is only included in the driver's .c

For a non-hypothetical case why it makes sense to have such things in
their own header file: if you dig out some older versions of the ATM
distribution, you'll find the programs called endump.c and zndump.c in
atm/debug. They run in user space and dump the card status, decoding
the "interesting" bits. And, of course, they include the register
headers.

Since they're strictly for development, it's okay that they include
things from deep down in /usr/src/linux (i.e. no need to move the
headers to linux/include/*), but it's important that they can share
the same definitions (to avoid version conflicts, etc.).

Besides, using a specific header file for the registers lowers the
risk that definitions get scattered all over the driver, so it makes
it easier to look for copy-from-manual bugs.

- Werner

-- 
  _________________________________________________________________________
 / Werner Almesberger, ICA, EPFL, CH           Werner.Almesberger@epfl.ch /
/_IN_N_032__Tel_+41_21_693_6621__Fax_+41_21_693_6610_____________________/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-11-23 11:59 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-22  9:32 [NEW DRIVER] firestream Patrick van de Lageweg
2000-11-22 17:23 ` Mitchell Blank Jr
2000-11-22 23:05   ` Rogier Wolff
2000-11-22 23:35     ` Jes Sorensen
2000-11-22 23:41       ` Jeff Garzik
2000-11-23 11:15   ` Rogier Wolff
2000-11-23 11:44     ` Peter Samuelson
2000-11-23 11:52       ` Rogier Wolff
2000-11-23 11:28   ` Werner Almesberger [this message]
2000-11-23  5:40 ` Peter Samuelson
2000-11-23  8:22   ` Rogier Wolff
2000-11-23  8:40     ` Peter Samuelson
2000-11-23 10:32     ` Vojtech Pavlik
2000-11-23 22:19 ` Bartlomiej Zolnierkiewicz
2000-11-23 23:43   ` Rogier Wolff
  -- strict thread matches above, loose matches on Subject: below --
2000-11-29  8:45 Patrick van de Lageweg
2000-12-06  8:45 Patrick van de Lageweg
2000-12-12 15:44 Patrick van de Lageweg
2000-12-15 12:07 Patrick van de Lageweg

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=20001123122837.E599@almesberger.net \
    --to=werner.almesberger@epfl.ch \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mitch@sfgoth.com \
    --cc=patrick@bitwizard.nl \
    --cc=wolff@bitwizard.nl \
    /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