public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Aleksander Sanochkin <asanochkin@lnxw.com>
Cc: dwmw2@infradead.org, linux-mtd@lists.infradead.org
Subject: Re: JFFS1/MTD bug-fixes
Date: Tue, 4 Dec 2001 23:44:46 +0100	[thread overview]
Message-ID: <20011204234446.B14180@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0112040822310.7813-300000@newbast.lynuxworks.com>; from asanochkin@Lnxw.COM on Tue, Dec 04, 2001 at 08:30:10AM -0800

Hi!

> Yes, I've looked through Jörn Engel's code. Our modifications are less
> significant and are based on other goals in mind.
> 
> Primary goal was to allow for creating Flash partitions that consist of
> non-consequent sectors. For instance, the user may wish to chose sector
> 2 for storing some binary data and use sectors 1,3,4..... as a single
> JFFS partition.
> 
> Another goal was a possibility of flexible (re-)configration of the
> partitions, without having to change any C code. Supported methods are:
> build-time (via a CONFIG_... define), boot-time (via a kernel command
> line), and run-time (via an mtdchar IOCTL command). With all the three
> methods, the user uses a string notation to specify desired layout of the
> partitions. For instance, "0,3-8:1,2:9-25" means three partitions, with
> sectors 0 and 3 to 8 belonging to the first partition, 1 and 2 to the
> second, and 9 to 25 to the third.

We already have partitioning that is independent of the kernels normal
partitioning. Now you send in the equivalent of the logical volume
manager. The mtd code is getting there. :)

What are your reasons to use mtdchar ioctl()s for runtime
repartitioning? This should be pretty independent of the char device,
(caching) block device or whatever the future might still bring. Why
not a /proc interface?

Apart from that the design looks pretty sane. I will look through the
code and try to merge it with mine as soon as my workload drops to an
acceptable value again, most likely around christmas.

Joern

  reply	other threads:[~2001-12-04 22:34 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-04 16:30 JFFS1/MTD bug-fixes Aleksander Sanochkin
2001-12-04 22:44 ` Jörn Engel [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-12-07 13:11 Aleksander Sanochkin
2001-12-07 15:34 ` Jörn Engel
2001-12-07 13:07 Aleksander Sanochkin
2001-12-07 15:40 ` Jörn Engel
2001-12-04 16:36 Aleksander Sanochkin
2001-12-04 22:18 ` Jörn Engel
2001-12-03 15:36 Aleksander Sanochkin
2001-12-03 15:55 ` David Woodhouse
2001-12-04  9:07   ` Jörn Engel
2001-11-30 17:29 Aleksander Sanochkin
2001-12-01 10:47 ` David Woodhouse

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=20011204234446.B14180@wohnheim.fh-wedel.de \
    --to=joern@wohnheim.fh-wedel.de \
    --cc=asanochkin@lnxw.com \
    --cc=dwmw2@infradead.org \
    --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