From: Wolfgang Denk <wd@denx.de>
To: "Zeitler, Nathan" <nzeitler@osii.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Lite5200 and PCI1520
Date: Mon, 13 Dec 2004 22:13:25 +0100 [thread overview]
Message-ID: <20041213211330.CE496C1430@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 13 Dec 2004 11:50:20 CST." <01C22B6B78D52B46BE3C38FB525617EF909AC5@osimail.osii.com>
In message <01C22B6B78D52B46BE3C38FB525617EF909AC5@osimail.osii.com> you wrote:
>
> and write to CompactFlash devices behind a PCI1520 PCI bridge on a
> custom Lite5200 board. I am admittedly new to this process within
Now what? Is it a custom board, or a Lite5200?
> embedded devices and could use some direction. We're using a recent
> 2.4.25 kernel from Denx, as well as UBOOT 1.1.1 and ELDK2.1.
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).
> I can't access anything plugged into the sockets! PCI1520 registers
> detect a card is inserted, but I can't read and write to flash cards
> from Linux. I checked out PCMCIA Card Services from CVS, compiled and
> ran cardmgr and it gives a seg-fault, but indicates it is watching the
What's you PCMCIA config file looking like?
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
Perl already has an IDE. It's called Unix.
-- Tom Christiansen in 375bd509@cs.colorado.edu
next prev parent reply other threads:[~2004-12-13 22:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-13 17:50 Lite5200 and PCI1520 Zeitler, Nathan
2004-12-13 21:13 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-13 22:09 Zeitler, Nathan
2004-12-13 23:48 ` Andrew Dennison
2004-12-14 0:32 ` Wolfgang Denk
2004-12-14 1:25 ` Andrew Dennison
2004-12-14 0:06 Zeitler, Nathan
2004-12-14 0:45 ` Andrew Dennison
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=20041213211330.CE496C1430@atlas.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@ozlabs.org \
--cc=nzeitler@osii.com \
/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).