<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers, branch v2.6.30.8</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers?h=v2.6.30.8</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers?h=v2.6.30.8'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2009-09-24T15:27:29Z</updated>
<entry>
<title>PCI: Unhide the SMBus on the Compaq Evo D510 USDT</title>
<updated>2009-09-24T15:27:29Z</updated>
<author>
<name>Jean Delvare</name>
<email>khali@linux-fr.org</email>
</author>
<published>2009-07-28T09:49:19Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8717bad06ba13356600381e5babe5f62e74c49be'/>
<id>urn:sha1:8717bad06ba13356600381e5babe5f62e74c49be</id>
<content type='text'>
commit 6b5096e4d4496e185cd1ada5d1b8e1d941c805ed upstream.

One more form factor for Compaq Evo D510, which needs the same quirk
as the other form factors. Apparently there's no hardware monitoring
chip on that one, but SPD EEPROMs, so it's still worth unhiding the
SMBus.

Signed-off-by: Jean Delvare &lt;khali@linux-fr.org&gt;
Tested-by: Nuzhna Pomoshch &lt;nuzhna_pomoshch@yahoo.com&gt;
Signed-off-by: Jesse Barnes &lt;jbarnes@virtuousgeek.org&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:27:28Z</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=db4d3b9dedd857ae5f90301a654b7997132be7ae'/>
<id>urn:sha1:db4d3b9dedd857ae5f90301a654b7997132be7ae</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>virtio_blk: don't bounce highmem requests</title>
<updated>2009-09-24T15:27:28Z</updated>
<author>
<name>Christoph Hellwig</name>
<email>hch@lst.de</email>
</author>
<published>2009-09-11T22:49:19Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=98d53d73e1a28f0f55de4141ef91799aba0507b6'/>
<id>urn:sha1:98d53d73e1a28f0f55de4141ef91799aba0507b6</id>
<content type='text'>
commit 4eff3cae9c9809720c636e64bc72f212258e0bd5 upstream

virtio_blk: don't bounce highmem requests

By default a block driver bounces highmem requests, but virtio-blk is
perfectly fine with any request that fit into it's 64 bit addressing scheme,
mapped in the kernel virtual space or not.

Besides improving performance on highmem systems this also makes the
reproducible oops in __bounce_end_io go away (but hiding the real cause).

Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;
Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
Cc: Chuck Ebbert &lt;cebbert@redhat.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;
</content>
</entry>
<entry>
<title>V4L: em28xx: set up tda9887_conf in em28xx_card_setup()</title>
<updated>2009-09-24T15:27:27Z</updated>
<author>
<name>Franklin Meng</name>
<email>fmeng2002@yahoo.com</email>
</author>
<published>2009-09-12T14:31:05Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=330c9c3402b93246476e685c41da974663c152cc'/>
<id>urn:sha1:330c9c3402b93246476e685c41da974663c152cc</id>
<content type='text'>
V4L: em28xx: set up tda9887_conf in em28xx_card_setup()

(cherry picked from commit ae3340cbf59ea362c2016eea762456cc0969fd9e)

Added tda9887_conf set up into em28xx_card_setup()

Signed-off-by: Franklin Meng &lt;fmeng2002@yahoo.com&gt;
Signed-off-by: Douglas Schilling Landgraf &lt;dougsland@redhat.com&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@redhat.com&gt;
Tested-by: Larry Finger &lt;Larry.Finger@lwfinger.net&gt;
Signed-off-by: Michael Krufky &lt;mkrufky@linuxtv.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>PCI: apply nv_msi_ht_cap_quirk on resume too</title>
<updated>2009-09-24T15:27:16Z</updated>
<author>
<name>Tejun Heo</name>
<email>tj@kernel.org</email>
</author>
<published>2009-07-21T23:08:43Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=23b7ff36511e0aea0b054d0c7236f8f91509da07'/>
<id>urn:sha1:23b7ff36511e0aea0b054d0c7236f8f91509da07</id>
<content type='text'>
commit 6dab62ee5a3bf4f71b8320c09db2e6022a19f40e upstream.

http://bugzilla.kernel.org/show_bug.cgi?id=12542 reports that with the
quirk not applied on resume, msi stops working after resuming and mcp78s
ahci fails due to IRQ mis-delivery.  Apply it on resume too.

