public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rene Herman <rene.herman@keyaccess.nl>
To: Denis Zaitsev <zzz@anda.ru>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG][2.6.8.1] Something wrong with ISAPnP and serial driver
Date: Sat, 09 Oct 2004 22:18:36 +0200	[thread overview]
Message-ID: <4168479C.5080306@keyaccess.nl> (raw)
In-Reply-To: <20041010015206.A30047@natasha.ward.six>

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).

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. 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"

Hope that helps.

Rene.

  reply	other threads:[~2004-10-09 20:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-09 19:52 [BUG][2.6.8.1] Something wrong with ISAPnP and serial driver Denis Zaitsev
2004-10-09 20:18 ` Rene Herman [this message]
2004-10-09 21:38   ` Denis Zaitsev
2004-10-09 21:54     ` Rene Herman
     [not found]       ` <20041010043443.A1639@natasha.ward.six>
2004-10-09 22:46         ` Rene Herman
2004-10-09 23:28           ` Denis Zaitsev

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=4168479C.5080306@keyaccess.nl \
    --to=rene.herman@keyaccess.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zzz@anda.ru \
    /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