<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/include/linux/mmc/host.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-06T12:26:55Z</updated>
<entry>
<title>mmc: require explicit support for high-speed</title>
<updated>2007-03-06T12:26:55Z</updated>
<author>
<name>Pierre Ossman</name>
</author>
<published>2007-02-18T11:07:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=cd9277c011a99769fa371521b460ed57f6d280b1'/>
<id>urn:sha1:cd9277c011a99769fa371521b460ed57f6d280b1</id>
<content type='text'>
The new high-speed timings are similar to each other and the old
system, but not identical. And although things "just work" most of
the time, sometimes it does not. So we need to start marking which
hosts are known to fully comply with the new timings.

Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: Allow host drivers to specify max block count</title>
<updated>2007-02-04T19:54:10Z</updated>
<author>
<name>Pierre Ossman</name>
</author>
<published>2006-11-21T16:55:45Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=55db890a838c7b37256241b1fc53d6344aa79cc0'/>
<id>urn:sha1:55db890a838c7b37256241b1fc53d6344aa79cc0</id>
<content type='text'>
Many controllers have an upper limit on the number of blocks that can be
transferred in one request. Allow the host drivers to specify this and make
sure we avoid hitting this limit.

Also change the max_sectors field to avoid confusion. This makes it map
less directly to the block layer limits, but as they didn't apply directly
on MMC cards anyway, this isn't a great loss.

Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: Allow host drivers to specify a max block size</title>
<updated>2007-02-04T19:54:10Z</updated>
<author>
<name>Pierre Ossman</name>
</author>
<published>2006-11-21T16:54:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fe4a3c7a20f14d86022a8132adbf6ddb98e7197c'/>
<id>urn:sha1:fe4a3c7a20f14d86022a8132adbf6ddb98e7197c</id>
<content type='text'>
Most controllers have an upper limit on the block size. Allow the host
drivers to specify this and make sure we avoid hitting this limit.

Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: let host be parent of cards</title>
<updated>2007-02-04T19:54:06Z</updated>
<author>
<name>Pierre Ossman</name>
</author>
<published>2007-01-14T00:41:45Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=11354d03afe9dd0d114e078057158baad4b4eee9'/>
<id>urn:sha1:11354d03afe9dd0d114e078057158baad4b4eee9</id>
<content type='text'>
Change the parent of cards to be a specific host (a class
device), not the physical controller. This is particularly
useful when the hardware has multiple slots, meaning
multiple hosts.

Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>mmc: replace host-&gt;card_busy</title>
<updated>2007-02-04T19:54:06Z</updated>
<author>
<name>Pierre Ossman</name>
</author>
<published>2006-12-26T14:11:23Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f22ee4edf63e7480511112d9965c71e07be3f8b7'/>
<id>urn:sha1:f22ee4edf63e7480511112d9965c71e07be3f8b7</id>
<content type='text'>
As card_busy was only used to indicate if the host was exclusively
claimed and not really used to identify a particular card, replacing
it with just a boolean makes things a lot more easily understandable.

Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
</content>
</entry>
<entry>
<title>Merge branch 'master' of git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6</title>
<updated>2006-12-05T14:37:56Z</updated>
<author>
<name>David Howells</name>
</author>
<published>2006-12-05T14:37:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=4c1ac1b49122b805adfa4efc620592f68dccf5db'/>
<id>urn:sha1:4c1ac1b49122b805adfa4efc620592f68dccf5db</id>
<content type='text'>
Conflicts:

	drivers/infiniband/core/iwcm.c
	drivers/net/chelsio/cxgb2.c
	drivers/net/wireless/bcm43xx/bcm43xx_main.c
	drivers/net/wireless/prism54/islpci_eth.c
	drivers/usb/core/hub.h
	drivers/usb/input/hid-core.c
	net/core/netpoll.c

Fix up merge failures with Linus's head and fix new compilation failures.

Signed-Off-By: David Howells &lt;dhowells@redhat.com&gt;
</content>
</entry>
<entry>
<title>Driver core: convert mmc code to use struct device</title>
<updated>2006-12-01T22:52:00Z</updated>
<author>
<name>Greg Kroah-Hartman</name>
</author>
<published>2006-09-12T15:00:10Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=fcaf71fd51f9cfc504455d3e19ec242e4b2073ed'/>
<id>urn:sha1:fcaf71fd51f9cfc504455d3e19ec242e4b2073ed</id>
<content type='text'>
Converts from using struct "class_device" to "struct device" making
everything show up properly in /sys/devices/ with symlinks from the
/sys/class directory.

Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>WorkStruct: make allyesconfig</title>
<updated>2006-11-22T14:57:56Z</updated>
<author>
<name>David Howells</name>
</author>
<published>2006-11-22T14:57:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c4028958b6ecad064b1a6303a6a5906d4fe48d73'/>
<id>urn:sha1:c4028958b6ecad064b1a6303a6a5906d4fe48d73</id>
<content type='text'>
Fix up for make allyesconfig.

Signed-Off-By: David Howells &lt;dhowells@redhat.com&gt;
</content>
</entry>
<entry>
<title>[MMC] MMC_CAP_BYTEBLOCK flag for non-log2 block sizes capable hosts</title>
<updated>2006-09-24T09:44:09Z</updated>
<author>
<name>Russell King</name>
</author>
<published>2006-09-24T09:44:09Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=42431acbac43eb47c774c29d370f5c59136805bf'/>
<id>urn:sha1:42431acbac43eb47c774c29d370f5c59136805bf</id>
<content type='text'>
Some MMC hosts can only handle log2 block sizes.  Unfortunately,
the MMC password support needs to be able to send non-log2 block
sizes.  Provide a capability so that the MMC password support can
decide whether it should use this support or not.

The unfortunate side effect of this host limitation is that any
MMC card protected by a password which is not a log2 block size
can not be accessed on a host which only allows a log2 block size.

This change just adds the flag.  The MMC password support code
needs updating to use it (if and when it is finally submitted.)

Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
<entry>
<title>[MMC] Add multi block-write capability</title>
<updated>2006-09-16T10:57:49Z</updated>
<author>
<name>Russell King</name>
</author>
<published>2006-08-30T14:14:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=db53f28b3a6d9338cca1b7e917dc063ac99e1871'/>
<id>urn:sha1:db53f28b3a6d9338cca1b7e917dc063ac99e1871</id>
<content type='text'>
Add a capability flag for drivers to set when they can perform multi-
block transfers to cards _and_ correctly report the number of bytes
transferred should an error occur.

The last point is very important - if a driver reports more bytes than
were actually accepted by the card and an error occurs, there is the
possibility for data loss.

Pierre Ossman provided the patch for wbsd and sdhci.

Signed-off-by: Pierre Ossman &lt;drzeus@drzeus.cx&gt;
Signed-off-by: Russell King &lt;rmk+kernel@arm.linux.org.uk&gt;
</content>
</entry>
</feed>
