All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodel Miguel <RodelFMiguel@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Porting U-Boot to an ARM920T-Based Board.
Date: Tue, 5 Oct 2004 23:56:37 +0800	[thread overview]
Message-ID: <515b5ffa04100508563e7d6b6f@mail.gmail.com> (raw)

Hi,

I would like to get some help to port u-boot on a new hardware (the
hardware is still under heavy development).

I have listed the following issues which I've encountered while
reading the README and browsing the source tree.

1.  My board has an ARM920T core.  Instinctively, I would choose a
"template" board support subdirectory that has the same core.  If my
platform is very different from the template,  can I just choose the
board that fits my needs (e.g. UART, FLASH, MEMORY MAP, etc.) and just
re-configure the core?  If this is possible, how do I do this?

2.  My UART port is 16550 compliant.  The ARM920T core (cpu/arm920T/)
is using a serial.c that is compliant to S3C24XX.  Can I just simply
overwrite cpu/arm920t/serial.c with 16550 compliant serial.c?

3.  Can somebody please tell me the files that are most-likely to
change when porting u-boot to a new platform?  Currently I am
modifying the following:

     board/myboard /* copied from board smdk2410 */
          - What should be placed here?  Initialization routines? 
What is the "minimal" requirement for this subdirectory?

     Makefile - to make our board noticable to the main kernel tree

     include/configs/myboard.h

4. Are there other important files to modify in order to build the
proper u-boot image?

Please advise on the stated issues.  Thank you very much.

Regards,
Rodel Miguel

             reply	other threads:[~2004-10-05 15:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-05 15:56 Rodel Miguel [this message]
2004-10-05 17:17 ` [U-Boot-Users] Porting U-Boot to an ARM920T-Based Board 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=515b5ffa04100508563e7d6b6f@mail.gmail.com \
    --to=rodelfmiguel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.