From: "Eric Bénard" <eric@eukrea.com>
To: Frans Meulenbroeks <fransmeulenbroeks@gmail.com>
Cc: Patches, oe-core layer <openembedded-core@lists.openembedded.org>
Subject: Re: split mtd-utils
Date: Fri, 11 Jan 2013 09:48:25 +0100 [thread overview]
Message-ID: <20130111094825.13615ca8@e6520eb> (raw)
In-Reply-To: <CACW_hTaR+s1OyZFCseA1Nx0kxwi_W0NHzpBw7r-8jinKeBA21w@mail.gmail.com>
Hi Frans,
Le Fri, 11 Jan 2013 09:40:43 +0100,
Frans Meulenbroeks <fransmeulenbroeks@gmail.com> a écrit :
> Along the lines of the oe classic patch I propose to split as follows:
>
>
> mtd-utils-jffs2 package containing
> jffs2dump
> jffs2reader
> mkfs.jffs2
>
> mtd-utils-ubifs package containing:
> mkfs.ubifs
> ubiattach
> ubicrc32
> ubidetach
> ubiformat
> ubimkvol
> ubinfo
> ubinize
> ubirename
> ubirmvol
> ubirsvol
> ubiupdatevol
>
> mtd-utils package containing:
> docfdisk
> doc_loadbios
> flashcp
> flash_erase
> flash_eraseall
> flash_lock
> flash_otp_dump
> flash_otp_info
> flash_unlock
> ftl_check
> ftl_format
> mtd_debug
> mtdinfo
> nanddump
> nandtest
> nandwrite
> nftldump
> nftl_format
> recv_image
> rfddump
> rfdformat
> serve_image
> sumtool
>
IIRC sumtol is used for jffs2 images (to create the erase block
summary) so that may better fit into mtd-utils-jffs2
Also, nftl* rfd* doc* ftl* serve_image may go into a separate packate
(mtd-utils-misc ?) as I believe those tools are not very usefull in
most configurations using mtd with nowadays's flashs.
Eric
next prev parent reply other threads:[~2013-01-11 9:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 16:12 split mtd-utils Frans Meulenbroeks
2013-01-09 17:17 ` Richard Purdie
2013-01-10 14:56 ` Andrea Adami
2013-01-10 15:06 ` Frans Meulenbroeks
2013-01-11 8:40 ` Frans Meulenbroeks
2013-01-11 8:48 ` Eric Bénard [this message]
2013-01-11 8:57 ` Frans Meulenbroeks
2013-01-21 11:21 ` Frans Meulenbroeks
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=20130111094825.13615ca8@e6520eb \
--to=eric@eukrea.com \
--cc=fransmeulenbroeks@gmail.com \
--cc=openembedded-core@lists.openembedded.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 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.