From: Aaron Williams <Aaron.Williams@cavium.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-boot Porting
Date: Thu, 05 Jul 2012 16:52:50 -0700 [thread overview]
Message-ID: <4FF628D2.20805@cavium.com> (raw)
In-Reply-To: <CAM26VFu7i=_v87MGomqVPv2wDYTX38SMKWqN+EojGtW1eEFkPw@mail.gmail.com>
Hi Zahid,
I am in charge of U-Boot for OCTEON MIPS. I have not pushed the changes
back upstream since the amount of code is enormous (over 430K lines of
code!). Granted, a huge percentage of that is from generated register
files but it is still a huge amount of code. Just the DRAM
initialization code is 9600 lines of code for DDR2 and DDR3 support.
We also do things that no other architecture does with U-Boot such as we
always run in TLB mapped memory. The code is available under GPL but you
need to contact support at cavium.com. With the TLB mapping it no longer
matters where U-Boot is loaded in memory. The same U-Boot binary image
can start executing at any 64K flash boundary in the first 4MB of flash
(so we support the same image as a failsafe and standard bootloader),
any 4MB boundary in RAM (when booted over PCI or eJTAG) and out of L2
cache (our top of trunk copies itself from flash to the L2 cache very
early on to speed up memory initialization). The TLB mapping also allows
U-Boot to be copied to the very top of memory since KSEG0 is rather
limited to only 256MB. This is essential since we can support many GB of
RAM which otherwise requires 64-bit addressing.
I need to push some of my changes back upstream since I have added some
drivers for some temperature sensors, power monitors, fixed the AHCI
driver and added a few features over the standard U-Boot (such as
dynamically generated prompt support).
-Aaron
On 07/05/2012 04:42 AM, sayed zahid wrote:
> Hi ,
> I have basic knowledge of porting u-boot to a new board. But now i have got
> a task to port u-boot on cavium mips based board. As i know that mips
> architecture is already supported, but will it support all cavium octeon
> mips variants? Please put some light on this. I would be glad if you guys,
> give my some idea to where to start with or suggest some documents which
> will help me understand and port on a new architecture
> Regards
> Zahid
>
>
>
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
--
Aaron Williams
Software Engineer
Cavium, Inc.
(408) 943-7198 (510) 789-8988 (cell)
next prev parent reply other threads:[~2012-07-05 23:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 11:42 [U-Boot] U-boot Porting sayed zahid
2012-07-05 13:18 ` Andreas Bießmann
2012-07-05 23:05 ` Daniel Schwierzeck
2012-07-05 23:56 ` Aaron Williams
2012-07-06 8:09 ` Andreas Bießmann
2012-07-05 23:52 ` Aaron Williams [this message]
2012-07-06 8:19 ` Andreas Bießmann
2012-07-06 20:37 ` Aaron Williams
2012-07-09 21:11 ` Daniel Schwierzeck
2012-07-10 22:39 ` Aaron Williams
2012-07-11 5:50 ` 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=4FF628D2.20805@cavium.com \
--to=aaron.williams@cavium.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