Re: Adding PCMCIA support to the kernel tree -- developers needed.

[Miles Lane <miles@megapathdsl.net>]

David Woodhouse wrote:

[...]
> > > -- The i82365 driver can't handle (non-CardBus) PCI-to-PCMCIA bridges
> > >    any more.  Some of the PCI code in the old i82365 driver needs to
> > >    be put back.
> 
> Or specific drivers for the PCI drivers need to be provided. The i82365
> driver with all the PCI stuff is a horrible mess. I tried putting back the
> non-CardBus PCI support at one point. It was ugly, and didn't work.
> Someone's now working on a driver for the Intel i82092AA bridge, and I
> think that's the best answer for the other PCI-PCMCIA bridges too, rather
> than merging it back into the ISA i82365 code.

Well, would care to elaborate on what the PCI mess is, exactly?  

I like the idea of not overloading drivers, if overloading leads to 
horribly complex or unmaintainable code.  Is there any generic code in
the 
i82365 driver that you think should be split out and included in drivers
for the various bridge drivers?

[...]
> I was actually coming to the conclusion that I'd prefer just to ditch the
> whole of the existing PCMCIA support and rewrite it from scratch as a kind
> of hot-pluggable isapnp, which is basically what it is (when you remember
> that PCMCIA != CardBus).

Why do you think the codebase needs to be jettisoned?

Which do you think should happen first:  you develop an exploratory 
implementation or have a general discussion of design issues?

My preference would be, if we decide to start fresh, that Linus
participate 
in the design process.  This worked well during the early design stage
for
the /sbin/hotplug design.

	Miles

_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel