From: Russell King <rmk+serial@arm.linux.org.uk>
To: Sasha Khapyorsky <sashak@smlink.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: [2.6 patch] drivers/serial/8250_pci.c: don't probe non-serial softmodems
Date: Sat, 30 Apr 2005 09:54:16 +0100 [thread overview]
Message-ID: <20050430095416.A31027@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050419235608.GB8276@tecr>; from sashak@smlink.com on Wed, Apr 20, 2005 at 02:56:08AM +0300
On Wed, Apr 20, 2005 at 02:56:08AM +0300, Sasha Khapyorsky wrote:
> Some soft modem pci devices (known list in the patch) claim to have
> 'communication' class, and as result they are grabbed by serial driver.
> Actually those devices are useless for serial drivers (it is not "real"
> modem and doesn't have serial interface), but this prevents probing from
> soft modem drivers (there are few in ALSA).
What class id are these devices?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-04-30 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 23:56 [2.6 patch] drivers/serial/8250_pci.c: don't probe non-serial softmodems Sasha Khapyorsky
2005-04-30 8:54 ` Russell King [this message]
2005-04-30 21:23 ` Sasha Khapyorsky
2005-05-27 23:00 ` Sasha Khapyorsky
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=20050430095416.A31027@flint.arm.linux.org.uk \
--to=rmk+serial@arm.linux.org.uk \
--cc=linux-serial@vger.kernel.org \
--cc=sashak@smlink.com \
/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;
as well as URLs for NNTP newsgroup(s).