Signed-off-by: Tejun Heo &lt;tj@kernel.org&gt;
Cc: Peer Chen &lt;pchen@nvidia.com&gt;
Cc: Tj &lt;linux@tjworld.net&gt;
Reported-by: Nicolas Derive &lt;kalon33@ubuntu.com&gt;
Cc: Greg KH &lt;greg@kroah.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Jesse Barnes &lt;jbarnes@virtuousgeek.org&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>mlx4_core: Allocate and map sufficient ICM memory for EQ context</title>
<updated>2009-09-24T15:27:16Z</updated>
<author>
<name>Roland Dreier</name>
<email>rolandd@cisco.com</email>
</author>
<published>2009-09-06T03:24:49Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=359de899b30a6c1c18e53ca4a8e4265d9f7f67c0'/>
<id>urn:sha1:359de899b30a6c1c18e53ca4a8e4265d9f7f67c0</id>
<content type='text'>
commit fa0681d2129732027355d6b7083dd8932b9b799d upstream.

The current implementation allocates a single host page for EQ context
memory, which was OK when we only allocated a few EQs.  However, since
we now allocate an EQ for each CPU core, this patch removes the
hard-coded limit (which we exceed with 4 KB pages and 128 byte EQ
context entries with 32 CPUs) and uses the same ICM table code as all
other context tables, which ends up simplifying the code quite a bit
while fixing the problem.

This problem was actually hit in practice on a dual-socket Nehalem box
with 16 real hardware threads and sufficiently odd ACPI tables that it
shows on boot

    SMP: Allowing 32 CPUs, 16 hotplug CPUs

so num_possible_cpus() ends up 32, and mlx4 ends up creating 33 MSI-X
interrupts and 33 EQs.  This mlx4 bug means that mlx4 can't even
initialize at all on this quite mainstream system.

Reported-by: Eli Cohen &lt;eli@mellanox.co.il&gt;
Tested-by: Christoph Lameter &lt;cl@linux-foundation.org&gt;
Signed-off-by: Roland Dreier &lt;rolandd@cisco.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:27:11Z</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=3aad23963b58deb117f763805176b5dec74dc5b0'/>
<id>urn:sha1:3aad23963b58deb117f763805176b5dec74dc5b0</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:27:11Z</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=423b4ef5e712ef34d55d070d0cb84c9bb4a07ec2'/>
<id>urn:sha1:423b4ef5e712ef34d55d070d0cb84c9bb4a07ec2</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>ath5k: write PCU registers on initial reset</title>
<updated>2009-09-24T15:27:08Z</updated>
<author>
<name>Bob Copeland</name>
<email>me@bobcopeland.com</email>
</author>
<published>2009-07-05T01:03:13Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=f1d3ff8e09a2f7bf1ba969c1d38d29725ef1a4c4'/>
<id>urn:sha1:f1d3ff8e09a2f7bf1ba969c1d38d29725ef1a4c4</id>
<content type='text'>
commit 3355443ad7601991affa5992b0d53870335af765 upstream.

"Ath5k: unify resets"
introduced a regression into 2.6.28 where the PCU registers are never
initialized, due to ath5k_reset() always passing true for change_channel.
We subsequently program a lot of these registers but several may start
in an unknown state.

Reported-by: Forrest Zhang &lt;forrest@hifulltech.com&gt;
Signed-off-by: Bob Copeland &lt;me@bobcopeland.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>agp/intel: remove restore in resume</title>
<updated>2009-09-24T15:27:06Z</updated>
<author>
<name>Zhenyu Wang</name>
<email>zhenyuw@linux.intel.com</email>
</author>
<published>2009-09-14T02:47:06Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=23c686de43928eb7d2bcc2485333e87498f5a27e'/>
<id>urn:sha1:23c686de43928eb7d2bcc2485333e87498f5a27e</id>
<content type='text'>
commit 121264827656f5f06328b17983c796af17dc5949 upstream.

As early pci resume has already restored config for host
bridge and graphics device, don't need to restore it again,
This removes an original order hack for graphics device restore.

This fixed the resume hang issue found by Alan Stern on 845G,
caused by extra config restore on graphics device.

Cc: Alan Stern &lt;stern@rowland.harvard.edu&gt;
Signed-off-by: Zhenyu Wang &lt;zhenyuw@linux.intel.com&gt;
Signed-off-by: Dave Airlie &lt;airlied@linux.ie&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
</feed>
