White/blacklisting manf_id/prod_id vs. func_id
linux at dominikbrodowski.net
Tue Nov 21 15:04:15 EST 2006
On Tue, Nov 21, 2006 at 07:54:07PM +0000, Russell King wrote:
> > > Good devices should just work out of the box as they used to with
> > > the original pcmcia-cs implementation.
> > They do work out of the box. They just might not work if userspace is
> > not up and running -- but that's not a regression. So please stop
> > making this claim.
> Why then, is this Elan card not detected out of the box despite advertising
> that it is a serial function,
The way I read the facts was that
a) there are some Elan cards which do now work out of the box if the
ID overlap is removed,
b) there are some Elan multifunction(!) cards which do need an ID -- but
they needed that before, too. I'm thinking about allowing func_id matches
on MFC too, if the func_id actually states serial and not multifunction.
But, what should happen in your opinion if the func_id says
multifunction? Presume it is a serial card?
> But when the explicit IDs are added, it works. _That_ sounds to me very
> much like the function matching is broken.
Or that userspace isn't correctly set up.
> > What's the story with PCI drivers and devices?
> 99% of them just work. We occasionally have to add another ID, and
> recently there have been some specific IDs we've been able to remove.
> On the whole, the list of explicit devices is actually rather stable.
For PCMCIA, we're still in the transition process -- and the list of
explicit devices is actually quite stable already.
PS: You might need to fix your signature ;)
> > One thing which might be worth thinking about is adding an interface
> > similar to PCI's new_id. Patches are welcome.
> Don't look at me - remember I gave up PCMCIA and recently serial (and
> MMC) as well. But that doesn't mean I give up reviewing serial patches,
> which is what this is all about.
> Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
> maintainer of: 2.6 Serial core
More information about the linux-pcmcia