public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Aaron Williams <Aaron.Williams@caviumnetworks.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] New to U-boot development, adding Octeon support
Date: Fri, 12 Nov 2010 13:45:22 -0800	[thread overview]
Message-ID: <201011121345.22528.Aaron.Williams@caviumnetworks.com> (raw)

Hi,

I am rather new to U-boot development and will be working on migrating the 
current Cavium Octeon U-boot code to a much more up to date version but I 
first have some questions.

My goal is to be able to hopefully submit the changes back into the main U-
boot tree and do this as cleanly as possible.

One of the first things I came across is that we need some significant 
changes to some of the MIPS specific libraries and start-up code. Should I 
just create separate files under arch/mips/xxx or should I create 
subdirectories for the Octeon platform like how it's done for the PowerPC? 
These changes would be global across the Octeon and not board specific. A 
number of the changes are required for handling multiple cores.

Down the road we would also like to add our own replacements to some of the 
functions provided by U-boot to speed it up on our platform, for example 
taking advantage of the hardware CRC and decompression features.

Also, what would be a good stable starting version to work from?

-Thanks.

-Aaron Williams

             reply	other threads:[~2010-11-12 21:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12 21:45 Aaron Williams [this message]
2010-11-12 23:10 ` [U-Boot] New to U-boot development, adding Octeon support 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=201011121345.22528.Aaron.Williams@caviumnetworks.com \
    --to=aaron.williams@caviumnetworks.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