<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/include/linux/mtd/mtd.h, branch linux-2.6.21.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.21.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.21.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2007-03-08T09:17:43Z</updated>
<entry>
<title>[MTD] [NAND] make oobavail public</title>
<updated>2007-03-08T09:17:43Z</updated>
<author>
<name>Vitaly Wool</name>
</author>
<published>2007-03-06T13:56:34Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1f92267c51a514f35ad5b0fd46cb099c0980b679'/>
<id>urn:sha1:1f92267c51a514f35ad5b0fd46cb099c0980b679</id>
<content type='text'>
During the MTD rework the oobavail parameter of mtd_info structure has become
private. This is not quite correct in terms of integrity and logic. If we have
means to write to OOB area, then we'd like to know upfront how many bytes out
of OOB are spare per page to be able to adapt to specific cases.
The patch inlined adds the public oobavail parameter.

Signed-off-by: Vitaly Wool &lt;vwool@ru.mvista.com&gt;
Signed-off-by: David Woodhouse &lt;dwmw2@infradead.org&gt;
</content>
</entry>
<entry>
<title>[MTD] Clarify OOB-operation interface comments</title>
<updated>2007-02-09T15:27:50Z</updated>
<author>
<name>Artem Bityutskiy</name>
</author>
<published>2007-01-31T09:43:13Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=73a4421c5a0aa77b996891e7616b396c360b3ed8'/>
<id>urn:sha1:73a4421c5a0aa77b996891e7616b396c360b3ed8</id>
<content type='text'>
Add more comment to OOB I/O interface. Read/write are not
symmetric which is confusing and should be documented.

Signed-off-by: Artem Bityutskiy &lt;Artem.Bityutskiy@nokia.com&gt;
Signed-off-by: David Woodhouse &lt;dwmw2@infradead.org&gt;
</content>
</entry>
<entry>
<title>[MTD] remove unused ecctype,eccsize fields from struct mtd_info</title>
<updated>2007-02-09T15:27:12Z</updated>
<author>
<name>Artem Bityutskiy</name>
</author>
<published>2007-01-30T08:50:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=64f60710568db5cec1a76c1d1e261b239f9ef809'/>
<id>urn:sha1:64f60710568db5cec1a76c1d1e261b239f9ef809</id>
<content type='text'>
Remove unused and broken mtd-&gt;ecctype and mtd-&gt;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 &lt;Artem.Bityutskiy@nokia.com&gt;
Signed-off-by: David Woodhouse &lt;dwmw2@infradead.org&gt;
</content>
</entry>
<entry>
<title>[MTD] [NOR] Intel: remove ugly PROGREGION macros</title>
<updated>2007-02-09T15:26:37Z</updated>
<author>
<name>Artem Bityutskiy</name>
</author>
<published>2007-01-30T08:45:55Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d416085572eb6a44fd2cf29fd7aed83ffc95fd88'/>
<id>urn:sha1:d416085572eb6a44fd2cf29fd7aed83ffc95fd88</id>
<content type='text'>
Remove ugly and weird MTD_PROGREGION_CTRLMODE_VALID() and
MTD_PROGREGION_CTRLMODE_INVALID() macros. There is only one
user of them and they are used locally just for printing.

Anyway, this patch is a preparation for removing mtd-&gt;ecctype
and mtd-&gt;eccsize, but these macros use them. Fix this.

Signed-off-by: Artem Bityutskiy &lt;Artem.Bityutskiy@nokia.com&gt;
Signed-off-by: David Woodhouse &lt;dwmw2@infradead.org&gt;
</content>
</entry>
<entry>
<title>[MTD] add get and put methods</title>
<updated>2006-11-29T15:04:53Z</updated>
<author>
<name>Artem Bityutskiy</name>
</author>
<published>2006-10-11T11:52:45Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9fe912cea32aec18f860c95e8574410b5892481b'/>
<id>urn:sha1:9fe912cea32aec18f860c95e8574410b5892481b</id>
<content type='text'>
This patch adds get_device() and put_device() methods to the MTD description
structure (struct mtd_info). These methods are called by MTD whenever the MTD
device is get or put. They are needed when the underlying driver is something
smarter then just flash chip driver, for example UBI.

