[U-Boot] Patches for new at91 board / lowlevel_init.S

[U-Boot] Patches for new at91 board / lowlevel_init.S

[Michael Roth]

Hello,

I'm having patches for a new at91sam9261 based board in my queue I would
like to publish for the current merge window.

However, this patch needs a way to supply its own lowlevel_init.S
instead the at91 default.

A week ago I asked a question about that topic and there was a hint to
look for the ronetix patches and a note that the next U-Boot release
will contain a solution.

However, the mentioned ronetix patch followed a discussion about
possible ways to address this topic but as far I can see, no solution
was selected.

Additionally, in the current git tree there is still no solution for
this topic, too (or I'm missing something).

So my question is:

How should I proceed? Should I post my solution? Or should I wait a
couple of more days for an "official" solution?


Michael Roth

[U-Boot] Cloning, Maybe silly question

[Pink Boy]

I have a suggestion/question.

Would it be easy, hard, silly to add a CLONE command to the make 
file?  (Are a separate make script?)  So if someone wants to create 
a new board based on an existing board they could just type,

make CLONE at91sam6263ek_CONFIG myboard

or if it's script 

./clone.sh at91sam6263ek_CONFIG myboard

The make file would clone the at91sam9263ek board configuration
and put it in a new directory called myboard and update the 
makefile?

Matt Harper
Tehama Wireless.

[U-Boot] Cloning, Maybe silly question

[Wolfgang Denk]

Dear Pink Boy,

In message <959751.81577.qm@web31812.mail.mud.yahoo.com> you wrote:
> 
> I have a suggestion/question.
> 
> Would it be easy, hard, silly to add a CLONE command to the make 
> file?  (Are a separate make script?)  So if someone wants to create 
> a new board based on an existing board they could just type,

Easy and silly. You cannot do such stuff automatically without doing
stupid things like copying a lot of code that either is board specific
or should be shared.

> The make file would clone the at91sam9263ek board configuration
> and put it in a new directory called myboard and update the 
> makefile?

And what would that save you? 2 minutes of work in a one man-week
task?

Best regards,

Wolfgang Denk

-- 
DENX Software Engineering GmbH,     MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
If it has syntax, it isn't user friendly.

[U-Boot] Patches for new at91 board / lowlevel_init.S

[Jean-Christophe PLAGNIOL-VILLARD]

On 23:57 Sat 24 Jan     , Michael Roth wrote:
> Hello,
> 
> I'm having patches for a new at91sam9261 based board in my queue I would
> like to publish for the current merge window.
> 
> However, this patch needs a way to supply its own lowlevel_init.S
> instead the at91 default.
I'll apply a patch that allow this at the beginning of the week
with 2 boards that use it.

I you search on the ML you will find the patch in question which is about the
Ronetix PM9263

Best Regards,
J.

[U-Boot] Patches for new at91 board / lowlevel_init.S

[Michael Roth]

Jean-Christophe PLAGNIOL-VILLARD schrieb:

> I'll apply a patch that allow this at the beginning of the week
> with 2 boards that use it.

Ok, fine!  I will wait and then base my patch on your implementation.

Thank you!


Michael Roth