Hi Scott:
Thanks!
I am also wondering if there is a include file which builds up a table
of working NAND devices and thier attributes which tells the U-boot on
the parameters about a particular NAND device on the board like
Block_size , page_size, device size, pages per block, device id etc.
alfred steele wrote:
Hi Scott:
Thanks!
I am also wondering if there is a include file which builds up a table
of working NAND devices and thier attributes which tells the U-boot on
the parameters about a particular NAND device on the board like
Block_size , page_size, device size, pages
Hi Scott,
Thanks!
The only requirement i have currently is to be able to populate the
device table with the Samsung K9F1G08R0A because it does not
appear in the existing list. This would help the NFC read the part id
and the other NAND attributes correctly on the target.
Thanks Reagrds,
Hi Scott,
Thanks!
The only requirement i have currently is to be able to populate the
device table with the Samsung K9F1G08R0A because it does not
appear in the existing list. This would help the NFC read the part id
and the other NAND attributes correctly on the target.
Thanks Regards.
On
alfred steele wrote:
Thanks!
The only requirement i have currently is to be able to populate the
device table with the Samsung K9F1G08R0A because it does not
appear in the existing list. This would help the NFC read the part id
and the other NAND attributes correctly on the target.
The
Thanks Again,
I am actually confused with the values for chip size which should be
the total chip size in MB w.r.t nand_flash_dev structure and
pagesize as pagesize seems to be extended bytes alone in the
datasheet which i am unable to figure of as of now. The pagesize seems
to be different from
2009/3/31 alfred steele alfred.jaq...@gmail.com:
Thanks Again,
I am actually confused with the values for chip size which should be
the total chip size in MB w.r.t nand_flash_dev structure and
pagesize as pagesize seems to be extended bytes alone in the
datasheet which i am unable to figure
alfred steele wrote:
I am actually confused with the values for chip size which should be
the total chip size in MB w.r.t nand_flash_dev structure and
pagesize as pagesize seems to be extended bytes alone in the
datasheet which i am unable to figure of as of now. The pagesize seems
to be
Hi Magnus,
Thanks!
Do you remember, off the head, what kind of hardware differences
between MX31 and Phycore. I am kind of trying to identify the
differences between the two in order to be able to map the patch to
the differences.
Was the nand_spl directory created for imx31(PDK) NAND specific
On Mon, Mar 30, 2009 at 11:48:57AM -0500, alfred steele wrote:
Was the nand_spl directory created for imx31(PDK) NAND specific
changes.
No. It has a board subdirectory where board-specific code goes, plus
some board-independent drivers.
I am also wondering if there is a include file which
Hi
2009/3/30 alfred steele alfred.jaq...@gmail.com:
Hi Magnus,
Thanks!
Do you remember, off the head, what kind of hardware differences
between MX31 and Phycore. I am kind of trying to identify the
differences between the two in order to be able to map the patch to
the differences.
Was
Hi Scott:
Thanks!
I am also wondering if there is a include file which builds up a table
of working NAND devices and thier attributes which tells the U-boot on
the parameters about a particular NAND device on the board like
Block_size , page_size, device size, pages per block, device id etc.
Hi All;
Is there an available port for IMX31 3stack with NAND boot.
I am looking for a U-boot port for IMX31 stack( which supports NAND boot.
The closest matches i know of as of now are as follows:
MX-31 ADS
MX-31 Phycore
Openmoko U-boot (Samsung processor though ARM) - This is the only one
Hi
2009/3/27 alfred steele alfred.jaq...@gmail.com:
Hi All;
Is there an available port for IMX31 3stack with NAND boot.
I am looking for a U-boot port for IMX31 stack( which supports NAND boot.
The closest matches i know of as of now are as follows:
MX-31 ADS
MX-31 Phycore
Openmoko
Thanks Magnus,
How difficult or rather much an effort would it need to add NAND boot
support and make it work on MX35 or MX31 3stack board.
Are there any existing guidelines for accelerating the development or
is the generic uboot porting guidelines .
Regards,
Alfred
On Fri, Mar 27, 2009 at
2009/3/27 alfred steele alfred.jaq...@gmail.com:
Thanks Magnus,
How difficult or rather much an effort would it need to add NAND boot
support and make it work on MX35 or MX31 3stack board.
Are there any existing guidelines for accelerating the development or
is the generic uboot porting
16 matches
Mail list logo
