From: Artem Bityutskiy <dedekind1@gmail.com>
To: Daid <daid303@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: mtd-utils: "flash_erase -j" failes with "unable to get NAND oobinfo" on large flash chips.
Date: Thu, 14 Apr 2011 17:12:58 +0300 [thread overview]
Message-ID: <1302790378.2796.45.camel@localhost> (raw)
In-Reply-To: <BANLkTikgzbGGNg7AXYt89MvM4whvKxXHiQ@mail.gmail.com>
On Thu, 2011-04-14 at 13:43 +0200, Daid wrote:
> On Thu, Apr 14, 2011 at 8:09 AM, Artem Bityutskiy <dedekind1@gmail.com> wrote:
> > On Tue, 2011-04-12 at 11:58 +0200, Daid wrote:
> >> I've made a patch to fix flash_erase with large flash chips.
> >> flash_erase uses MEMGETOOBSEL which no longer works if the ECC area is
> >> larger then 32 bytes. ECCGETLAYOUT is the replacement ioctl.
> >>
> >> This patch is based on the work of Stanley Miao, he made a patch in
> >> June 2010 for flash_eraseall.
> >> http://lists.infradead.org/pipermail/linux-mtd/2010-June/031981.html
> >> I've implemented the backwards compatibility differently, checking
> >> kernel versions doesn't feel correct.
> >
> > Hi Daid, would you please use libmtd instead? If libmtd does not have
> > some functionality you need - just add it there.
> >
> > The thing is that we are trying to unify this stuff a little.
> >
> > --
> > Best Regards,
> > Artem Bityutskiy (Артём Битюцкий)
> >
> >
>
> Hi Artem, libmtd didn't have the functionality I needed. I've made a new patch
> with the functionality build into libmtd.
>
> I've added the extra information to struct mtd_dev_info, however, the
> info needed is
> only available with ioctls, so even with the sysfs interface it needs
> to open /dev/mtdXX.
> When you use mtd_get_dev_info, it reads all the information, which simple for
> the user of libmtd, but sort of mixes legacy and the sysfs interface.
Could you please split this on 2 patches:
1. Add new functionality to libmtd
2. Start using it in mkfs.jffs2.
This way it is easier to review, and if you screw up mkfs.jffs2 we can
always revert patch #2 without reverting libmtd.
> +/**
> + * mtd_get_oob_info - fill the mtd_dev_info structure with information
> + * about the OOB data.
> + */
> +static int mtd_get_oob_info(struct mtd_dev_info *mtd)
> +{
> + int i, fd;
> + char node[sizeof(MTD_DEV_PATT) + 20];
> +
> + sprintf(node, MTD_DEV_PATT, mtd->mtd_num);
> + fd = open(node, O_RDWR);
> + if (fd == -1)
> + return sys_errmsg("cannot open \"%s\"", node);
> +
> + if (mtd->type == MTD_NANDFLASH) {
> + /* get ECC/OOB information for NAND flash */
> +#if defined(ECCGETLAYOUT)
Where does this define come from?
> + struct nand_ecclayout ecclayout;
> + memset(&ecclayout, 0, sizeof(ecclayout));
> + if (ioctl(fd, ECCGETLAYOUT, &ecclayout) == 0) {
> + mtd->eccbytes = ecclayout.eccbytes;
> + for(i=0; i<64; i++) {
> + mtd->eccpos[i] = ecclayout.eccpos[i];
> + }
> + mtd->oob_available = ecclayout.oobavail;
> + for (i=0; i<MTD_NAND_MAX_OOBFREE_ENTRIES; i++) {
> + mtd->oob_free[i].offset = ecclayout.oobfree[i].offset;
> + mtd->oob_free[i].length = ecclayout.oobfree[i].length;
> + }
> + } else {
> +#endif/*defined(ECCGETLAYOUT)*/
> + /* new ECC interface failed or not available, fall back to old OOB
> interface, which does not support large flash */
> + struct nand_oobinfo oobinfo;
> + if (ioctl(fd, MEMGETOOBSEL, &oobinfo) == 0)
The legacy piece of code should be handled in libmtd_legacy.c There are
already some things you can re-use.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2011-04-14 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-12 9:58 mtd-utils: "flash_erase -j" failes with "unable to get NAND oobinfo" on large flash chips Daid
2011-04-14 6:09 ` Artem Bityutskiy
2011-04-14 11:43 ` Daid
2011-04-14 14:12 ` Artem Bityutskiy [this message]
[not found] ` <BANLkTinf1qWFKz19Q2YQKg4o2wT6m-nqsA@mail.gmail.com>
[not found] ` <BANLkTinZwawiu=-M2qm2PDhZ_yhjM8fS5Q@mail.gmail.com>
2011-04-21 12:55 ` Fwd: " Artem Bityutskiy
2011-04-21 12:58 ` Artem Bityutskiy
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=1302790378.2796.45.camel@localhost \
--to=dedekind1@gmail.com \
--cc=daid303@gmail.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;
as well as URLs for NNTP newsgroup(s).