<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers, branch v2.6.28.4</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers?h=v2.6.28.4</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers?h=v2.6.28.4'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2009-02-06T21:47:24Z</updated>
<entry>
<title>ACPICA: Allow multiple backslash prefix in namepaths</title>
<updated>2009-02-06T21:47:24Z</updated>
<author>
<name>Lin Ming</name>
<email>ming.m.lin@intel.com</email>
</author>
<published>2008-11-13T02:54:39Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=723060e9421fb0bf065cfdd962df39a8daa450bb'/>
<id>urn:sha1:723060e9421fb0bf065cfdd962df39a8daa450bb</id>
<content type='text'>
commit d037c5fd7367548191eab2b376a1d08c4ffaf7ff upstream.

In a fully qualified namepath, allow multiple backslash prefixes.
This can happen because of the use of a double-backslash in strings
(since backslash is the escape character) causing confusion.
ACPICA BZ 739 Lin Ming.

http://www.acpica.org/bugzilla/show_bug.cgi?id=739

Signed-off-by: Lin Ming &lt;ming.m.lin@intel.com&gt;
Signed-off-by: Bob Moore &lt;robert.moore@intel.com&gt;
Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
Cc: Thomas Renninger &lt;trenn@suse.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>sata_mv: Fix chip type for Hightpoint RocketRaid 1740/1742</title>
<updated>2009-02-06T21:47:24Z</updated>
<author>
<name>Mark Lord</name>
<email>liml@rtr.ca</email>
</author>
<published>2009-01-27T21:33:13Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1b3826f5b9b1b9e3e60300080834b8979e63bd94'/>
<id>urn:sha1:1b3826f5b9b1b9e3e60300080834b8979e63bd94</id>
<content type='text'>
commit 4462254ac6be9150aae87d54d388fc348d6fcead upstream.

Fix chip type for the Highpoint RocketRAID 1740 and 1742 PCI cards.
These really do have Marvell 6042 chips on them, rather than the 5081 chip.

Confirmed by multiple (two) users (for the 1740), and by examining
the product photographs from Highpoint's web site.

Signed-off-by: Mark Lord &lt;mlord@pobox.com&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>ACPI: Do not modify SCI_EN directly</title>
<updated>2009-02-06T21:47:24Z</updated>
<author>
<name>Rafael J. Wysocki</name>
<email>rjw@sisk.pl</email>
</author>
<published>2008-12-29T18:19:07Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a88af3b3c8938d43bb0b0a71508b546086789eee'/>
<id>urn:sha1:a88af3b3c8938d43bb0b0a71508b546086789eee</id>
<content type='text'>
commit 11e93130c7ce5228d484fd5e86f3984835d4256b upstream.

According to the ACPI specification the SCI_EN flag is controlled by
the hardware, which sets this flag to inform the kernel that ACPI is
enabled.  For this reason, we shouldn't try to modify SCI_EN
directly.  Also, we don't need to do it in irqrouter_resume(), since
lower-level resume code takes care of enabling ACPI in case it hasn't
been enabled by the BIOS before passing control to the kernel (which
by the way is against the ACPI specification).

Signed-off-by: Rafael J. Wysocki &lt;rjw@sisk.pl&gt;
Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
Cc: Thomas Renninger &lt;trenn@suse.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>Newly inserted battery might differ from one just removed, so update of battery info fields is required.</title>
<updated>2009-02-06T21:47:23Z</updated>
<author>
<name>Alexey Starikovskiy</name>
<email>astarikovskiy@suse.de</email>
</author>
<published>2008-12-22T23:44:54Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=f74bb48f2e5ec381ba74f6952f55f0402c151d3e'/>
<id>urn:sha1:f74bb48f2e5ec381ba74f6952f55f0402c151d3e</id>
<content type='text'>
commit 50b178512b7d6e7724f87459f6bd06504c9c2da1 upstream.

Signed-off-by: Alexey Starikovskiy &lt;astarikovskiy@suse.de&gt;
Acked-by: Andy Neitzke &lt;neitzke@ias.edu&gt;

Signed-off-by: Alexey Starikovskiy &lt;astarikovskiy@suse.de&gt;
Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
Cc: Thomas Renninger &lt;trenn@suse.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>video: always update the brightness when poking "brightness"</title>
<updated>2009-02-06T21:47:23Z</updated>
<author>
<name>Zhang Rui</name>
<email>rui.zhang@intel.com</email>
</author>
<published>2008-12-31T02:58:48Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d0269c8bc47b632a1f195f14129772045162da5c'/>
<id>urn:sha1:d0269c8bc47b632a1f195f14129772045162da5c</id>
<content type='text'>
commit 9e6dada9d255497127251c03aaa59296d186f959 upstream.

always update props.brightness no matter the backlight is changed
via procfs, hotkeys or sysfs.

Sighed-off-by: Zhang Rui &lt;rui.zhang@intel.com&gt;
Acked-by: Matthew Garrett &lt;mjg59@srcf.ucam.org&gt;
Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
Cc: Thomas Renninger &lt;trenn@suse.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>cpuidle: Add decaying history logic to menu idle predictor</title>
<updated>2009-02-06T21:47:23Z</updated>
<author>
<name>Venkatesh Pallipadi</name>
<email>venkatesh.pallipadi@intel.com</email>
</author>
<published>2009-01-27T16:38:46Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=00559920e4bd114effb56e669690aa2479260af2'/>
<id>urn:sha1:00559920e4bd114effb56e669690aa2479260af2</id>
<content type='text'>
commit 816bb611e41be29b476dc16f6297eb551bf4d747 upstream

