<feed xmlns='http://www.w3.org/2005/Atom'>
<title>lwn.git/drivers/mtd/mtdcore.c, branch v2.6.30.1</title>
<subtitle>Linux kernel documentation tree maintained by Jonathan Corbet</subtitle>
<id>http://mirrors.hust.edu.cn/git/lwn.git/atom?h=v2.6.30.1</id>
<link rel='self' href='http://mirrors.hust.edu.cn/git/lwn.git/atom?h=v2.6.30.1'/>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/'/>
<updated>2009-04-19T08:12:49+00:00</updated>
<entry>
<title>mtd: expose subpage size via sysfs</title>
<updated>2009-04-19T08:12:49+00:00</updated>
<author>
<name>Artem Bityutskiy</name>
<email>dedekind@infradead.org</email>
</author>
<published>2009-04-18T09:29:42+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=e7693548950ea5801d5d8b00414aed37033cf972'/>
<id>urn:sha1:e7693548950ea5801d5d8b00414aed37033cf972</id>
<content type='text'>
MTD has got sysfs support in 2.6.30-rc1. But subpage size is not
exposed there - do this.

UBI utilities badly need this parameter. At the moment there is
no way to get subpage size - ioctls do not return it. And we
just got sysfs support, so we can easilly extend it with this
additional parameter.

This can be merged late in the development cycle because:
1. sysfs support has been just added - there are no users for
   it so far, even.
2. UBI utilities really need this parameter, and it is better
   not to delay this.

Signed-off-by: Artem Bityutskiy &lt;Artem.Bityutskiy@nokia.com&gt;
Signed-off-by: David Woodhouse &lt;David.Woodhouse@intel.com&gt;
</content>
</entry>
<entry>
<title>mtd: mtd in mtd_release is unused without CONFIG_MTD_CHAR</title>
<updated>2009-04-19T07:59:17+00:00</updated>
<author>
<name>Denis V. Lunev</name>
<email>den@openvz.org</email>
</author>
<published>2009-04-12T07:14:46+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=2fdb11449ca82f4f1907fce4929df4e0bd267c50'/>
<id>urn:sha1:2fdb11449ca82f4f1907fce4929df4e0bd267c50</id>
<content type='text'>
drivers/mtd/mtdcore.c: In function 'mtd_release':
drivers/mtd/mtdcore.c:51: warning: unused variable 'mtd'

[akpm: make it actually build]
Signed-off-by: Denis V. Lunev &lt;den@openvz.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: David Woodhouse &lt;David.Woodhouse@intel.com&gt;
</content>
</entry>
<entry>
<title>[MTD] sysfs support should not depend on CONFIG_PROC_FS</title>
<updated>2009-04-04T21:52:08+00:00</updated>
<author>
<name>Kevin Cernekee</name>
<email>kpc.mtd@gmail.com</email>
</author>
<published>2009-04-04T18:03:04+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=45b09076149f1360e15919ca7e004e8d3810a0f7'/>
<id>urn:sha1:45b09076149f1360e15919ca7e004e8d3810a0f7</id>
<content type='text'>
Move the driver model init code out of the "#ifdef CONFIG_PROC_FS"
block.

Tested with both values of CONFIG_PROC_FS .  Tested with CONFIG_MTD=m .

Issue was reported here: http://lkml.org/lkml/2009/4/4/107

Signed-off-by: Kevin Cernekee &lt;kpc.mtd@gmail.com&gt;
Signed-off-by: David Woodhouse &lt;David.Woodhouse@intel.com&gt;
</content>
</entry>
<entry>
<title>[MTD] driver model updates (part 2)</title>
<updated>2009-04-04T13:32:39+00:00</updated>
<author>
<name>Kevin Cernekee</name>
<email>kpc.mtd@gmail.com</email>
</author>
<published>2009-04-03T20:00:45+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=694bb7fc19c6b87e106f4c85a2707072e2f111a0'/>
<id>urn:sha1:694bb7fc19c6b87e106f4c85a2707072e2f111a0</id>
<content type='text'>
1) Add more sysfs attributes: flags, size, erasesize, writesize,
   oobsize, numeraseregions, name

2) Move core_initcall() code into init_mtd().  The original approach
   does not work if CONFIG_MTD=m .

3) Add device_unregister() in del_mtd_device() so that devices get
   removed from sysfs as each driver is unloaded.

Signed-off-by: Kevin Cernekee &lt;kpc.mtd@gmail.com&gt;
Signed-off-by: David Woodhouse &lt;David.Woodhouse@intel.com&gt;
</content>
</entry>
<entry>
<title>[MTD] driver model updates</title>
<updated>2009-04-04T13:29:07+00:00</updated>
<author>
<name>David Brownell</name>
<email>dbrownell@users.sourceforge.net</email>
</author>
<published>2009-03-26T07:42:41+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=1f24b5a8ecbb2a3c7080f418974d40e3ffedb221'/>
<id>urn:sha1:1f24b5a8ecbb2a3c7080f418974d40e3ffedb221</id>
<content type='text'>
Update driver model support in the MTD framework, so it fits
better into the current udev-based hotplug framework:

 - Each mtd_info now has a device node.  MTD drivers should set
   the dev.parent field to point to the physical device, before
   setting up partitions or otherwise declaring MTDs.

 - Those device nodes always map to /sys/class/mtdX device nodes,
   which no longer depend on MTD_CHARDEV.

 - Those mtdX sysfs nodes have a "starter set" of attributes;
   it's not yet sufficient to replace /proc/mtd.

 - Enabling MTD_CHARDEV provides /sys/class/mtdXro/ nodes and the
   /sys/class/mtd*/dev attributes (for udev, mdev, etc).

 - Include a MODULE_ALIAS_CHARDEV_MAJOR macro.  It'll work with
   udev creating the /dev/mtd* nodes, not just a static rootfs.

