From: Carsten Schlote <c.schlote@konzeptpark.de>
To: barebox@lists.infradead.org
Subject: Updated MPC5200B support (pcm030, kp-mcb2, ...)
Date: Thu, 22 Apr 2010 12:10:56 +0200 [thread overview]
Message-ID: <1271931056.12005.59.camel@kplaws107lx> (raw)
Hi,
yesterday I spent some time to get BareBox up and running on MPC5200B
again. Finally I got it working on our hardware. Not yet tested for
phytec pcm030, but I'm sure that without some fixes it won't work out of
the box.
I found and hacked/fixed the following problems so far:
- cfi_flash driver has problems with big-endian. Some byte swapping is
done in readb()/writeb() at HW access layer and also at several other
places in the CFI driver. Swapping things twice isn't exactly what the
driver and the flashdevice expects and needs a lot of more cleanups.
- Detection of flash/bank layout was hacked to workaround 'faulty'
values read from flash device (might be also a chip or HW design
problem, I need to check that in more detail)
- CFI flash buffer writes are broken with big-endian as well
- Some problems and old bugs from the u-boot-v1 era found in cpu_init.c.
Fortunately the HW did the right things although some register setups
were broken.
- Missing headers for arch/ppc to compile the liblzo code.
(unsigned.h ?)
Now with network, flash and basic debugging outputs available I would
like to port some more drivers and at least RO filesystems (fat, jffs2,
ext2/3/4) for MPC5xxx platform and replace the stone-age crappy u-boot
asap.
Just in case - Is there any on-going or even experimental work for MPC I
could start with?
--
Carsten Schlote <c.schlote@konzeptpark.de>
konzeptpark.de
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
reply other threads:[~2010-04-22 10:11 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=1271931056.12005.59.camel@kplaws107lx \
--to=c.schlote@konzeptpark.de \
--cc=barebox@lists.infradead.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