Re: isapnp modem in 2.6.0-test9-bk13 not working

[ivan <pivo@pobox.sk>]

On Tue, Dec 02, 2003 at 11:25:12PM +0000, Adam Belay wrote:
> Date: Tue, 2 Dec 2003 23:25:12 +0000
> From: Adam Belay <ambx1@neo.rr.com>
> To: ivan vadovic <pivo@pobox.sk>
> Subject: Re: isapnp modem in 2.6.0-test9-bk13 not working
> 
> On Tue, Dec 02, 2003 at 10:43:37PM +0000, Adam Belay wrote:
> > On Tue, Nov 11, 2003 at 01:58:58AM +0100, ivan vadovic wrote:
> > > I've got an ordinary isapnp modem which provides a serial port unlike
> > > winmodems and it just happens to work under 2.4 kernels. When I boot into
> > > the 2.6 kernel on the same machine, everything ( sound, ide, md, networking,
> > > input devices) seems to work right but the modem. Modprobing 8250_pnp only
> > > detects the 2 onboard serial ports. Am I doing anything wrong? What am I
> > > supposed to test? Should I provide any more info? Please Cc me as I'm not
> > > on the list.
> > >
> > 
> > Could you try this patch.
> > 
> > --- a/drivers/serial/8250_pnp.c	2003-11-26 20:42:52.000000000 +0000
> > +++ b/drivers/serial/8250_pnp.c	2003-12-02 22:41:04.000000000 +0000
> > @@ -310,6 +310,8 @@
> >  	{	"PNPCXXX",		UNKNOWN_DEV	},
> >  	/* More unkown PnP modems */
> >  	{	"PNPDXXX",		UNKNOWN_DEV	},
> > +	/* check all devices and guess if they are modems */
> > +	{	"ANYDEVS",		UNKNOWN_DEV	},
> >  	{	"",			0	}
> >  };
> > 
> > Thanks,
> > Adam
> > 
> 
> On second thought this isn't a very good idea because of the way the current
> code enables devices on a match.  Instead I'll need the EISA ID for your modem.
> You can find it by catting /proc/isapnp in 2.4 or through sysfs in 2.6.

Could it be something like RSS0250 ?
I made it work with isapnptools btw. Under 2.4 I didn't need isapnptools so
there's a bug somewhere. I'll try the patch a little bit later.

This is what isapnptools says:
Board 1 has Identity 52 00 00 08 98 50 02 73 4a:  RSS0250 Serial No 2200

Thanks for help.
Ivan