So the sysfs structure is pretty much what you'd expect, except
that readonly chardev nodes are a bit quirky.

Signed-off-by: David Brownell &lt;dbrownell@users.sourceforge.net&gt;
Signed-off-by: David Woodhouse &lt;David.Woodhouse@intel.com&gt;
</content>
</entry>
<entry>
<title>NOMMU: Present backing device capabilities for MTD chardevs</title>
<updated>2009-03-24T09:00:19+00:00</updated>
<author>
<name>David Howells</name>
<email>dhowells@redhat.com</email>
</author>
<published>2009-02-12T10:40:00+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=402d326519c1a4859c527702383f4e60f606ef52'/>
<id>urn:sha1:402d326519c1a4859c527702383f4e60f606ef52</id>
<content type='text'>
Present backing device capabilities for MTD character device files to allow
NOMMU mmap to do direct mapping where possible.

Signed-off-by: David Howells &lt;dhowells@redhat.com&gt;
Tested-by: Bernd Schmidt &lt;bernd.schmidt@analog.com&gt;
Signed-off-by: David Woodhouse &lt;David.Woodhouse@intel.com&gt;
</content>
</entry>
<entry>
<title>[MTD] update internal API to support 64-bit device size</title>
<updated>2008-12-10T13:37:21+00:00</updated>
<author>
<name>Adrian Hunter</name>
<email>ext-adrian.hunter@nokia.com</email>
</author>
<published>2008-12-10T13:37:21+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=69423d99fc182a81f3c5db3eb5c140acc6fc64be'/>
<id>urn:sha1:69423d99fc182a81f3c5db3eb5c140acc6fc64be</id>
<content type='text'>
MTD internal API presently uses 32-bit values to represent
device size.  This patch updates them to 64-bits but leaves
the external API unchanged.  Extending the external API
is a separate issue for several reasons.  First, no one
needs it at the moment.  Secondly, whether the implementation
is done with IOCTLs, sysfs or both is still debated.  Thirdly
external API changes require the internal API to be accepted
first.

Note that although the MTD API will be able to support 64-bit
device sizes, existing drivers do not and are not required
to do so, although NAND base has been updated.

In general, changing from 32-bit to 64-bit values cause little
or no changes to the majority of the code with the following
exceptions:
    	- printk message formats
    	- division and modulus of 64-bit values
    	- NAND base support
	- 32-bit local variables used by mtdpart and mtdconcat
	- naughtily assuming one structure maps to another
	in MEMERASE ioctl

Signed-off-by: Adrian Hunter &lt;ext-adrian.hunter@nokia.com&gt;
Signed-off-by: Artem Bityutskiy &lt;Artem.Bityutskiy@nokia.com&gt;
Signed-off-by: David Woodhouse &lt;David.Woodhouse@intel.com&gt;
</content>
</entry>
<entry>
<title>[MTD] Use list_for_each_entry[_safe] where appropriate.</title>
<updated>2008-06-04T16:53:31+00:00</updated>
<author>
<name>Chris Malley</name>
<email>mail@chrismalley.co.uk</email>
</author>
<published>2008-05-19T19:11:50+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=71a928c0e52cedc43747c64b96a5f74592ab678f'/>
<id>urn:sha1:71a928c0e52cedc43747c64b96a5f74592ab678f</id>
<content type='text'>
Janitorial work to remove temporary pointers and make some functions a bit
more readable.

Signed-off-by: Chris Malley &lt;mail@chrismalley.co.uk&gt;
Reviewed-By: Jörn Engel &lt;joern@logfs.org&gt;
Signed-off-by: David Woodhouse &lt;dwmw2@infradead.org&gt;
</content>
</entry>
<entry>
<title>MTD/JFFS2: remove CVS keywords</title>
<updated>2008-06-04T16:50:17+00:00</updated>
<author>
<name>Adrian Bunk</name>
<email>bunk@kernel.org</email>
</author>
<published>2008-05-19T22:03:52+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=59018b6d2acabb114ab58637e6ab95ba424a89d0'/>
<id>urn:sha1:59018b6d2acabb114ab58637e6ab95ba424a89d0</id>
<content type='text'>
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 &lt;bunk@kernel.org&gt;
Signed-off-by: David Woodhouse &lt;dwmw2@infradead.org&gt;
</content>
</entry>
<entry>
<title>[MTD] use list_for_each_entry() in del_mtd_device()</title>
<updated>2008-06-04T16:34:48+00:00</updated>
<author>
<name>matthias@kaehlcke.net</name>
<email>matthias@kaehlcke.net</email>
</author>
<published>2008-05-31T13:28:10+00:00</published>
<link rel='alternate' type='text/html' href='http://mirrors.hust.edu.cn/git/lwn.git/commit/?id=856613c98c2f864994d5fb33a62b7a468f68ab9b'/>
<id>urn:sha1:856613c98c2f864994d5fb33a62b7a468f68ab9b</id>
<content type='text'>
Signed-off-by: Matthias Kaehlcke &lt;matthias@kaehlcke.net&gt;
Signed-off-by: David Woodhouse &lt;dwmw2@infradead.org&gt;
</content>
</entry>
</feed>
