maintainer: parport drivers

maintainer: parport drivers

[Mike Sharkey]

Hello,

I understand there are currently no active maintainers of parport and
friends - unless that has changed recently. 

We are heavy users of parport devices, and so I am offering to begin
maintaining the parport drivers. I have spent some time studying the
drivers closely, and I've read Love's book linux kernel development, so
I think I'm just about ready for this.

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

Kind Regards,

Mike Sharkey
Pike Aerospace Research Corporation
Bradford, Ontario
Canada
http://www.pikeaero.com

Re: maintainer: parport drivers

[Randy Dunlap]

On Tue, 17 Jul 2007 12:09:16 -0400 Mike Sharkey wrote:

> Hello,
> 
> I understand there are currently no active maintainers of parport and
> friends - unless that has changed recently. 
> 
> We are heavy users of parport devices, and so I am offering to begin
> maintaining the parport drivers. I have spent some time studying the
> drivers closely, and I've read Love's book linux kernel development, so
> I think I'm just about ready for this.
> 
> My question is; what are some of the outstanding issues with parport
> which people would like to see addressed?

There are probably others, but "Advanced Search" at
bugzilla.kernel.org finds these 4 bug reports:

http://bugzilla.kernel.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=parport&long_desc_type=substring&long_desc=&kernel_version_type=allwordssubstr&kernel_version=&bug_status=NEW&bug_status=REOPENED&bug_status=ASSIGNED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&chfieldfrom=&chfieldto=Now&chfieldvalue=&regression=both&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0=


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***

Re: maintainer: parport drivers

[Adrian Bunk]

On Tue, Jul 17, 2007 at 09:58:15AM -0700, Randy Dunlap wrote:
> On Tue, 17 Jul 2007 12:09:16 -0400 Mike Sharkey wrote:
> 
> > Hello,
> > 
> > I understand there are currently no active maintainers of parport and
> > friends - unless that has changed recently. 
> > 
> > We are heavy users of parport devices, and so I am offering to begin
> > maintaining the parport drivers. I have spent some time studying the
> > drivers closely, and I've read Love's book linux kernel development, so
> > I think I'm just about ready for this.
> > 
> > My question is; what are some of the outstanding issues with parport
> > which people would like to see addressed?
> 
> There are probably others, but "Advanced Search" at
> bugzilla.kernel.org finds these 4 bug reports:
>...

You don't need an advanced search.

There's a component Drivers/Parallel in the kernel Bugzilla that 
contains a superset of the bugs from your search.

> ~Randy

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed

Re: maintainer: parport drivers

[Rene Herman]

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.