Re: [U-Boot] [PATCH 3/5] i.MX6: nitrogen6x/sabrelite: override set_board_name()

Hi Eric, On 19/11/2013 04:40, Eric Nelson wrote: >> I have a major question: if it is possible to detect at runtime, as you >> have already implemented, which is the board where code is running, why >> is it possible to override it for the operator ? >> > First off, I want to clarify things. Ther

Re: [U-Boot] [PATCH 3/5] i.MX6: nitrogen6x/sabrelite: override set_board_name()

Hi Stefano, On 11/18/2013 03:57 AM, Stefano Babic wrote: Hi Eric, On 17/11/2013 18:17, Eric Nelson wrote: Since the nitrogen6x board file auto-detects Nitrogen6x and SABRE Lite boards, override set_board_name to produce one of two values for board_name. Signed-off-by: Eric Nelson --- board

Re: [U-Boot] [PATCH 3/5] i.MX6: nitrogen6x/sabrelite: override set_board_name()

Hi Eric, On 17/11/2013 18:17, Eric Nelson wrote: > Since the nitrogen6x board file auto-detects Nitrogen6x and > SABRE Lite boards, override set_board_name to produce one > of two values for board_name. > > Signed-off-by: Eric Nelson > --- > board/boundary/nitrogen6x/nitrogen6x.c | 14 +

[U-Boot] [PATCH 3/5] i.MX6: nitrogen6x/sabrelite: override set_board_name()

Since the nitrogen6x board file auto-detects Nitrogen6x and SABRE Lite boards, override set_board_name to produce one of two values for board_name. Signed-off-by: Eric Nelson --- board/boundary/nitrogen6x/nitrogen6x.c | 14 +- 1 file changed, 13 insertions(+), 1 deletion(-) diff --g