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:56:36 -0700 [thread overview]
Message-ID: <4FF629B4.9000706@cavium.com> (raw)
In-Reply-To: <4FF5943E.8010303@gmail.com>
Hi Andreas,
We have been shipping 2011.03 for some time and internally are planning
to use 2012.07 when it is released since we are tracking the top of
trunk. We have made a lot of improvements since then and added a lot of
new capabilities.
-Aaron
On 07/05/2012 06:18 AM, Andreas Bie?mann wrote:
> Dear sayed zahid,
>
> On 05.07.2012 13:42, 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?
> I guess no. I had to work with some non mainlined version of u-boot
> provided by cavium a year ago (or something around that). At that time
> we got a
>
> ---8<---
> abiessmann at azuregos % git grep U_BOOT_VERSION include/version.h
> include/version.h:#define U_BOOT_VERSION "U-Boot 1.1.1"
> --->8---
>
> :(
>
> AFAIR there was a lot of basic stuff missing in mainline U-Boot to get
> Cavium mips64 running at that time so I didn't start to port these
> proprietary changes (well it would not have been accepted the way it was
> written down; beside that cavium forced us to sign a NDA for that piece
> of GPL code).
>
> I have not followed their open source efforts since then, but I saw a
> lot of work on the linux-mips list by David Daney and I think Aaron
> Williams is working for Cavium too and is on this list. Maybe one of
> them can comment?
>
>> 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
> You should not hesitate to contact their support and ask for proper
> mainline support of u-boot ;)
>
> Enough Cavium bashing.
>
> Regarding your question for documents, I'm sorry I can not help you
> here. I recommend start working with some mainlined device which is
> comparable, get firm with the architecture, try to find commonalities,
> get the new cpu in u-boot step by step.
>
> Best regards
>
> Andreas Bie?mann
>
--
Aaron Williams
Software Engineer
Cavium, Inc.
(408) 943-7198 (510) 789-8988 (cell)
next prev parent reply other threads:[~2012-07-05 23:56 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 [this message]
2012-07-06 8:09 ` Andreas Bießmann
2012-07-05 23:52 ` Aaron Williams
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=4FF629B4.9000706@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