Hi,
Please see last set of queries inline..
From: Scott Wood [mailto:scottw...@freescale.com]
On Sat, 2013-09-28 at 06:24 +, Gupta, Pekon wrote:
From: Scott Wood [mailto:scottw...@freescale.com]
On Fri, 2013-09-27 at 04:18 +, Gupta, Pekon wrote:
[snip]
(1)
On Wed, 2013-10-02 at 14:40 +, Gupta, Pekon wrote:
Hi,
Please see last set of queries inline..
From: Scott Wood [mailto:scottw...@freescale.com]
On Sat, 2013-09-28 at 06:24 +, Gupta, Pekon wrote:
From: Scott Wood [mailto:scottw...@freescale.com]
On Fri, 2013-09-27 at
On 25/09/13 06:23, Pekon Gupta wrote:
NAND driver needs to know bus-width of the connected NAND device, in order to
perform proper I/O and initialize itself. Currently there is no CONFIG option
to provide this information to NAND driver.
- SPL NAND driver does not have framework to parse ONFI
Hi Mark,
From: Mark Jackson [mailto:mpfj-l...@newflow.co.uk]
To: Gupta, Pekon; scottw...@freescale.com; Rini, Tom
snip
diff --git a/include/configs/am335x_evm.h
b/include/configs/am335x_evm.h
index 978bca7..c92cb2f 100644
--- a/include/configs/am335x_evm.h
+++
On Sat, 2013-09-28 at 06:24 +, Gupta, Pekon wrote:
From: Scott Wood [mailto:scottw...@freescale.com]
On Fri, 2013-09-27 at 04:18 +, Gupta, Pekon wrote:
Apart from SPL, CONFIG_SYS_NAND_DEVICE_WIDTH also be useful for
(1) drivers which do not use CONFIG_SYS_NAND_ONFI_DETECTION,
From: Scott Wood [mailto:scottw...@freescale.com]
On Fri, 2013-09-27 at 04:18 +, Gupta, Pekon wrote:
From: Scott Wood [mailto:scottw...@freescale.com]
On Thu, 2013-09-26 at 13:14 +, Gupta, Pekon wrote:
From: Gupta, Pekon pe...@ti.com
[snip]
The changelog that
On Fri, 2013-09-27 at 04:18 +, Gupta, Pekon wrote:
From: Scott Wood [mailto:scottw...@freescale.com]
On Thu, 2013-09-26 at 13:14 +, Gupta, Pekon wrote:
From: Gupta, Pekon pe...@ti.com
NAND driver needs to know bus-width of the connected NAND device,
in
order to
(re-sending by dropping cc-list, as u-boot maillist moderated earlier mail
saying
Too many recipients to the message :-) )
From: Scott Wood [mailto:scottw...@freescale.com]
On Wed, 2013-09-25 at 22:08 +, Woodruff, Richard wrote:
Short comment. Apologies for top posting:
The
On Thu, 2013-09-26 at 13:14 +, Gupta, Pekon wrote:
From: Gupta, Pekon pe...@ti.com
NAND driver needs to know bus-width of the connected NAND device, in
order to perform proper I/O and initialize itself. Currently there is no
CONFIG
option to provide this information to NAND
From: Scott Wood [mailto:scottw...@freescale.com]
On Wed, 2013-09-25 at 22:08 +, Woodruff, Richard wrote:
Short comment. Apologies for top posting:
The first incarnations of SPL and loader mainly cared about the boot flash
device.
Is there an SPL that cares about something
From: Scott Wood [mailto:scottw...@freescale.com]
On Thu, 2013-09-26 at 13:14 +, Gupta, Pekon wrote:
From: Gupta, Pekon pe...@ti.com
NAND driver needs to know bus-width of the connected NAND device,
in
order to perform proper I/O and initialize itself. Currently there is no
Short comment. Apologies for top posting:
The first incarnations of SPL and loader mainly cared about the boot flash
device.
OMAPs require a resistor strap to specify the width of the boot device. The
values is latched for SW to read.
As such always a run time check of width was sufficient
On Wed, 2013-09-25 at 22:08 +, Woodruff, Richard wrote:
Short comment. Apologies for top posting:
The first incarnations of SPL and loader mainly cared about the boot flash
device.
Is there an SPL that cares about something other than the boot device
now?
OMAPs require a resistor
13 matches
Mail list logo