Add decaying history of predicted idle time, instead of using the last early
wakeup. This logic helps menu governor do better job of predicting idle time.

With this change, we also measured noticable (~8%) power savings on
a DP server system with CPUs supporting deep C states, when system
was lightly loaded. There was no change to power or perf on other load
conditions.

Signed-off-by: Venkatesh Pallipadi &lt;venkatesh.pallipadi@intel.com&gt;
Signed-off-by: Len Brown &lt;len.brown@intel.com&gt;
Cc: Thomas Renninger &lt;trenn@suse.de&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

</content>
</entry>
<entry>
<title>p54usb: rewriting rx/tx routines to make use of usb_anchor's facilities</title>
<updated>2009-02-06T21:47:22Z</updated>
<author>
<name>Christian Lamparter</name>
<email>chunkeey@web.de</email>
</author>
<published>2009-01-24T09:44:53Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d661ee77bd5eedd3782155b6c6f4426dda3abdd3'/>
<id>urn:sha1:d661ee77bd5eedd3782155b6c6f4426dda3abdd3</id>
<content type='text'>
commit dd397dc9dddfa2149a1bbc9e52ac7d5630737cec upstream

Alan Stern found several flaws in p54usb's implementation and annotated:
"usb_kill_urb() and similar routines do not expect an URB's completion
routine to deallocate it.  This is almost obvious -- if the URB is deallocated
before the completion routine returns then there's no way for usb_kill_urb
to detect when the URB actually is complete."

This patch addresses all known limitations in the old implementation and fixes
khub's "use-after-freed" hang, when SLUB debug's poisoning option is enabled.

Signed-off-by: Christian Lamparter &lt;chunkeey@web.de&gt;
Tested-by: Larry Finger &lt;Larry.Finger@lwfinger.net&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>p54: fix p54_read_eeprom to cope with tx_hdr_len</title>
<updated>2009-02-06T21:47:20Z</updated>
<author>
<name>Christian Lamparter</name>
<email>chunkeey@web.de</email>
</author>
<published>2009-01-24T09:44:40Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=621c147ff8fc7fca0d127e0e4c7c9c017560900a'/>
<id>urn:sha1:621c147ff8fc7fca0d127e0e4c7c9c017560900a</id>
<content type='text'>
commit b92f30d65aeb0502e2ed8beb80c8465578b40002 upstream

This patch fixes a regression in "p54: move eeprom code into common library"
7cb770729ba895f73253dfcd46c3fcba45d896f9

Some of p54usb's devices need a little headroom for the transportation and
this was forgotten in the eeprom change.

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

</content>
</entry>
<entry>
<title>p54: fix lm87 checksum endianness</title>
<updated>2009-02-06T21:47:20Z</updated>
<author>
<name>Johannes Berg</name>
<email>johannes@sipsolutions.net</email>
</author>
<published>2009-01-24T09:44:26Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=631c7b5c602f9516cfe11c4556181c14bee6fdb3'/>
<id>urn:sha1:631c7b5c602f9516cfe11c4556181c14bee6fdb3</id>
<content type='text'>
commit c91276592695e13d1b52eab572551017cbf96ee7 upstream

This fixes the checksum calculation for lm87 firmwares
on big endian platforms, the device treats the data as
an array of 32-bit little endian values so the driver
needs to do that as well.

Signed-off-by: Johannes Berg &lt;johannes@sipsolutions.net&gt;
Acked-by: Christian Lamparter &lt;chunkeey@web.de&gt;
Signed-off-by: John W. Linville &lt;linville@tuxdriver.com&gt;

</content>
</entry>
<entry>
<title>iwlwifi: fix rs_get_rate WARN_ON()</title>
<updated>2009-02-06T21:47:20Z</updated>
<author>
<name>Abbas, Mohamed</name>
<email>mohamed.abbas@intel.com</email>
</author>
<published>2009-01-21T18:58:02Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1d2966c46a14815bf7c5016b5ca6068bce9ec1c6'/>
<id>urn:sha1:1d2966c46a14815bf7c5016b5ca6068bce9ec1c6</id>
<content type='text'>
commit c338ba3ca5bef2df2082d9e8d336ff7b2880c326 upstream.

In ieee80211_sta structure there is u64 supp_rates[IEEE80211_NUM_BANDS]
this is filled with all support rate from assoc_resp.  If we associate
with G-band AP only supp_rates of G-band will be set the other band
supp_rates will be set to 0. If the user type this command
this will cause mac80211 to set to new channel, mac80211
does not disassociate in setting new channel, so the active
band is now A-band. then in handling the new essid mac80211 will
kick in the assoc steps which involve sending disassociation frame.
in this mac80211 will WARN_ON sta-&gt;supp_rates[A_BAND] == 0.

This fixes:
http://www.intellinuxwireless.org/bugzilla/show_bug.cgi?id=1822
http://www.kerneloops.org/searchweek.php?search=rs_get_rate

Signed-off-by: mohamed abbas &lt;mohamed.abbas@intel.com&gt;
Signed-off-by: Reinette Chatre &lt;reinette.chatre@intel.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>
</feed>