Signed-off-by: Artem Bityutskiy &lt;dedekind@infradead.org&gt;
</content>
</entry>
<entry>
<title>[MTD] add get_mtd_device_nm() function</title>
<updated>2006-11-29T15:04:31Z</updated>
<author>
<name>Artem Bityutskiy</name>
</author>
<published>2006-10-11T11:52:44Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7799308f34d3c3371a319559687c78c0f2506fcf'/>
<id>urn:sha1:7799308f34d3c3371a319559687c78c0f2506fcf</id>
<content type='text'>
This patch adds one more function to the MTD interface to make it possible to
open MTD devices by their names, not only numbers. This is very handy in many
situations. Also, MTD device number depend on load order and may vary, while
names are fixed.

Signed-off-by: Artem Bityutskiy &lt;dedekind@infradead.org&gt;
</content>
</entry>
<entry>
<title>[MTD] NAND: add subpage write support</title>
<updated>2006-11-29T15:03:52Z</updated>
<author>
<name>Thomas Gleixner</name>
</author>
<published>2006-09-28T13:38:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=29072b96078ffde36f03d51e6b5d0cff1ba8c7df'/>
<id>urn:sha1:29072b96078ffde36f03d51e6b5d0cff1ba8c7df</id>
<content type='text'>
Many SLC NANDs support up to 4 writes at one NAND page. Add support
of this feature.

Signed-off-by: Artem Bityutskiy &lt;dedekind@infradead.org&gt;
</content>
</entry>
<entry>
<title>[MTD] increase MAX_MTD_DEVICES</title>
<updated>2006-11-29T14:57:34Z</updated>
<author>
<name>Artem Bityutskiy</name>
</author>
<published>2006-11-13T11:47:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c0fe10aef354912c38c43991dd38c16f1828cfe3'/>
<id>urn:sha1:c0fe10aef354912c38c43991dd38c16f1828cfe3</id>
<content type='text'>
Signed-off-by: Artem Bityutskiy &lt;dedekind@infradead.org&gt;
</content>
</entry>
<entry>
<title>[MTD] [NAND] remove len/ooblen confusion.</title>
<updated>2006-11-28T22:39:03Z</updated>
<author>
<name>Vitaly Wool</name>
</author>
<published>2006-11-03T15:20:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=7014568bad55c20b7ee4f439d78c9e875912d51f'/>
<id>urn:sha1:7014568bad55c20b7ee4f439d78c9e875912d51f</id>
<content type='text'>
As was discussed between Ricard Wanderlöf, David Woodhouse, Artem 
Bityutskiy and me, the current API for reading/writing OOB is confusing. 

The thing that introduces confusion is the need to specify ops.len 
together with ops.ooblen for reads/writes that concern only OOB not data 
area. So, ops.len is overloaded: when ops.datbuf != NULL it serves to 
specify the length of the data read, and when ops.datbuf == NULL, it 
serves to specify the full OOB read length.

The patch inlined below is the slightly updated version of the previous 
patch serving the same purpose, but with the new Artem's comments taken 
into account.

Artem, BTW, thanks a lot for your valuable input!

Signed-off-by: Vitaly Wool &lt;vwool@ru.mvista.com&gt;
Signed-off-by: David Woodhouse &lt;dwmw2@infradead.org&gt;
</content>
</entry>
<entry>
<title>MTD: kernel-doc fixes + additions</title>
<updated>2006-06-29T07:55:41Z</updated>
<author>
<name>Randy Dunlap</name>
</author>
<published>2006-06-29T04:48:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ea9b6dcc152f09c207117ab121d4fa03d2db282a'/>
<id>urn:sha1:ea9b6dcc152f09c207117ab121d4fa03d2db282a</id>
<content type='text'>
Fix some kernel-doc typos/spellos.
Use kernel-doc syntax in places where it was almost used.
Correct/add struct, struct field, and function param names where needed.

Signed-off-by: Randy Dunlap &lt;rdunlap@xenotime.net&gt;
Signed-off-by: David Woodhouse &lt;dwmw2@infradead.org&gt;
</content>
</entry>
</feed>
