From: Curt Brune <curt@acm.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] SoC -- a new port and coding style
Date: Sun, 29 Feb 2004 14:52:11 -0800 [thread overview]
Message-ID: <20040229145211.B7611@curtisb.com> (raw)
I have a "porting to a new chip" question. I see the u-boot directory
structure allows for CPU specific stuff to go in cpu/ and board
specific stuff to go in board/ . My question regards a SoC based on
an ARM7TDMI core from Samsung called the s3c4510.
The "s3c4510" has a whole bunch of registers for the ethernet, uart,
timers, i2c -- none of which has anything to do with the ARM7TDMI
core or the board.
There does not seem to be an appropriate place in the u-boot directory
structure to put the "s3c4510" specific stuff -- it has nothing to do
the CPU and it is not board specific either (I've seen at least 3
other boards based on the Samsung chip which configure the s3c4510
differently).
Where would be the "right" place to put such changes? Seems I could:
a. jam them in cpu/arm720t with #ifdef
b. create cpu/arm7tdmi and include the s3c4510 in board/
c. create cpu/s3c4510
Cheers,
Curt
next reply other threads:[~2004-02-29 22:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 22:52 Curt Brune [this message]
2004-02-29 23:55 ` [U-Boot-Users] SoC -- a new port and coding style 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=20040229145211.B7611@curtisb.com \
--to=curt@acm.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