From: "Tom Sightler" <ttsig@tuxyturvy.com>
To: "Jeff Garzik" <jgarzik@mandrakesoft.com>,
"Bill Nottingham" <notting@redhat.com>
Cc: <linux-kernel@vger.kernel.org>, <tytso@mit.edu>,
"Alessandro Suardi" <alessandro.suardi@oracle.com>
Subject: Re: [PATCH] make Xircom cardbus modems work
Date: Wed, 9 May 2001 10:37:12 -0400 [thread overview]
Message-ID: <001101c0d895$8bfe27f0$2d040a0a@zeusinc.com> (raw)
In-Reply-To: <20010509093733.C18911@devserv.devel.redhat.com> <3AF94ACB.F3688AB@mandrakesoft.com>
> Does the attached patch work for you?
>
> serial.c still has the basic problem that there is a logical disconnect
> between the pci_boards list and the pci-device-id list: any device
> which is not PCI_CLASS_COMMUNICATION_SERIAL or
> PCI_CLASS_COMMUNICATION_MODEM will not get scanned. The solution is to
> move the PCI ids into the probe list, before the class listing. Ideally
> I would like to merge the Xircom cardbus fix with this fix, since they
> are both modifying the pci_board list and thus conflict.
>
> Except for the Xircom Cardbus update (based on your patch, Bill), this
> patch has been tested and is known to solve the problems reported to me
> which were caused by the logical disconnect.
>
> (Alessandro, Tom, tytso: the attached patch is updated for the changes
> in Bill's patch, so you haven't seen this version yet)
>
> Jeff
Just wanted to report that this patch finally fixes my Xircom Cardbus
adapter. Works like a charm.
Thanks!!
Later,
Tom
next prev parent reply other threads:[~2001-05-09 14:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-09 13:37 [PATCH] make Xircom cardbus modems work Bill Nottingham
2001-05-09 13:48 ` Jeff Garzik
2001-05-09 14:37 ` Tom Sightler [this message]
2001-05-09 21:29 ` Bill Nottingham
2001-05-14 9:45 ` Alessandro Suardi
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='001101c0d895$8bfe27f0$2d040a0a@zeusinc.com' \
--to=ttsig@tuxyturvy.com \
--cc=alessandro.suardi@oracle.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=notting@redhat.com \
--cc=tytso@mit.edu \
/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