mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Robert P. J. Day" <rpjday@mindspring.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	eng.linux@digi.com
Subject: Re: [PATCH][RFC] Remove support for the orphaned, obsolete Digi EPCA driver.
Date: Mon, 2 Jul 2007 10:20:48 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0707021015340.20805@localhost.localdomain> (raw)
In-Reply-To: <20070702151534.2728ae63@the-village.bc.nu>

On Mon, 2 Jul 2007, Alan Cox wrote:

> > > > This driver requires a number of user-space tools.  They can be acquired from
> > > > http://www.digi.com, but only works with 2.4 kernels."
> > >
> > > So fix them or merge the newer digi drivers first.
> >
> > ok, but what then does it mean to read that this driver:
> >
> > 1) *requires* a number of user-space tools, and
> > 2) these tools don't work with the 2.6 kernel?
>
> Last time I poked at the tools they were working under 2.6 with some
> trivial compile fixes. Ideally this driver would be trimmed to ISA
> only and the newer dgrs drivers merged but latter half appears to be
> something digi have no interest in

  ah, that wasn't obvious from the text.  in any event, there's still
some cosmetic cleanup that can be done if that driver's going to stick
around.

  first, from Documentation/ioctl-number.txt:

...
Documentation/ioctl-number.txt:'d'      F0-FF   linux/digi1.h
Documentation/ioctl-number.txt:'e'      all     linux/digi1.h           conflict!
...

there *is* no header file linux/digi1.h -- there is, however, a
drivers/char/digi1.h.

  also, there are references to a README.epca file in various places:

Documentation/kernel-parameters.txt:                    See drivers/char/README.epca and
Documentation/digiepca.txt:drivers/char/README.epca for more details.  Note,
drivers/char/epca.c:/* See README.epca for change history --DAT*/

but there is no README.epca file.  just a couple observations.

rday
-- 
========================================================================
Robert P. J. Day
Linux Consulting, Training and Annoying Kernel Pedantry
Waterloo, Ontario, CANADA

http://fsdev.net/wiki/index.php?title=Main_Page
========================================================================

  reply	other threads:[~2007-07-02 14:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-02 13:14 Robert P. J. Day
2007-07-02 13:46 ` Alan Cox
2007-07-02 13:48   ` Robert P. J. Day
2007-07-02 14:15     ` Alan Cox
2007-07-02 14:20       ` Robert P. J. Day [this message]
2007-07-02 14:56       ` Kilau, Scott
2007-07-02 15:05         ` Alan Cox

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.0707021015340.20805@localhost.localdomain \
    --to=rpjday@mindspring.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=eng.linux@digi.com \
    --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®