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 23:54:12 +0200 [thread overview]
Message-ID: <41685E04.3070103@keyaccess.nl> (raw)
In-Reply-To: <20041010033820.B30047@natasha.ward.six>
Denis Zaitsev wrote:
> 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?
The PnP card ID, with the USR0009 the PnP device ID; PnP cards can (and
often do) have more than one device. For me, they are both the same:
$ cat /sys/devices/pnp1/01\:02/{card_,01\:02.00/}id
ETT0002
ETT0002
I do believe you need the device ID in 8250_pnp, but try the card ID
when it doesn't work, I guess.
>>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?
That they are found by 8250_pnp seems okay; onboard ports are normally
PnP BIOS devices -- the devices in /sys/devices/pnp0. However, normally
the BIOS will have enabled those ports itself meaning 8250 would pick
them up already, so no, that's not standard.
> Thanks. But what about the incorrect info in /proc/tty/driver/serial?
Skipping that one. Maybe that will fix itself once you have the PnP ID
listed.
Rene.
PS: CCing you, but gw.anda.ru seems to have decided I'm a spammer.
next prev parent reply other threads:[~2004-10-09 21:58 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
2004-10-09 21:38 ` Denis Zaitsev
2004-10-09 21:54 ` Rene Herman [this message]
[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=41685E04.3070103@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.