From: Adam Belay <ambx1@neo.rr.com>
To: ivan vadovic <pivo@pobox.sk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: isapnp modem in 2.6.0-test9-bk13 not working
Date: Tue, 2 Dec 2003 23:25:12 +0000 [thread overview]
Message-ID: <20031202232512.GA14946@neo.rr.com> (raw)
In-Reply-To: <20031202224337.GA3531@neo.rr.com>
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.
Thanks,
Adam
next prev parent reply other threads:[~2003-12-03 4:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-11 0:58 isapnp modem in 2.6.0-test9-bk13 not working ivan vadovic
2003-12-02 22:43 ` Adam Belay
2003-12-02 23:25 ` Adam Belay [this message]
2003-12-03 18:49 ` ivan
2003-12-03 20:40 ` isapnp modem working [PATCH] ivan vadovic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20031202232512.GA14946@neo.rr.com \
--to=ambx1@neo.rr.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pivo@pobox.sk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox