<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers, branch v2.6.27.36</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers?h=v2.6.27.36</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers?h=v2.6.27.36'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2009-10-05T15:11:45Z</updated>
<entry>
<title>Fix incorrect stable backport to bas_gigaset</title>
<updated>2009-10-05T15:11:45Z</updated>
<author>
<name>Tilman Schmidt</name>
<email>tilman@imap.cc</email>
</author>
<published>2009-08-25T15:35:56Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=18494baca2fd31e6203be2ae9c572c86667da1b1'/>
<id>urn:sha1:18494baca2fd31e6203be2ae9c572c86667da1b1</id>
<content type='text'>
bas_gigaset: correctly allocate USB interrupt transfer buffer

[ Upstream commit 170ebf85160dd128e1c4206cc197cce7d1424705 ]

This incorrect backport to 2.6.28.10 placed some code into the probe function
which used a pointer before it was initialized. Moving this to the correct
place (as it is in upstream).

Signed-off-by: Stefan Bader &lt;stefan.bader@canonical.com&gt;
Acked-by: Tim Gardner &lt;tim.gardner@canonical.com&gt;
Acked-by: Steve Conklin &lt;steve.conklin@canonical.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>pcnet_cs: Fix misuse of the equality operator.</title>
<updated>2009-10-05T15:11:44Z</updated>
<author>
<name>Cord Walter</name>
<email>qord@cwalter.net</email>
</author>
<published>2009-02-03T23:14:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=54cd9c84498433f1800ad47445428d3e33d75188'/>
<id>urn:sha1:54cd9c84498433f1800ad47445428d3e33d75188</id>
<content type='text'>
commit a9d3a146923d374b945aa388dc884df69564a818 upstream.

Signed-off-by: Cord Walter &lt;qord@cwalter.net&gt;
Signed-off-by: Komuro &lt;komurojun-mbn@nifty.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Cc: Christoph Biedl &lt;linux-kernel.bfrz@manchmal.in-ulm.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>enc28j60: fix RX buffer overflow</title>
<updated>2009-10-05T15:11:43Z</updated>
<author>
<name>Baruch Siach</name>
<email>baruch@tkos.co.il</email>
</author>
<published>2009-01-05T00:23:01Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=52ccbcd1bcbed712bb586c3c17164fe326e89f1a'/>
<id>urn:sha1:52ccbcd1bcbed712bb586c3c17164fe326e89f1a</id>
<content type='text'>
commit 22692018b93f0782cda5a843cecfffda1854eb8d upstream.

The enc28j60 driver doesn't check whether the length of the packet as reported
by the hardware fits into the preallocated buffer. When stressed, the hardware
may report insanely large packets even tough the "Receive OK" bit is set. Fix
this.

Signed-off-by: Baruch Siach &lt;baruch@tkos.co.il&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>p54usb: add Zcomax XG-705A usbid</title>
<updated>2009-10-05T15:11:41Z</updated>
<author>
<name>Christian Lamparter</name>
<email>chunkeey@googlemail.com</email>
</author>
<published>2009-09-14T21:08:43Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e6edca0908edee83e00c90a904c5ecaf9d0e5404'/>
<id>urn:sha1:e6edca0908edee83e00c90a904c5ecaf9d0e5404</id>
<content type='text'>
commit f7f71173ea69d4dabf166533beffa9294090b7ef upstream.

This patch adds a new usbid for Zcomax XG-705A to the device table.

Reported-by: Jari Jaakola &lt;jari.jaakola@gmail.com&gt;
Signed-off-by: Christian Lamparter &lt;chunkeey@googlemail.com&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>libata: fix off-by-one error in ata_tf_read_block()</title>
<updated>2009-09-24T15:47:35Z</updated>
<author>
<name>Tejun Heo</name>
<email>htejun@gmail.com</email>
</author>
<published>2009-08-16T12:21:21Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8dee92cc72924326b360e06f08b05d79e9833c3c'/>
<id>urn:sha1:8dee92cc72924326b360e06f08b05d79e9833c3c</id>
<content type='text'>
commit ac8672ea922bde59acf50eaa1eaa1640a6395fd2 upstream.

ata_tf_read_block() has off-by-one error when converting CHS address
to LBA.  The bug isn't very visible because ata_tf_read_block() is
used only when generating sense data for a failed RW command and CHS
addressing isn't used too often these days.

This problem was spotted by Atsushi Nemoto.

Signed-off-by: Tejun Heo &lt;tj@kernel.org&gt;
Reported-by: Atsushi Nemoto &lt;anemo@mba.ocn.ne.jp&gt;
Signed-off-by: Jeff Garzik &lt;jgarzik@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>TPM: Fixup boot probe timeout for tpm_tis driver</title>
<updated>2009-09-24T15:47:30Z</updated>
<author>
<name>Jason Gunthorpe</name>
<email>jgunthorpe@obsidianresearch.com</email>
</author>
<published>2009-09-09T23:22:18Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1c27e4044eabce1fd6aa27d7178c7a07811d6f16'/>
<id>urn:sha1:1c27e4044eabce1fd6aa27d7178c7a07811d6f16</id>
<content type='text'>
commit ec57935837a78f9661125b08a5d08b697568e040 upstream.

When probing the device in tpm_tis_init the call request_locality
uses timeout_a, which wasn't being initalized until after
request_locality. This results in request_locality falsely timing
out if the chip is still starting. Move the initialization to before
request_locality.

