public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Kyungmin Park <kyungmin.park@samsung.com>
To: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: OneNAND on PXA-270?
Date: Wed, 08 Nov 2006 23:44:13 +0000 (GMT)	[thread overview]
Message-ID: <13165051.297441163029462867.JavaMail.weblogic@ep_ml25> (raw)

Hi,

> We're evaluating the Samsung OneNAND to replace the NAND and NOR chips in
> our PXA-270-based device.  We're using 2.6.18 and it looks like the MTD
> drivers are there, and we understand a little about x-loader and u-boot
> sharing the first 128K block.  Does anyone have experience booting Linux
> from the OneNAND on a PXA machine?  Specifically, we're interested in:

> 1) flashing the OneNAND over JTAG (we use Abatron bdi-2000)

As I know, bdi can't program onenand directly.

> 2) how to modify u-boot, if needed, to be entered by x-load

Just use your u-boot, we only need a xloader

After build xloader, just merge two image xloader + uboot.
Of course, you can find merge script in xloader scripts directory.

> 3) JFFS2 performance, funky mkfs parameters/caveats

In our test environment, apollon based on omap2420 with latest mtd tree

warning: process `iozone' used the removed sysctl system call
        Iozone: Performance Test of File I/O
                Version $Revision: 3.260 $
                Compiled for 32 bit mode.
                Build: linux-arm

        Run began: Thu Nov  9 08:31:37 2006

        Auto Mode 2. This option is obsolete. Use -az -i0 -i1
        File size set to 30720 KB
        Command line used: iozone -A -s 30m -U /jffs2 -f /jffs2/test
        Output is in Kbytes/sec
        Time Resolution = 0.000030 seconds.
        Processor cache size set to 1024 Kbytes.
        Processor cache line size set to 32 bytes.
        File stride size set to 17 * record size.

              KB  reclen   write rewrite    read    reread
           30720       4    4738    4787     8535    15577
           30720       8    5414    4771    15776    15706
           30720      16    4803    6009    15832    15844
           30720      32    4793    4805     8623    15913
           30720      64    5438    4810    16050    16011
           30720     128    4856    6204    16195    16174
           30720     256    4838    4881     8657    16253

> The version of x-load that I found online has support for three OMAP
> boards and no cpu/pxa folder (which I assume is taken straight from
> u-boot).  Can someone send source for x-load adopted to their pxa machine?

you can find pxa support here.

http://source.mvista.com/git/gitweb.cgi?p=xloader.git;a=log

refer to i580 board which is based on pxa270.

Thank you,
Kyungmin Park

             reply	other threads:[~2006-11-08 23:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-08 23:44 Kyungmin Park [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-11-08 17:44 OneNAND on PXA-270? Pete MacKay

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=13165051.297441163029462867.JavaMail.weblogic@ep_ml25 \
    --to=kyungmin.park@samsung.com \
    --cc=linux-mtd@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox