On Mon, Jan 16, 2012 at 3:32 AM, Michael Hope wrote:
> Hi there. I have a style question. For the pre-built versions of
> gcc-linaro, should we release a i686 version that also runs on x86_64,
> or do separate i686 and x86_64 builds?
>
> If we do just an i686 version then:
> * There's less to t
: Javier Martinez Canillas
---
arch/arm/mach-omap2/board-flash.c |4 ++--
arch/arm/mach-omap2/board-flash.h | 11 +++
2 files changed, 13 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-omap2/board-flash.c
b/arch/arm/mach-omap2/board-flash.c
index 0349fd2..70a81f9 100644
IGEP-based boards can have two different flash memories, a OneNAND or
a NAND device. The boot configuration pins (sys_boot) are used to
specify which memory is available.
Also, this patch removes unnecesary code for registering the OneNAND.
Signed-off-by: Javier Martinez Canillas
---
arch/arm
On Wed, Apr 25, 2012 at 9:59 AM, Enric Balletbò i Serra
wrote:
> 2012/4/4 Javier Martinez Canillas :
>> board_onenand_init() and board_nand_init() initialization functions are
>> used to initialize OneNAND and NAND memories respectively. But only
>> board_nand_init() was vi
On Wed, Apr 25, 2012 at 10:00 AM, Enric Balletbò i Serra
wrote:
> 2012/4/4 Javier Martinez Canillas :
>> IGEP-based boards can have two different flash memories, a OneNAND or
>> a NAND device. The boot configuration pins (sys_boot) are used to
>> specify which memory is
On Wed, May 9, 2012 at 1:16 AM, Tony Lindgren wrote:
> * Javier Martinez Canillas [120427 02:33]:
>> On Wed, Apr 25, 2012 at 9:59 AM, Enric Balletbò i Serra
>> wrote:
>> >
>> > Tony, as this is a fix ,may be included ?
>> >
>> > Acked-by: Enric