From: "Andrew Dennison" <andrew.dennison@motec.com.au>
To: <wd@denx.de>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: Lite5200 and PCI1520
Date: Tue, 14 Dec 2004 12:25:20 +1100 [thread overview]
Message-ID: <003001c4e17b$c6d45e10$4000a8c0@CAT> (raw)
In-Reply-To: <20041214003301.2CC13C1430@atlas.denx.de>
On Tuesday, 14 December 2004 11:33 AM, wd@denx.de wrote:
> Dear Andrew,
>=20
> in message <002a01c4e16e$34451010$4000a8c0@CAT> you wrote:
>>=20
>> I posted a question on cardbus with the 5200 a few weeks ago but got
>> no reply. I think the reason is that cardbus / pcmcia support may
>> not have been considered when the 5200 PCI memory map was laid out,
>> but I would love to be contradicted!
>=20
> I think I can confirm that this was not considered, but I'm not sure
> that this is an issue here.
Hi Wolfgang,
It's a problem for PCMCIA, but probably not for cardbus. The PCMCIA =
16bit
I/O space can't be mapped above 0x1000 in the PCI address space. The CPU
physical address doesn't matter.
The PCMCIA memory space can be mapped to any 16MiB boundary so this =
isn't
a problem
>=20
>> I also have a few outstanding issues that I haven't resolved yet,
>> hence I haven't posted a full patch, but I can now load and
>> configure a wireless ethernet card. Loading cardbus drivers
>> currently fails when accessing PCI configuration space on the
>> cardbus bus, and I haven't sorted this out yet.=20
>=20
> I'd like to see your patch (even if preliminary).
I'll work on bundling it up in the next day or two. There are lots of
changes, including partial support for IRQ0 being a valid interrupt...
sigh. The setup of the BAT for MBAR also doesn't seem correct to me, but
I'm now using io_block_mapping() in my platform support.
Another problem I noticed is pcibios trashing the 5200 bridge setup. =
I've
hacked around this for now. Not a problem for PCMCIA but would have =
broken
bus mastering for cardbus / PCI.
While looking at PCI I noticed that the icecube platform (which I =
copied:)
compiles in pci_auto and indirect_pci but they aren't used. Is this work
in progress or a "cut-n-paste" error?
> Unfortunately I don't have any hardware yet with a working cardbus
> interface. But this might change soon...
Good to hear:)
next prev parent reply other threads:[~2004-12-14 1:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 22:09 Lite5200 and PCI1520 Zeitler, Nathan
2004-12-13 23:48 ` Andrew Dennison
2004-12-14 0:32 ` Wolfgang Denk
2004-12-14 1:25 ` Andrew Dennison [this message]
2004-12-17 7:11 ` Lite5200 and PCI1520 - preliminary patch Andrew Dennison
-- strict thread matches above, loose matches on Subject: below --
2004-12-14 0:06 Lite5200 and PCI1520 Zeitler, Nathan
2004-12-14 0:45 ` Andrew Dennison
2004-12-13 17:50 Zeitler, Nathan
2004-12-13 21:13 ` Wolfgang Denk
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='003001c4e17b$c6d45e10$4000a8c0@CAT' \
--to=andrew.dennison@motec.com.au \
--cc=linuxppc-embedded@ozlabs.org \
--cc=wd@denx.de \
/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).