Re: [U-Boot] A bit about board.c, board.c

2011-10-28 Thread Albert ARIBAUD
Hi Simon, Le 22/10/2011 18:40, Simon Glass a écrit : > Hi Albert, > > On Sat, Oct 22, 2011 at 12:17 AM, Albert ARIBAUD > wrote: >> Le 22/10/2011 07:11, Simon Glass a écrit : >>> >>> Hi, >>> >>> Each architecture has its own board.c but they are mostly quite similar. >>> >>> New features such as

Re: [U-Boot] A bit about board.c, board.c

2011-11-15 Thread Simon Glass
Hi Wolfgang, On Sun, Oct 23, 2011 at 1:14 AM, Wolfgang Denk wrote: > Dear Simon Glass, > > In message > you > wrote: >> >> My suggestion was: >> >> CONFIG_ARCH_GENERIC_BOARD - you get lib/board.c >> not CONFIG_ARCH_GENERIC_BOARD - you get arch/xxx/lib/board.c > > If we do something like this,

Re: [U-Boot] A bit about board.c, board.c

2011-10-22 Thread Albert ARIBAUD
Le 22/10/2011 07:11, Simon Glass a écrit : > Hi, > > Each architecture has its own board.c but they are mostly quite similar. > > New features such as fdt, boot timing, trace, profiling, etc. must be > done separately for each arch, even if there are no > architecture-specific bits. > > What would

Re: [U-Boot] A bit about board.c, board.c

2011-10-22 Thread Simon Glass
Hi Albert, On Sat, Oct 22, 2011 at 12:17 AM, Albert ARIBAUD wrote: > Le 22/10/2011 07:11, Simon Glass a écrit : >> >> Hi, >> >> Each architecture has its own board.c but they are mostly quite similar. >> >> New features such as fdt, boot timing, trace, profiling, etc. must be >> done separately f

Re: [U-Boot] A bit about board.c, board.c

2011-10-22 Thread Graeme Russ
Hi Simon, On 23/10/11 03:36, Simon Glass wrote: > Hi Graeme, > > Did you mean to send to list? Oops, yes I did - Done now > On Fri, Oct 21, 2011 at 10:49 PM, Graeme Russ wrote: >> Hi Simon >> >> On Oct 22, 2011 4:11 PM, "Simon Glass" wrote: >>> >>> Hi, >>> >>> Each architecture has its own b

Re: [U-Boot] A bit about board.c, board.c

2011-10-22 Thread Graeme Russ
Hi Simon, On 23/10/11 08:41, Graeme Russ wrote: > Hi Simon, > > > On 23/10/11 03:36, Simon Glass wrote: >> Hi Graeme, [snip] >>> I vote to pick an arch, convert it to a unified style and move it to >>> lib/board.c and then merge each arch over. This should be done in a single >>> series rather

Re: [U-Boot] A bit about board.c, board.c

2011-10-23 Thread Wolfgang Denk
Dear Simon Glass, In message you wrote: > > My suggestion was: > > CONFIG_ARCH_GENERIC_BOARD - you get lib/board.c > not CONFIG_ARCH_GENERIC_BOARD - you get arch/xxx/lib/board.c If we do something like this, then the other way round. There should never be any #defines needed for the standard