From: George Andre <george.andre@intelligraphics.com>
To: linux-kernel@vger.kernel.org
Cc: alan@lxorguk.ukuu.org.uk
Subject: [BUG] PCI-2-Cardbus bridge, Kernel PCMCIA services and Cardbus
Date: Mon, 11 Nov 2002 17:29:11 +0100 [thread overview]
Message-ID: <3DCFDAD7.9080003@intelligraphics.com> (raw)
Hi people,
I have a strange problem with virtually all 2.4 kernels,
(tried 2.4.18 to 2.4.20-rc1). I'm developing a driver
for a wireless card for our customer. Since it's a Cardbus
wireless card and my dev machine is a desktop, I'm using
a Ricoh 5c475 based PCI-2-Cardbus bridge.
My problem is that the yenta_socket.o driver (or pcmcia_core.o)
indeed create Cardbus bus with my device on it, but the BAR's
are all messed up. I get negative len ranges on the MMIO addresses
(0xE7010000 - 0xE7003FFF).
I'm not sure this is a problem in the Kernel PCMCIA drivers, because
even with them not loaded, the Ricoh device (Cardbus bridge) contains
weird bridge resources (offset 0x1C and forward in the PCI
config space headertype 0x02). This doesn't happen only with my
customers wireless card, but with one another different vendors wireless
card too.
I've even tried Alan Cox' 2.4.20-pre10-ac2 patch with no success.
Anyone seen this before and know where I might throw my search lights ?
Thanks,
George.
reply other threads:[~2002-11-11 16:22 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=3DCFDAD7.9080003@intelligraphics.com \
--to=george.andre@intelligraphics.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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