This probably only matters for embedded cases (ie mine), a BIOS likely
gets the TPM into a state where this code path isn't necessary.

Signed-off-by: Jason Gunthorpe &lt;jgunthorpe@obsidianresearch.com&gt;
Acked-by: Rajiv Andrade &lt;srajiv@linux.vnet.ibm.com&gt;
Signed-off-by: James Morris &lt;jmorris@namei.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>powerpc/ps3: Workaround for flash memory I/O error</title>
<updated>2009-09-24T15:47:27Z</updated>
<author>
<name>Geoff Levand</name>
<email>geoffrey.levand@am.sony.com</email>
</author>
<published>2009-09-09T13:28:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=30a864e5edc5e3cd001cb1194eea87695ef7f29d'/>
<id>urn:sha1:30a864e5edc5e3cd001cb1194eea87695ef7f29d</id>
<content type='text'>
commit bc00351edd5c1b84d48c3fdca740fedfce4ae6ce upstream.

A workaround for flash memory I/O errors when the PS3 internal
hard disk has not been formatted for OtherOS use.

This error condition mainly effects 'Live CD' users who have not
formatted the PS3's internal hard disk for OtherOS.

Fixes errors similar to these when using the ps3-flash-util
or ps3-boot-game-os programs:

  ps3flash read failed 0x2050000
  os_area_header_read: read error: os_area_header: Input/output error
  main:627: os_area_read_hp error.
  ERROR: can't change boot flag

Signed-off-by: Geoff Levand &lt;geoffrey.levand@am.sony.com&gt;
Signed-off-by: Benjamin Herrenschmidt &lt;benh@kernel.crashing.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>E100: fix interaction with swiotlb on X86.</title>
<updated>2009-09-15T17:37:19Z</updated>
<author>
<name>Krzysztof Hałasa</name>
<email>khc@pm.waw.pl</email>
</author>
<published>2009-08-24T02:02:13Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=832b524a136e7306f66a632a42dbc86fd41b2f3c'/>
<id>urn:sha1:832b524a136e7306f66a632a42dbc86fd41b2f3c</id>
<content type='text'>
[ Upstream commit 6ff9c2e7fa8ca63a575792534b63c5092099c286 ]

E100 places it's RX packet descriptors inside skb-&gt;data and uses them
with bidirectional streaming DMA mapping. Data in descriptors is
accessed simultaneously by the chip (writing status and size when
a packet is received) and CPU (reading to check if the packet was
received). This isn't a valid usage of PCI DMA API, which requires use
of the coherent (consistent) memory for such purpose. Unfortunately e100
chips working in "simplified" RX mode have to store received data
directly after the descriptor. Fixing the driver to conform to the API
would require using unsupported "flexible" RX mode or receiving data
into a coherent memory and using CPU to copy it to network buffers.

This patch, while not yet making the driver conform to the PCI DMA API,
allows it to work correctly on X86 with swiotlb (while not breaking
other architectures).

Signed-off-by: Krzysztof Hałasa &lt;khc@pm.waw.pl&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>SCSI: sr: report more accurate drive status after closing the tray.</title>
<updated>2009-09-09T03:17:50Z</updated>
<author>
<name>Peter Jones</name>
<email>pjones@redhat.com</email>
</author>
<published>2009-08-18T14:18:20Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=deeab04d78c0b5b505853a8f6810fb70bc40acd2'/>
<id>urn:sha1:deeab04d78c0b5b505853a8f6810fb70bc40acd2</id>
<content type='text'>
commit 96bcc722c47d07b6fd05c9d0cb3ab8ea5574c5b1 upstream

[SCSI] sr: report more accurate drive status after closing the tray.

So, what's happening here is that the drive is reporting a sense of
2/4/1 ("logical unit is becoming ready") from sr_test_unit_ready(), and
then we ask for the media event notification before checking that result
at all.  The check_media_event_descriptor() call isn't getting a check
condition, but it's also reporting that the tray is closed and that
there's no media.  In actuality it doesn't yet know if there's media or
not, but there's no way to express that in the media event status field.

My current thought is that if it told us the device isn't yet ready, we
should return that immediately, since there's nothing that'll tell us
any more data than that reliably:

Signed-off-by: James Bottomley &lt;James.Bottomley@HansenPartnership.com&gt;
Cc: Chuck Ebbert &lt;cebbert@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>Remove low_latency flag setting from nozomi and mxser drivers</title>
<updated>2009-09-09T03:17:49Z</updated>
<author>
<name>Chuck Ebbert</name>
<email>cebbert@redhat.com</email>
</author>
<published>2009-08-18T14:23:09Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=206c31f296348cbd3c9a7700a6f9b946459914be'/>
<id>urn:sha1:206c31f296348cbd3c9a7700a6f9b946459914be</id>
<content type='text'>
commit 4d8d4d251df8eaaa3dae71c8cfa7fbf4510d967d upstream

[ cebbert@redhat.com: backport to 2.6.27 ]

Remove low_latency flag setting from nozomi and mxser drivers

The kernel oopses if this flag is set.

[and neither driver should set it as they call tty_flip_buffer_push from IRQ
 paths so have always been buggy]

Signed-off-by: Chuck Ebbert &lt;cebbert@redhat.com&gt;
Signed-off-by: Alan Cox &lt;alan@linux.intel.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@linux-foundation.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
</feed>
