All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@gmail.com>
To: mike@pikeaero.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: maintainer: parport drivers
Date: Tue, 17 Jul 2007 22:47:33 +0200	[thread overview]
Message-ID: <469D2AE5.2080204@gmail.com> (raw)
In-Reply-To: <1184688556.711.8.camel@jake>

On 07/17/2007 06:09 PM, Mike Sharkey wrote:

> My question is; what are some of the outstanding issues with parport 
> which people would like to see addressed?

I've been wondering why PARPORT_PC_FIFO is EXPERIMENTAL. If it's expected to 
work these days it could be made non-experimental, and perhaps enabled 
always even.

Also not sure of the value of PARPORT_PC_SUPERIO. I haven't checked in some 
time, but that code didn't use to work for me even though I have a chipset 
which seems supported (Winbond 83977). These days, PNP (-ACPI) is providing 
PARPORT with the needed info for me:

| pnp: the driver 'parport_pc' has been registered
| pnp: match found with the PnP device '00:09' and the driver 'parport_pc'
| parport_pc 00:09: reported by Plug and Play ACPI
| parport0: PC-style at 0x378 (0x778), irq 7, dma 3 
[PCSPP,TRISTATE,COMPAT,EPP,ECP,DMA]
| lp0: using parport0 (interrupt-driven).

If that's also expected, perhaps that option and code could just go...

Rene.

      parent reply	other threads:[~2007-07-17 20:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-17 16:09 maintainer: parport drivers Mike Sharkey
2007-07-17 16:58 ` Randy Dunlap
2007-07-17 17:12   ` Adrian Bunk
2007-07-17 20:47 ` Rene Herman [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=469D2AE5.2080204@gmail.com \
    --to=rene.herman@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike@pikeaero.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.