RE: Lite5200 and PCI1520

RE: Lite5200 and PCI1520

[Zeitler, Nathan]

Hello Wolfgang,=20

>Now what? Is it a custom board, or a Lite5200?=20

My apologies.  It is a custom board based closely on the design of the
Lite5200.  Thus we are able to put a PCI1520 chip on the same PCB and
connect it to the MPC5200 PCI bus.

>U-Boot 1.1.1 is old. You better use current code (top of CVS).
>
>ELDK 2.1 is extremely old. You better use a current version (3.1).

Agreed, they are old, although I was hoping to be more certain that the
age of the toolchain was a problem first.  I have tried top-of-CVS
UBOOT, but reverted when no evident improvement occurred.=20
 =20
>What's you PCMCIA config file looking like?

Under /etc/sysconfig/pcmcia:
PCMCIA=3Dyes
PCIC=3Dyenta_socket
PCIC_OPTS=3D
CORE_OPTS=3D
CARDMGR_OPTS=3D

Under /etc/pcmcia/config.opts...=20
(This is as how I found it, although I added the 4th port address and
changed the memory range in an attempt to get it to cooperate.  I/O
resources aren't even being detected, so I tried adding 0x50000000 to
each I/O port address in yenta.c and adding the same value to each I/O
here to no avail):
include port 0x100-0x4ff, port 0x800-0x8ff, port 0xc00-0xcff, port
0x1000-0x10ff
include memory 0x40000000-0x40001fff
include port 0xa00-0xaff
exclude irq 4
exclude irq 7
module "ray_cs" opts "essid=3DADHOC_ESSID hop_dwell=3D128 =
beacon_period=3D256
translate=3D1"

Help with respect to getting the interrupts and anything further
(configuration files and more) is appreciated, although for the sake of
keeping on topic, I can send any Card Services-based queries to the
pcmcia-cs mailing list if so desired :-)

RE: Lite5200 and PCI1520

[Andrew Dennison]

Nathan Zeitler wrote:

> Hello Wolfgang,
>=20
>> Now what? Is it a custom board, or a Lite5200?
>=20
> My apologies.  It is a custom board based closely on the design of the
> Lite5200.  Thus we are able to put a PCI1520 chip on the same PCB and
> connect it to the MPC5200 PCI bus.

Nathan,
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!

I also have a custom board with a mpc5200, pci1520 cardbus bridge, DDR,
etc.

Which kernel are you using?

I'm using Denx linuxppc_2_4_devel cvs and so far I've had to make =
several
changes to get close to a working system. I've changed the PCI bus =
mapping
so ISA I/O (ie PCMCIA) is at the bottom of the PCI address space, from =
my
reading / debugging this seems to be required to get PCMCIA to work. I
initially tried hacking yenta.c to use a high I/O range (like you have)
but this doesn't seem to be the solution. My memory map is now as =
follows:

/*
 * VPC mapping deviates from icecube so PCMCIA can work!
 * From Processor to PCI:
 *   PCI Mem Space: 0x40000000 - 0x50000000 -> 0x40000000 - 0x50000000
(256 MB)
 *   PCI I/O Space: 0x50000000 - 0x51000000 -> 0x00000000 - 0x01000000 =
(16
MB)
 *
 * From PCI to Processor:
 *   System Memory: 0x80000000 -> 0x00000000
 */

this also requires:
#define _IO_BASE	isa_io_base=20
and isa_io_base to be set to the correct virtual address, =
pci_dram_offset
=3D 0x8000000, among other changes.

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.

Part of the reason for my reply is also to check if my current approach
(remapping the PCI address space) is sane - comments anyone? I have made
similar changes in u-boot and can now read / write CF cards so it seems
like the right approach for the kernel too.

Andrew

Re: Lite5200 and PCI1520

[Wolfgang Denk]

Dear Andrew,

in message <002a01c4e16e$34451010$4000a8c0@CAT> you wrote:
> 
> 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!

I think I can confirm that this was not considered, but I'm not  sure
that this is an issue here.

> 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.

I'd like to see your patch (even if preliminary).

> Part of the reason for my reply is also to check if my current approach
> (remapping the PCI address space) is sane - comments anyone? I have made
> similar changes in u-boot and can now read / write CF cards so it seems
> like the right approach for the kernel too.

Unfortunately I don't have any hardware yet with  a  working  cardbus
interface. But this might change soon...

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
Men don't talk peace unless they're ready to back it up with war.
	-- Col. Green, "The Savage Curtain", stardate 5906.4

RE: Lite5200 and PCI1520

[Andrew Dennison]

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:)

RE: Lite5200 and PCI1520 - preliminary patch

[Andrew Dennison]

[-- Attachment #1: Type: text/plain, Size: 1548 bytes --]

On Tuesday, 14 December 2004 11:33 AM, wd@denx.de wrote:
> 
> I'd like to see your patch (even if preliminary).
> 

Well - here it is.

This is a patch against Denx linuxppc_2_4_devel, LABEL_2003_12_22_1500.
Yes - I know that's old but I have some RTAI modules and I didn't want to
jump kernel versions just yet.

All problems I've fixed are still in the top of CVS anyway. Some changes
I've made are backported from or inspired by later 2.4 and 2.6 kernels.

Current status:
orinoco_cs cards work for me
ide_cs fails registering the driver.
some cardbus cards enumerate and can dump_cis, others cause a TEA on
insertion. May be hardware or software bugs:)
card status and functional interrupts sometimes don't work on boot.
IRQ = 0 not supported, may just change mpc5xxx_pci to start interrupts at
1 as fixing this is a lot of work, and all the same assumptions still
exist in 2.6:(
lots of debug rubbish still present

Issues addressed:
1) remap PCI addresses to make PCMCIA feasible
2) use io_block_mapping for MBAR, so pci configuration type 0 cycles are
on a valid memory address after init
3) fix pci configuration type 1 cycles as per errata
4) add PCI1520 support, with interrupt related fixes
5) added preliminary support for my hardware. Most (all?) of the
deviations from idecube in the vpc platform are required for PCMCIA

If anyone has a cardbus pci card that works in a lite5200 and wants to do
some testing I can patch the icecube platform.

I would appreciate some feedback on this!

Andrew

[-- Attachment #2: vpc_patch.2.gz --]
[-- Type: application/x-gzip, Size: 16529 bytes --]