From: Reinhard Meyer <r.meyer@emk-elektronik.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] RTC for MPC5200
Date: Thu, 15 Jan 2004 13:58:19 +0100 [thread overview]
Message-ID: <073401c3db67$4c4bb410$6d4ba8c0@alb.sub.de> (raw)
In-Reply-To: 20040115110025.46CFCC10AF@atlas.denx.de
Dear Wolfgang,
> In message <06cc01c3db51$e2f496e0$6d4ba8c0@alb.sub.de> you wrote:
> > supports only the MPC5200 and nothing else
> MGT5100?
I do not have the 5100 datasheet (and I cannot find any on the
www.mot-sps.com site), nor do I have 5100 hardware to verify.
If you can mail me a 5100 datasheet I am willing to have a look at its RTC
and if similiar enough I will modify the source to accomodate both.
But I cannot test it with a 5100, that would be up to someone else (you?)
> I _had_ to complain because ther eis some tendency to drop arbitray
> source files to the list with just laconic comments "this is what I
> am using - feel free to try it - it's sink or swim."
I was not trying to go in this tendency, though of course I can only test
new stuff on our own hardware.
> Of course it can. See the documentation in the README (and/or read in
> the diff man page about the "-N" option).
I _am_ using
cvs -z6 -d :pserver:anonymous at cvs.sourceforge.net:/cvsroot/u-boot diff -puRN
u-boot >u-boot.patch.txt
but files that are new in my tree do not show up in the patch. A hand made
diff like
diff -puN /dev/null u-boot/rtc/mpc5200.c
does the trick, however.
Reinhard
prev parent reply other threads:[~2004-01-15 12:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-08 21:05 [U-Boot-Users] RTC for MPC5200 Victor Wren
2004-01-08 22:56 ` Wolfgang Denk
2004-01-09 0:23 ` Victor Wren
2004-01-09 6:46 ` Wolfgang Denk
2004-01-09 16:51 ` Reinhard Meyer
2004-01-09 20:11 ` Reinhard Meyer
2004-01-15 9:18 ` Wolfgang Denk
2004-01-15 10:22 ` Reinhard Meyer
2004-01-15 11:00 ` Wolfgang Denk
2004-01-15 12:58 ` Reinhard Meyer [this message]
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='073401c3db67$4c4bb410$6d4ba8c0@alb.sub.de' \
--to=r.meyer@emk-elektronik.de \
--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