public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Reinhard Meyer <u-boot@emk-elektronik.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] U-Boot support for board(s) meesc, otc570
Date: Tue, 18 Jan 2011 13:25:59 +0100	[thread overview]
Message-ID: <4D3586D7.7040009@emk-elektronik.de> (raw)
In-Reply-To: <4D3577A9.8050505@esd.eu>

Dear Daniel Gorsulowski,
> Hello Albert,
> 
> Albert ARIBAUD wrote:
>> Le 18/01/2011 10:27, Daniel Gorsulowski a ?crit :
>>> Hello again!
>>
>> Hi Daniel,
>>
>>> One month ago, I asked you for help (see message below), but got no
>>> answer.
>>
>> Sorry about that. Last quarter of 2010 was rather busy for me.
>>
>>> Do you see any chance, to fix the at91 tree?
>>>
>>> There is no way to fix my boards, as long as all at91 builds have
>>> fundamental problems.
>>>
>>> I found a patch series from Alexander Stein, but it seems, this series
>>> does not go mainline:
>>> http://lists.denx.de/pipermail/u-boot/2010-November/080885.html
>>> Should I ask Alexander for resend his pathes?
>>>
>>> Regards
>>> Daniel
>>
>> Reinhard (Cc:) has lots of fixes in his u-boot-atmel tree; you should try
>> its master branch. I'm leaving below your (unanswered, apologies again)
>> questions for Reinhard to answer.
>>
>> Regards,
>> Albert.
> 
> Thanks for your response!
> I tried Reinhards master branch, but build throws same errors as shown
> below. It seems, among other things the atmel usart driver needs an
> update to new SoC access. Alexander Steins patch series seems to add this
> support.
> 
> I'll wait for a fix until I send patches for my boards.

1. Please send always the mailing list, too!

2. Use the rework101229 branch (minus the last 5 patches).

There is lot of cleanup done in the header files and the ATMEL drivers.
The at91sam9260(9xe)ek board builds fine and works.
Use that as a template or reference what to do.
You should *only* need to adapt board/*/files and your configs/<board>.h
files. And of course updated entries in boards.cfg.

Once the rework is done for *almost* *ALL* AT91 SoCs it will be put for
review into mainline, probably for the 06.2011 U-Boot.

Best Regards,
Reinhard

       reply	other threads:[~2011-01-18 12:25 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20101127215828.7CD40220233A@lilith>
     [not found] ` <4D072AED.6080703@esd.eu>
     [not found]   ` <4D355CFC.5050806@esd.eu>
     [not found]     ` <4D356200.5000801@aribaud.net>
     [not found]       ` <4D3577A9.8050505@esd.eu>
2011-01-18 12:25         ` Reinhard Meyer [this message]
2011-01-20  7:48           ` [U-Boot] U-Boot support for board(s) meesc, otc570 Daniel Gorsulowski
2011-01-21  6:43             ` Reinhard Meyer
2011-01-21  9:11               ` Daniel Gorsulowski
2011-01-21 10:44                 ` Reinhard Meyer
2011-01-21 11:17                   ` Daniel Gorsulowski
2011-01-21 11:50                     ` Reinhard Meyer
2011-01-21 12:39                       ` Daniel Gorsulowski
2011-01-21 13:21                         ` Reinhard Meyer
2011-01-24 11:39                 ` Daniel Gorsulowski
2011-01-24 12:08                   ` Reinhard Meyer
2011-01-25 18:13                   ` Albert ARIBAUD
2011-04-11 10:11                   ` Reinhard Meyer

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=4D3586D7.7040009@emk-elektronik.de \
    --to=u-boot@emk-elektronik.de \
    --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