All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Eric Bénard" <eric@eukrea.com>
To: Daiane Angolini <daiane.list@gmail.com>
Cc: meta-freescale Mailing List <meta-freescale@yoctoproject.org>,
	Otavio Salvador <otavio@ossystems.com.br>
Subject: Re: [meta-fsl-arm PATCH 4/4] mxs-base.inc: Add default settings for UBI filesystem generation
Date: Wed, 18 Sep 2013 15:33:32 +0200	[thread overview]
Message-ID: <20130918153332.64536e4a@e6520eb> (raw)
In-Reply-To: <CA+jg_OV_eC9GFbQ0X2ZG126DEGMM4gA0V5nYHqp+0LH09-+=-w@mail.gmail.com>

Hi Daiane,

Le Wed, 18 Sep 2013 09:58:47 -0300,
Daiane Angolini <daiane.list@gmail.com> a écrit :
> On Wed, Sep 18, 2013 at 9:32 AM, Eric Bénard <eric@eukrea.com> wrote:
> > Le Wed, 18 Sep 2013 09:23:22 -0300,
> > Otavio Salvador <otavio@ossystems.com.br> a écrit :
> >> I had this for loooooong time in my queue and I recall to try it, but
> >> not lately. I will also extend the commit log and move it to mx28evk
> >> board.
> >>
> > no these values are wrong as they come from an i.MX35 tutorial so that
> > won't work on an i.MX28EVK (moreover this board hasn't any NAND
> > populated by default so the values will depend on the NAND flash the
> > user puts in the socket - here I tested with 2k and 4k flashes).
> >
> > So if you can't test it please don't add default values.
> 
> If not use default values, what do you suggest?
> 
you need a default value for a pair of CPU/NAND flash.

In the present case the values in the log come from
https://community.freescale.com/docs/DOC-1579 which is an i.MX35 and
not a MXS (and is not embedding the same nand flash controller and as
stated on the page : "Values only for iMX35 PDK NAND - K9LBG08U0D-PCB0")
so I'm quite sure the i.MX35 values won't work.

Moreover "-s 512" is wrong vs the webpage content, other values are
not in sync with the patch's log and surprisingly for our i.MX35 boards
I have :
MKUBIFS_ARGS = "-m 2048 -e 129024 -c 2030"
UBINIZE_ARGS = "-m 2048 -p 128KiB -s 512"
which are exactly the values Otavio wants to put in mxs-base.inc (so I
assume he took them from our cpuimx35 board's conf file but copied the
community's log values and both don't match as I assume iMX35 PDK's log
comes from the LTIB generated kernel when we are using mainline and so
a different NAND driver).

Last but not least I have tested some 2k and 4k NAND flashs on i.MX28
with UBI files generated using OE-Core and for example for 2k I have :
MKUBIFS_ARGS = "-m 2048 -e 126976 -c 1900"
UBINIZE_ARGS = "-m 2048 -p 128KiB -s 2048"
which corresponds to the values reported by the (3.10.x) kernel running
on the boards (and other i.MX28 boards embedding NAND are using the same
values for the key parameters of these variables - Denx's m28 for
example as you can see in their manual :
http://www.denx.de/wiki/publish/DULG/DULG-m28evk.pdf )

> Even if we can test it (I think I have access to one NAND to attach on imx28)
> it will be only *one* NAND
> 
True. As i.MX28 EVK comes without a NAND I think it's better to not
allow generating UBI rootfs for this board with random values and let
user who need UBI add the right values vs the flash they are really
using (same for all the other EVK as now Freescale ship empty sockets
by default).

Best regards
Eric


  parent reply	other threads:[~2013-09-18 13:33 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-17 21:30 [meta-fsl-arm PATCH 0/4] Ready to merge patches Otavio Salvador
2013-09-17 21:30 ` [meta-fsl-arm PATCH 1/4] linux-imx (3.0.35): Add defconfig file for i.MX6 Solo SoCs Otavio Salvador
2013-09-17 22:19   ` Fabio Estevam
2013-09-18  2:17     ` Otavio Salvador
2013-09-18  2:27       ` Fabio Estevam
2013-09-18  2:45         ` Otavio Salvador
2013-09-18  2:48           ` Fabio Estevam
2013-09-18  2:52             ` Otavio Salvador
2013-09-17 21:30 ` [meta-fsl-arm PATCH 2/4] linux-imx (3.0.35): Update to 4.1.0 based branch Otavio Salvador
2013-09-17 21:30 ` [meta-fsl-arm PATCH 3/4] linux-fslc: Update to a318c1dd revision Otavio Salvador
2013-09-17 21:30 ` [meta-fsl-arm PATCH 4/4] mxs-base.inc: Add default settings for UBI filesystem generation Otavio Salvador
2013-09-17 22:10   ` Eric Bénard
2013-09-18 12:23     ` Otavio Salvador
2013-09-18 12:32       ` Eric Bénard
2013-09-18 12:58         ` Daiane Angolini
2013-09-18 13:23           ` Otavio Salvador
2013-09-18 13:33           ` Eric Bénard [this message]
2013-09-18 13:43             ` Otavio Salvador
2013-09-18 14:06               ` Eric Bénard
2013-09-18  1:43 ` [meta-fsl-arm PATCH 0/4] Ready to merge patches Daiane Angolini
2013-09-18  2:41   ` Otavio Salvador

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=20130918153332.64536e4a@e6520eb \
    --to=eric@eukrea.com \
    --cc=daiane.list@gmail.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.