public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Chan <rspchan@starhub.net.sg>
To: linux-kernel@vger.kernel.org
Subject: 2.5.56 CardBus not accepting USB 2.0 adapter
Date: Sat, 11 Jan 2003 10:45:55 +0800	[thread overview]
Message-ID: <3E1F8563.4070004@starhub.net.sg> (raw)


2.5.56 CardBus is not accepting a USB 2.0 adapter due to
the infamous PCI resource collision problem.  This was
also seen in 2.5.54, 2.5.55. The card works under 2.4.18.

lspci has
02:03.0 CardBus bridge: Texas Instruments PCI1420
02:03.1 CardBus bridge: Texas Instruments PCI1420

dmesg shows:
cs: cb_alloc(bus 3): vendor 0x1033, device 0x0035
PCI: Device 03:00.0 not available because of resource collisions
PCI: Device 03:00.1 not available because of resource collisions
PCI: Device 03:00.2 not available because of resource collisions

Other people on this list seem to have problems with network cards.
I reported this on the usb devel list but apparently it is CardBus
b0rkeness rather than a usb problem.

Any ideas?

Richard Chan





                 reply	other threads:[~2003-01-11  2:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=3E1F8563.4070004@starhub.net.sg \
    --to=rspchan@starhub.net.sg \
    --cc=linux-kernel@vger.kernel.org \
    /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