From: Thomas Elste <info@elste.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Patch for ModNET50 board and NET+50 CPU
Date: Tue, 10 Feb 2004 16:33:25 +0100 [thread overview]
Message-ID: <opr25utze9940igx@smtp.elste.org> (raw)
In-Reply-To: <opr2ycf4kg940igx@smtp.elste.org>
>> I've ported U-Boot for the ModNET50 board from FSForth. The
>> board uses a NET+50 CPU from Netsilicon, an ARM7TDMI without
>> MMU. A patch for this CPU is also included.
> If possible, I would like to avoid creating a new CPU directory which
> just duplicates existing code.
Ok, I've changed the layout, so that the arm720t cpu directory
is used. The serial i/o stuff differs a lot, so I've created a
new file: serial_netarm.c . Anything else is done by ifdefs now.
> In the meantime I added the patch which changed the ARM memory
> layout. This obsoletes your patch.
> I'm afraid I have to ask you to resubmit this patch.
No problem, here's the new one (against todays CVS).
best regards
Thomas
--
Thomas Elste
Institut fuer Mikroelektronik- und Mechatronik-Systeme
www.imms.de
Langewiesener Strasse 22
98693 Ilmenau
-------------- next part --------------
A non-text attachment was scrubbed...
Name: u-boot-modnet50.diff.bz2
Type: application/bzip2
Size: 21906 bytes
Desc: not available
Url : http://lists.denx.de/pipermail/u-boot/attachments/20040210/4e7d819f/attachment.bin
next prev parent reply other threads:[~2004-02-10 15:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 14:13 [U-Boot-Users] Patch for ModNET50 board and NET+50 CPU Thomas Elste
2004-02-10 0:02 ` Wolfgang Denk
2004-02-10 15:33 ` Thomas Elste [this message]
2004-02-23 19:30 ` Wolfgang Denk
[not found] ` <opr3valsnmzmlzqt@smtp.web.de>
2004-02-24 13:39 ` Thomas Elste
2004-02-26 23:19 ` 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=opr25utze9940igx@smtp.elste.org \
--to=info@elste.org \
--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