From: Jerry Van Baren <gvb.uboot@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Reg. working with uboot
Date: Sun, 21 Dec 2008 17:29:28 -0500 [thread overview]
Message-ID: <494EC348.5040302@gmail.com> (raw)
In-Reply-To: <60e43c2d0812210753h36dc651ei97d32948a4c04292@mail.gmail.com>
Vanee S wrote:
> Hi,
> im new to uboot. i need to know what software are required to incorporate
> uboot for hardware based on ARM architecture. it would be great if i can get
> the step by step procedure to incorporate uboot.
Hi Vanee,
1) Use git to clone u-boot:
git clone git://git.denx.de/u-boot.git <your_repository_name>/
2) Read the README. You might start at line 3923 "U-Boot Porting Guide"
<http://git.denx.de/?p=u-boot.git;a=blob;f=README;h=2a553c274c372b014075cf67387dea964bd0722d;hb=HEAD#l3923>
3) Read the DULG manual (it talks about a specific processor and board
in places, but is mostly general purpose).
<http://www.denx.de/wiki/DULG/Manual>
4) Port u-boot to your board.
5) ???
6) Profit!
> what is the use of ELDK?
It is a cross compiler suite.
<http://www.denx.de/wiki/DULG/ELDK>
> what are the files that needs to be customized and how to get the
> information required?
All the information is available on the web + manufacturer's manuals.
You will have to read and understand it - U-Boot is free in the freedom
sense, but not free in that you have to invest your time to understand
it. You can trade off paying money for investing your time.
> Regards,
> S. Vanee
HTH,
gvb
next prev parent reply other threads:[~2008-12-21 22:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-21 15:53 [U-Boot] Reg. working with uboot Vanee S
2008-12-21 16:49 ` Wolfgang Denk
2008-12-30 3:45 ` Vanee S
2008-12-30 10:38 ` Wolfgang Denk
2008-12-21 22:29 ` Jerry Van Baren [this message]
2008-12-21 23:00 ` michael
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=494EC348.5040302@gmail.com \
--to=gvb.uboot@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox