Re: [BUG][2.6.8.1] Something wrong with ISAPnP and serial driver

Denis Zaitsev
2004-10-09T21:39:14Z

On Sat, Oct 09, 2004 at 10:18:36PM +0200, Rene Herman wrote:
> Denis Zaitsev wrote:
>
> > 1) The 2.6 kernel doesn't activate the ISA PnP modem at the boot,
> > while the 2.4 one always does.
>
> 2.4 used to scan the ISA PnP device ID string for some common substrings
> indicating a modem given a completely unknown ISA PnP device (the code
> is still present -- see drivers/serial/8250_pnp.c:check_name()) while
> 2.6 really needs your modem's PnP ID to be listed.
>
> > 2) The 8250 driver finds the PnP card's port, while the 8250_pnp finds
> > the non-PnP ports.
>
> 8250_pnp not finding it is therefore very likely a simple matter of it
> not knowing that it should be driving it. Try seeing if your modem's PnP
> ID (/sys/bus/pnp/devices/?/id) is listed in drivers/serial/8250_pnp.c
> and if not add it (and send as a patch to Russel King).

Ok, it isn't listed (USR0009). I'll send a patch. BTW, there is some
other ID - /sys/devices/pnp1/01:01/card_id - and it contains USR0101.
What's this?

> 8250 itself finding it was no doubt due to you enabling the port
> yourself so that from its standpoint, it was just another serial port
> already present.

But why doesn't it find the two standard mb-embedded ports? And why
they are found by 8250_pnp? Is it a normal behaviour?

> With your modem's ID added, 8250_pnp should find and activate the
> mdem itself without you needing to do anything other than "modprobe
> 8250_pnp"

Ok. I' trying. The kernel is compiling...

> Hope that helps.

Thanks. But what about the incorrect info in /proc/tty/driver/serial?