From: Marc Leeman <marc.leeman@barco.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] CVS tree broken for MPC8245-based boards
Date: Thu, 22 Jul 2004 10:48:42 +0200 [thread overview]
Message-ID: <20040722084842.GW417@smtp.barco.com> (raw)
In-Reply-To: <20040722083938.GI13840@nbase.co.il>
> Where register 0x800000e1 is documented? :)
Page 4-51, section 4.11 of the MPC8245 Integrated Processor User's
Manual.
A slightly more verbose bugreport can be downloaded from:
http://scorpius.homelinux.org/~marc/downloads/masterwrite.pdf
It seems to be a known problem inside Motorola.
--
Marc Leeman
Hardware R&D Engineer
Barco Control Rooms
Noordlaan 5, Industriezone, B-8520 Kuurne (BE)
Tel. +32 56 368 428
http://www.barcocontrolrooms.com
mailto:marc.leeman at barco.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.denx.de/pipermail/u-boot/attachments/20040722/dcce5e2c/attachment.pgp
next prev parent reply other threads:[~2004-07-22 8:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-21 23:05 [U-Boot-Users] CVS tree broken for MPC8245-based boards Matthew Karger
2004-07-22 7:25 ` Marc Leeman
2004-07-22 8:39 ` Gleb Natapov
2004-07-22 8:48 ` Marc Leeman [this message]
2004-07-22 8:57 ` Gleb Natapov
2004-08-02 22:04 ` 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=20040722084842.GW417@smtp.barco.com \
--to=marc.leeman@barco.com \
--cc=u-boot@lists.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