Send Davinci-linux-open-source mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-
source
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Davinci-linux-open-source digest..."
Today's Topics:
1. jffs2 and uImage (Bluebird-Eran Segal)
2. RE: Problem with u-boot and flash MT29F16G08DAA (Maupin, Chase)
3. RE: jffs2 and uImage (Maupin, Chase)
4. Re: VLYNQ support (Hugo Villeneuve)
5. Re: RE: Problem with u-boot and flash MT29F16G08DAA
(ashish pareek)
----------------------------------------------------------------------
Message: 1
Date: Wed, 17 Dec 2008 15:41:20 +0200
From: "Bluebird-Eran Segal" <[email protected]>
Subject: jffs2 and uImage
To: <[email protected]>
Message-ID:
<!~!UENERkVCMDkAAQACAAAAAAAAAAAAAAAAABgAAAAAAAAAiw6KQszGrEy0OrE32EtwicKAAAAQAAAAoes/[email protected]
>
Content-Type: text/plain; charset="us-ascii"
HI
I am trying to create flash jffs2 FS and uImage into NOR flash and
boot the board from the NOR flash in MVL401 2.6.10 kernel DVEVM board.
Can any one please tell me how can do it?
Eran S
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/20081217/a33e0ff5/attachment-0001.htm
------------------------------
Message: 2
Date: Wed, 17 Dec 2008 08:07:56 -0600
From: "Maupin, Chase" <[email protected]>
Subject: RE: Problem with u-boot and flash MT29F16G08DAA
To: "[email protected]" <[email protected]>
Cc: "[email protected]"
<[email protected]>,
"[email protected]" <[email protected]>
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
In my testing that was enough to support 4K nand pages. The only
other thing that needed to change was that in nand_ids.c the older
NAND chips can share the same device id as the new one. Thus the
new NAND chip is detected incorrectly and the page size is wrong.
i.e. for Samsung the NAND id for the 512MB nand chip was 0xd5 and
the id for the new chip was 0xD5. Since these are hex values the
new chip was mistakenly detected as a 512MB part. You may need to
comment out the old part.
Lastly, there is a limitation in the nand_base.c code of 2GB for the
total size of the nand chip. This is because they use a signed
value for the offset which causes bit extension during calculation
of the nand chip to use for the offset. Assuming this was fixed
there is then a 4GB limitation in the MTD subsystem.
Still, to at least get 2GB of NAND with 4K page sizes all I needed
to do was update the nand_ids.c file and increase the
NAND_MAX_OOBSIZE variable to 128.
Sincerely,
Chase Maupin
Software Applications
Catalog DSP Products
e-mail: [email protected]
phone: (281) 274-3285
-----Original Message-----
From: Felipe Balbi [mailto:[email protected]]
Sent: Monday, December 15, 2008 2:29 PM
To: Maupin, Chase
Cc: [email protected]; [email protected]; davinci-
linux-
[email protected]
Subject: Re: Problem with u-boot and flash MT29F16G08DAA
On Mon, Dec 15, 2008 at 02:19:24PM -0600, Maupin, Chase wrote:
You will definitely need to change the NAND_MAX_OOBSIZE to 128 for
4K
pages. You may also need to change the FFCHARS definition to 4096
to be
safe.
sure, that's an easy guess. But is that really enough in the end ? I
hope so :-)
--
balbi
------------------------------
Message: 3
Date: Wed, 17 Dec 2008 08:17:27 -0600
From: "Maupin, Chase" <[email protected]>
Subject: RE: jffs2 and uImage
To: Bluebird-Eran Segal <[email protected]>,
"[email protected]"
<[email protected]>
Message-ID:
<[email protected]>
Content-Type: text/plain; charset="us-ascii"
Eran,
You can find information on writing the JFFS2 image to NOR flash at
http://wiki.davincidsp.com/index.php?title=Put_JFFS2_Image_to_Flash
Information on creating the JFFS2 image can be found at
http://wiki.davincidsp.com/index.php?title=Create_a_JFFS2_Target_Image
You can use a similar method to write the kernel image to NOR flash
using the cp.b command in u-boot.
Sincerely,
Chase Maupin
Software Applications
Catalog DSP Products
e-mail: [email protected]<mailto:[email protected]>
phone: (281) 274-3285
________________________________
From: davinci-linux-open-source-bounces+chase.maupin=ti....@linux.davincidsp.com
[mailto:davinci-linux-open-source-bounces+chase.maupin=ti....@linux.davincidsp.com
] On Behalf Of Bluebird-Eran Segal
Sent: Wednesday, December 17, 2008 7:41 AM
To: [email protected]
Subject: jffs2 and uImage
HI
I am trying to create flash jffs2 FS and uImage into NOR flash and
boot the board from the NOR flash in MVL401 2.6.10 kernel DVEVM board.
Can any one please tell me how can do it?
Eran S
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/20081217/e8c4a7eb/attachment-0001.htm
------------------------------
Message: 4
Date: Wed, 17 Dec 2008 10:08:24 -0500
From: Hugo Villeneuve <[email protected]>
Subject: Re: VLYNQ support
To: Ottavio Campana <[email protected]>
Cc: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=US-ASCII
On Wed, 17 Dec 2008 11:14:19 +0100
Ottavio Campana <[email protected]> wrote:
Hugo Villeneuve ha scritto:
These patches are necessary to enable the VLYNQ module (power and
clock), and to configure it properly (interface width). Tested with
a custom VLYNQ driver on the SFFSDR board.
Dear Hugo, have you ever seen this ?
https://dev.openwrt.org/browser/trunk/target/linux/ar7/files/drivers/vlynq/vlynq.c
I saw it a few months ago, but eventually we decided to drop support
for vlynq, and I don't even know if it is compatible with your work
or not, but maybe it could be interesting for you.
Ottavio
Hi Ottavio,
Yes, in fact my driver is based on that code :)
Hugo V.
---------------
Hugo Villeneuve
www.hugovil.com
---------------
------------------------------
Message: 5
Date: 17 Dec 2008 15:47:29 -0000
From: "ashish pareek" <[email protected]>
Subject: Re: RE: Problem with u-boot and flash MT29F16G08DAA
To: "Maupin,Chase" <[email protected]>
Cc: "[email protected]"
<[email protected]>,
"[email protected]"
<[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset="iso-8859-1"
Hi Maupin,
Which Hardware did you use ? How different was ur hardware with
Dm355 EVM ? If Yes, Did u just replace existing 2k pg Nand with
another 4k pg Nand because i gess RBL just supports 2k pg Nand
already available their.
Furthur which kernel did u use as base code (2.6.10 or latest GIT
from Montavista i.t 2.6.28) ?
On Wed, 17 Dec 2008 Maupin,Chase wrote :
In my testing that was enough to support 4K nand pages. The only
other thing that needed to change was that in nand_ids.c the older
NAND chips can share the same device id as the new one. Thus the
new NAND chip is detected incorrectly and the page size is wrong.
i.e. for Samsung the NAND id for the 512MB nand chip was 0xd5 and
the id for the new chip was 0xD5. Since these are hex values the
new chip was mistakenly detected as a 512MB part. You may need to
comment out the old part.
Lastly, there is a limitation in the nand_base.c code of 2GB for
the total size of the nand chip. This is because they use a signed
value for the offset which causes bit extension during calculation
of the nand chip to use for the offset. Assuming this was fixed
there is then a 4GB limitation in the MTD subsystem.
Still, to at least get 2GB of NAND with 4K page sizes all I needed
to do was update the nand_ids.c file and increase the
NAND_MAX_OOBSIZE variable to 128.
Sincerely,
Chase Maupin
Software Applications
Catalog DSP Products
e-mail: [email protected]
phone: (281) 274-3285
-----Original Message-----
From: Felipe Balbi [mailto:[email protected]]
Sent: Monday, December 15, 2008 2:29 PM
To: Maupin, Chase
Cc: [email protected]; [email protected]; davinci-
linux-
[email protected]
Subject: Re: Problem with u-boot and flash MT29F16G08DAA
On Mon, Dec 15, 2008 at 02:19:24PM -0600, Maupin, Chase wrote:
You will definitely need to change the NAND_MAX_OOBSIZE to 128
for 4K
pages. You may also need to change the FFCHARS definition to 4096
to be
safe.
sure, that's an easy guess. But is that really enough in the end ? I
hope so :-)
--
balbi
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-
source
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://linux.omap.com/pipermail/davinci-linux-open-source/attachments/20081217/bed6891a/attachment.htm
------------------------------
_______________________________________________
Davinci-linux-open-source mailing list
[email protected]
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
End of Davinci-linux-open-source Digest, Vol 36, Issue 127
**********************************************************
