14 Apr, 2011
4 commits
-
Fix checkpatch.pl errors and warnings:
* space before tab
* line over 80 characters
* include linux/ioctl.h instead of asm/ioctl.hSigned-off-by: Artem Bityutskiy
-
There was an attempt to standartize various "__attribute__" and
other macros in order to have potentially portable and more
consistent code, see commit 82ddcb040570411fc2d421d96b3e69711c670328.Note, that commit refers Rober Love's blog post, but the URL
is broken, the valid URL is:
http://blog.rlove.org/2005/10/with-little-help-from-your-compiler.htmlMoreover, nowadays checkpatch.pl warns about using
__attribute__((packed)):"WARNING: __packed is preferred over __attribute__((packed))"
It is not a big deal for UBI to use __packed, so let's do it.
Signed-off-by: Artem Bityutskiy
-
Cleanup and improve commentaries around the "set volume properties" ioctl,
make a simple indentation fix as well.Signed-off-by: Artem Bityutskiy
-
Rename the ioctl which sets volume properties from 'UBI_IOCSETPROP' to
'UBI_IOCSETVOLPROP' to reflect the fact that this ioctl is about volume
properties, not device properties. This is also consistent with the
other volume ioctl name - 'UBI_IOCVOLUP'.The main motivation for the re-name, however, is that we are going
to introduce the per-UBI device "set properties" ioctl, so we need
good and logical naming.At the same time, re-name the "set volume properties request" data
structure from 'struct ubi_set_prop_req' to
'struct ubi_set_vol_prop_req'.And re-name 'UBI_PROP_DIRECT_WRITE' to 'UBI_VOL_PROP_DIRECT_WRITE'.
Signed-off-by: Artem Bityutskiy
25 Oct, 2010
3 commits
-
MLC NAND Flash has a different cell structure and differs in
functioning than the SLC NAND Flash. Hence we are considering it as
a different Flash type.Signed-off-by: Rohit H.S
Signed-off-by: Raghav Gupta
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse -
There were some improvements and additions necessary in the
comments explaining of the expansion of nand_ecclayout, the
introduction of nand_ecclayout_user, and the deprecation of the
ioctl ECCGETLAYOUT.Also, I found a better placement for the macro MTD_MAX_ECCPOS_ENTRIES;
next to the definition of MTD_MAX_OOBFREE_ENTRIES in mtd-abi.h. The macro
is really only important for the ioctl code (found in drivers/mtd/mtdchar.c)
but since there are small edits being made to the user-space header, I
figured this is a better location.Signed-off-by: Brian Norris
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse -
struct nand_ecclayout is too small for many new chips; OOB regions can be as
large as 448 bytes and may increase more in the future. Thus, copying that
struct to user-space with the ECCGETLAYOUT ioctl is not a good idea; the ioctl
would have to be updated every time there's a change to the current largest
size.Instead, the old nand_ecclayout is renamed to nand_ecclayout_user and a
new struct nand_ecclayout is created that can accomodate larger sizes and
expand without affecting the user-space. struct nand_ecclayout can still
be used in board drivers without modification -- at least for now.A new function is provided to convert from the new to the old in order to
allow the deprecated ioctl to continue to work with truncated data. Perhaps
the ioctl, the conversion process, and the struct nand_ecclayout_user can be
removed altogether in the future.Note: There are comments in nand/davinci_nand.c::nand_davinci_probe()
regarding this issue; this driver (and maybe others) can be updated to
account for extra space. All kernel drivers can use the expanded
nand_ecclayout as a drop-in replacement and ignore its benefits.Signed-off-by: Brian Norris
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse
09 Aug, 2010
1 commit
-
Signed-off-by: David Woodhouse
02 Aug, 2010
1 commit
-
This patchs adds a way for user space programs to find out whether a
flash sector is locked. An optional driver method in the mtd_info struct
provides the information.Signed-off-by: Richard Cochran
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse
06 Jun, 2009
1 commit
-
This file does not define any kernel-userspace API, all
it does it defines few helpers for userspace. Instead,
userspace should have a private copy of this file.The main (if not the only) user is the mtd-utils package, but
it already has a private copy of this file.This patch also removes references to 'jffs2-user.h' from
'Kbuild' and MAINTAINERS' files.Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse
29 May, 2009
2 commits
-
Signed-off-by: Kevin Cernekee
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse -
New MEMERASE/MEMREADOOB/MEMWRITEOOB ioctls are needed in order to support
64-bit offsets into large NAND flash devices.Signed-off-by: Kevin Cernekee
Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse
27 Mar, 2009
2 commits
-
The MTD headers traditionally use stdint types rather than
the kernel integer types. This converts them to do the
same as all the others.Cc: David Woodhouse
Signed-off-by: Arnd Bergmann
Signed-off-by: H. Peter Anvin
Signed-off-by: Ingo Molnar -
A number of standard posix types are used in exported headers, which
is not allowed if __STRICT_KERNEL_NAMES is defined. In order to
get rid of the non-__STRICT_KERNEL_NAMES part and to make sane headers
the default, we have to change them all to safe types.There are also still some leftovers in reiserfs_fs.h, elfcore.h
and coda.h, but these files have not compiled in user space for
a long time.This leaves out the various integer types ({u_,u,}int{8,16,32,64}_t),
which we take care of separately.Signed-off-by: Arnd Bergmann
Acked-by: Mauro Carvalho Chehab
Cc: David Airlie
Cc: Arnaldo Carvalho de Melo
Cc: YOSHIFUJI Hideaki
Cc: netdev@vger.kernel.org
Cc: linux-ppp@vger.kernel.org
Cc: Jaroslav Kysela
Cc: Takashi Iwai
Cc: David Woodhouse
Signed-off-by: H. Peter Anvin
Signed-off-by: Ingo Molnar
31 Jan, 2009
1 commit
-
fix the following 'make headers_check' warning:
usr/include/mtd/inftl-user.h:61: found __[us]{8,16,32,64} type without #include
Signed-off-by: Jaswinder Singh Rajput
27 Jan, 2009
1 commit
-
Introduce a new ioctl UBI_IOCSETPROP to set properties
on a volume. Also add the first property:
UBI_PROP_DIRECT_WRITE, this property is used to set the
ability to use direct writes in userspaceSigned-off-by: Sidney Amani
Signed-off-by: Corentin Chary
Signed-off-by: Artem Bityutskiy
18 Jan, 2009
4 commits
-
Signed-off-by: Artem Bityutskiy
-
This patch adds ioctl to check if an LEB is mapped or not (as a
debugging option so far).[Re-named ioctl to make it look the same as the other one and made
some minor stylistic changes. Artem Bityutskiy.]Signed-off-by: Corentin Chary
Signed-off-by: Artem Bityutskiy -
This patch adds ioctl for the LEB unmap operation (as a debugging
option so far).[Re-named ioctl to make it look the same as the other one and made
some minor stylistic changes. Artem Bityutskiy.]Signed-off-by: Corentin Chary
Signed-off-by: Artem Bityutskiy -
This patch adds ioctl for the LEB map operation (as a debugging
option so far).[Re-named ioctl to make it look the same as the other one and made
some minor stylistic changes. Artem Bityutskiy.]Signed-off-by: Corentin Chary
Signed-off-by: Artem Bityutskiy
06 Jan, 2009
1 commit
-
- (better, more, bigger ...) then -> (...) than
Signed-off-by: Frederik Schwarzer
Signed-off-by: Jiri Kosina
25 Jul, 2008
1 commit
24 Jul, 2008
2 commits
-
Just out or curiousity ran checkpatch.pl for whole UBI,
and discovered there are quite a few of stylistic issues.
Fix them.Signed-off-by: Artem Bityutskiy
-
Quite useful ioctl which allows to make atomic system upgrades.
The idea belongs to Richard TitmussSigned-off-by: Artem Bityutskiy
05 Jun, 2008
1 commit
-
Once upon a time, the MTD repository was using CVS.
This patch therefore removes all usages of the no longer updated CVS
keywords from the MTD code.This also includes code that printed them to the user.
Signed-off-by: Adrian Bunk
Signed-off-by: David Woodhouse
17 Apr, 2008
1 commit
-
The new trend in linux is not to store headers which define
on-media format in the include/ directory, but instead, store
them locally. This is because these headers "do not define any
kerneluserspace interface".Do so for UBI as well.
Signed-off-by: Artem Bityutskiy
03 Feb, 2008
2 commits
-
Patch for unlocking all Intel flash that has instant locking on power up.
The patch has been tested on Intel M18, P30 and J3D Strata Flash.
1. The automatic unlocking can be disabled for a particular partition
in the map or the command line.
a. For the bit mask in the map it should look like:
.mask_flags = MTD_POWERUP_LOCK,
b. For the command line parsing it should look like:
mtdparts=0x80000(bootloader)lk
2. This will only unlock parts with instant individual block locking.
Intel parts with legacy unlocking will not be unlocked.Signed-off-by: Justin Treon
Signed-off-by: Jared Hulbert
Acked-by: Nicolas Pitre
Signed-off-by: David Woodhouse
25 Jan, 2008
3 commits
-
We have to be able to change individual LEBs for utilities like
ubifsck, ubifstune. For example, ubifsck has to be able to fix
errors on the media, ubifstune has to be able to change the
the superblock, hence this ioctl.Signed-off-by: Artem Bityutskiy
-
Add more information about layout volume to make userspace tools
use the macros instead of constants. Also rename UBI_LAYOUT_VOL_ID
to make it consistent with other macros.Signed-off-by: Artem Bityutskiy
-
The problem: NAND flashes have different amount of initial bad physical
eraseblocks (marked as bad by the manufacturer). For example, for 256MiB
Samsung OneNAND flash there might be from 0 to 40 bad initial eraseblocks,
which is about 2%. When UBI is used as the base system, one needs to know
the exact amount of good physical eraseblocks, because this number is
needed to create the UBI image which is put to the devices during
production. But this number is not know, which forces us to use the
minimum number of good physical eraseblocks. And UBI additionally
reserves some percentage of physical eraseblocks for bad block handling
(default is 1%), so we have 1-3% of PEBs reserved at the end, depending
on the amount of initial bad PEBs. But it is desired to always have
1% (or more, depending on the configuration).Solution: this patch adds an "auto-resize" flag to the volume table.
The volume which has the "auto-resize" flag will automatically be re-sized
(enlarged) on the first UBI initialization. UBI clears the flag when
the volume is re-sized. Only one volume may have the "auto-resize" flag.So, the production UBI image may have one volume with "auto-resize"
flag set, and its size is automatically adjusted on the first boot
of the device.Signed-off-by: Artem Bityutskiy
27 Dec, 2007
1 commit
-
Signed-off-by: Artem Bityutskiy
18 Jul, 2007
1 commit
-
Kill UBI's homegrown endianess handling and replace it with
the standard kernel endianess handling.Signed-off-by: Christoph Hellwig
Signed-off-by: Artem Bityutskiy
27 Apr, 2007
1 commit
-
UBI (Latin: "where?") manages multiple logical volumes on a single
flash device, specifically supporting NAND flash devices. UBI provides
a flexible partitioning concept which still allows for wear-levelling
across the whole flash device.In a sense, UBI may be compared to the Logical Volume Manager
(LVM). Whereas LVM maps logical sector numbers to physical HDD sector
numbers, UBI maps logical eraseblocks to physical eraseblocks.More information may be found at
http://www.linux-mtd.infradead.org/doc/ubi.htmlPartitioning/Re-partitioning
An UBI volume occupies a certain number of erase blocks. This is
limited by a configured maximum volume size, which could also be
viewed as the partition size. Each individual UBI volume's size can
be changed independently of the other UBI volumes, provided that the
sum of all volume sizes doesn't exceed a certain limit.UBI supports dynamic volumes and static volumes. Static volumes are
read-only and their contents are protected by CRC check sums.Bad eraseblocks handling
UBI transparently handles bad eraseblocks. When a physical
eraseblock becomes bad, it is substituted by a good physical
eraseblock, and the user does not even notice this.Scrubbing
On a NAND flash bit flips can occur on any write operation,
sometimes also on read. If bit flips persist on the device, at first
they can still be corrected by ECC, but once they accumulate,
correction will become impossible. Thus it is best to actively scrub
the affected eraseblock, by first copying it to a free eraseblock
and then erasing the original. The UBI layer performs this type of
scrubbing under the covers, transparently to the UBI volume users.Erase Counts
UBI maintains an erase count header per eraseblock. This frees
higher-level layers (like file systems) from doing this and allows
for centralized erase count management instead. The erase counts are
used by the wear-levelling algorithm in the UBI layer. The algorithm
itself is exchangeable.Booting from NAND
For booting directly from NAND flash the hardware must at least be
capable of fetching and executing a small portion of the NAND
flash. Some NAND flash controllers have this kind of support. They
usually limit the window to a few kilobytes in erase block 0. This
"initial program loader" (IPL) must then contain sufficient logic to
load and execute the next boot phase.Due to bad eraseblocks, which may be randomly scattered over the
flash device, it is problematic to store the "secondary program
loader" (SPL) statically. Also, due to bit-flips it may become
corrupted over time. UBI allows to solve this problem gracefully by
storing the SPL in a small static UBI volume.UBI volumes vs. static partitions
UBI volumes are still very similar to static MTD partitions:
* both consist of eraseblocks (logical eraseblocks in case of UBI
volumes, and physical eraseblocks in case of static partitions;
* both support three basic operations - read, write, erase.But UBI volumes have the following advantages over traditional
static MTD partitions:* there are no eraseblock wear-leveling constraints in case of UBI
volumes, so the user should not care about this;
* there are no bit-flips and bad eraseblocks in case of UBI volumes.So, UBI volumes may be considered as flash devices with relaxed
restrictions.Where can it be found?
Documentation, kernel code and applications can be found in the MTD
gits.What are the applications for?
The applications help to create binary flash images for two purposes: pfi
files (partial flash images) for in-system update of UBI volumes, and plain
binary images, with or without OOB data in case of NAND, for a manufacturing
step. Furthermore some tools are/and will be created that allow flash content
analysis after a system has crashed..Who did UBI?
The original ideas, where UBI is based on, were developed by Andreas
Arnez, Frank Haverkamp and Thomas Gleixner. Josh W. Boyer and some others
were involved too. The implementation of the kernel layer was done by Artem
B. Bityutskiy. The user-space applications and tools were written by Oliver
Lohmann with contributions from Frank Haverkamp, Andreas Arnez, and Artem.
Joern Engel contributed a patch which modifies JFFS2 so that it can be run on
a UBI volume. Thomas Gleixner did modifications to the NAND layer. Alexander
Schmidt made some testing work as well as core functionality improvements.Signed-off-by: Artem B. Bityutskiy
Signed-off-by: Frank Haverkamp
09 Feb, 2007
1 commit
-
Remove unused and broken mtd->ecctype and mtd->eccsize fields
from struct mtd_info. Do not remove them from userspace API
data structures (don't want to breake userspace) but mark them
as obsolete by a comment. Any userspace program which uses them
should be half-broken anyway, so this is more about saving
data structure size.Signed-off-by: Artem Bityutskiy
Signed-off-by: David Woodhouse
02 Oct, 2006
1 commit
-
Manually resolve conflict in include/mtd/Kbuild
Signed-off-by: David Woodhouse
26 Sep, 2006
1 commit
-
Now that we have headers_install, we don't need this crap.
Signed-off-by: David Woodhouse
23 Sep, 2006
1 commit
-
* git://git.infradead.org/~dwmw2/hdroneline:
[HEADERS] One line per header in Kbuild files to reduce conflictsManual (trivial) conflict resolution in include/asm-s390/Kbuild
22 Sep, 2006
1 commit
-
Introduce the MTD_STUPID_LOCK flag which indicates that the flash chip is
always locked after power-up, so all sectors need to be unlocked before it
is usable.If this flag is set, and the chip provides an unlock() operation,
mtd_add_device will unlock the whole MTD device if it's writeable. This
means that non-writeable partitions will stay locked.Set MTD_STUPID_LOCK in fixup_use_atmel_lock() so that these chips will work
as expected.Signed-off-by: Håvard Skinnemoen
Signed-off-by: Andrew Morton
Signed-off-by: David Woodhouse
19 Sep, 2006
1 commit
-
Signed-off-by: David Woodhouse