<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers, branch v2.6.18.7</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers?h=v2.6.18.7</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers?h=v2.6.18.7'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2006-12-17T00:20:48Z</updated>
<entry>
<title>[PATCH] forcedeth: Disable INTx when enabling MSI in forcedeth</title>
<updated>2006-12-17T00:20:48Z</updated>
<author>
<name>Daniel Barkalow</name>
<email>barkalow@iabervon.org</email>
</author>
<published>2006-12-08T16:58:15Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=8dc0b54bc7e4d14efdd0314a9d9e3960a230d527'/>
<id>urn:sha1:8dc0b54bc7e4d14efdd0314a9d9e3960a230d527</id>
<content type='text'>
At least some nforce cards continue to send legacy interrupts when MSI
is enabled, and these interrupts are treated as unhandled by the
kernel. This patch disables legacy interrupts explicitly when enabling
MSI mode.

The correct fix is to change the MSI infrastructure to disable legacy
interrupts when enabling MSI, but this is potentially risky if the
device isn't PCI-2.3 or is quirky, so the correct fix is going into
mainline, while patches like this one go into -stable.

Legend has it that it is most correct to disable legacy interrupts
before enabling MSI, but the mainline patch does it in the other
order, and this patch is "obviously" the same as mainline.

Signed-off-by: Daniel Barkalow &lt;barkalow@iabervon.org&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] ieee1394: ohci1394: add PPC_PMAC platform code to driver probe</title>
<updated>2006-12-17T00:20:48Z</updated>
<author>
<name>Stefan Richter</name>
<email>stefanr@s5r6.in-berlin.de</email>
</author>
<published>2006-12-13T04:00:16Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=44ad470075f19907c6d92ee837e75db1724b0f46'/>
<id>urn:sha1:44ad470075f19907c6d92ee837e75db1724b0f46</id>
<content type='text'>
Fixes http://bugzilla.kernel.org/show_bug.cgi?id=7431
iBook G3 threw a machine check exception and put the display backlight
to full brightness after ohci1394 was unloaded and reloaded.

Signed-off-by: Stefan Richter &lt;stefanr@s5r6.in-berlin.de&gt;
[dsd@gentoo.org: also added missing if condition, commit
 63cca59e89892497e95e1e9c7156d3345fb7e2e8]
Signed-off-by: Daniel Drake &lt;dsd@gentoo.org&gt;
Acked-by: Stefan Richter &lt;stefanr@s5r6.in-berlin.de&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] V4L: Fix broken TUNER_LG_NTSC_TAPE radio support</title>
<updated>2006-12-17T00:20:47Z</updated>
<author>
<name>Hans Verkuil</name>
<email>hverkuil@xs4all.nl</email>
</author>
<published>2006-12-12T05:36:39Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=250c26f60da65f76e561522238b1ceeac673686b'/>
<id>urn:sha1:250c26f60da65f76e561522238b1ceeac673686b</id>
<content type='text'>
The TUNER_LG_NTSC_TAPE is identical in all respects to the
TUNER_PHILIPS_FM1236_MK3. So use the params struct for the Philips tuner.
Also add this LG_NTSC_TAPE tuner to the switches where radio specific
parameters are set so it behaves like a TUNER_PHILIPS_FM1236_MK3. This
change fixes the radio support for this tuner (the wrong bandswitch byte
was used).

Thanks to Andy Walls &lt;cwalls@radix.net&gt; for finding this bug.

Signed-off-by: Hans Verkuil &lt;hverkuil@xs4all.nl&gt;
Signed-off-by: Mauro Carvalho Chehab &lt;mchehab@infradead.org&gt;
Signed-off-by: Michael Krufky &lt;mkrufky@linuxtv.org&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] DVB: lgdt330x: fix signal / lock status detection bug</title>
<updated>2006-12-17T00:20:47Z</updated>
<author>
<name>Michael Krufky</name>
<email>mkrufky@linuxtv.org</email>
</author>
<published>2006-12-12T05:34:27Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5252ec9f76aa29c4bb1ab171d5f497c2baeb5657'/>
<id>urn:sha1:5252ec9f76aa29c4bb1ab171d5f497c2baeb5657</id>
<content type='text'>
In some cases when using VSB, the AGC status register has been known to
falsely report "no signal" when in fact there is a carrier lock.  The
datasheet labels these status flags as QAM only, yet the lgdt330x
module is using these flags for both QAM and VSB.

This patch allows for the carrier recovery lock status register to be
tested, even if the agc signal status register falsely reports no signal.

Thanks to jcrews from #linuxtv in irc, for initially reporting this bug.

Signed-off-by: Michael Krufky &lt;mkrufky@linuxtv.org&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] bonding: incorrect bonding state reported via ioctl</title>
<updated>2006-12-17T00:20:47Z</updated>
<author>
<name>Andy Gospodarek</name>
<email>andy@greyhouse.net</email>
</author>
<published>2006-11-21T16:46:44Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=198a9f8d9c6f6260b69e9f68bbc063cecba222b0'/>
<id>urn:sha1:198a9f8d9c6f6260b69e9f68bbc063cecba222b0</id>
<content type='text'>
This is a small fix-up to finish out the work done by Jay Vosburgh to
add carrier-state support for bonding devices.  The output in
/proc/net/bonding/bondX was correct, but when collecting the same info
via an iotcl it could still be incorrect.

Signed-off-by: Andy Gospodarek &lt;andy@greyhouse.net&gt;
Cc: Jeff Garzik &lt;jeff@garzik.org&gt;
Cc: Stephen Hemminger &lt;shemminger@osdl.org&gt;
Signed-off-by: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Jeff Garzik &lt;jeff@garzik.org&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] dm snapshot: fix freeing pending exception</title>
<updated>2006-12-17T00:20:47Z</updated>
<author>
<name>Milan Broz</name>
<email>mbroz@redhat.com</email>
</author>
<published>2006-12-05T15:11:18Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2b64e22fdbc35b4a0e7c1cbda590daaced401c35'/>
<id>urn:sha1:2b64e22fdbc35b4a0e7c1cbda590daaced401c35</id>
<content type='text'>
Fix oops when removing full snapshot
kernel bugzilla bug 7040

If a snapshot became invalid (full) while there is outstanding
pending_exception, pending_complete() forgets to remove
the corresponding exception from its exception table before freeing it.

Already fixed in 2.6.19.

Signed-off-by: Milan Broz &lt;mbroz@redhat.com&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] SUNHME: Fix for sunhme failures on x86</title>
<updated>2006-12-17T00:20:47Z</updated>
<author>
<name>Jurij Smakov</name>
<email>jurij@wooyd.org</email>
</author>
<published>2006-12-04T03:36:32Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=b501bcbbb21d2222fa4f0a11d89dffa9fa508be3'/>
<id>urn:sha1:b501bcbbb21d2222fa4f0a11d89dffa9fa508be3</id>
<content type='text'>
The following patch fixes the failure of sunhme drivers on x86 hosts
due to missing pci_enable_device() and pci_set_master() calls, lost
during code refactoring. It has been filed as bugzilla bug #7502 [0]
and Debian bug #397460 [1].

[0] http://bugzilla.kernel.org/show_bug.cgi?id=7502
[1] http://bugs.debian.org/397460

Signed-off-by: Jurij Smakov &lt;jurij@wooyd.org&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] dm crypt: Fix data corruption with dm-crypt over RAID5</title>
<updated>2006-12-17T00:20:46Z</updated>
<author>
<name>Christophe Saout</name>
<email>christophe@saout.de</email>
</author>
<published>2006-12-02T02:27:56Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=43e5eb5c8cd3194f747c0a82b9939bfc48f352c5'/>
<id>urn:sha1:43e5eb5c8cd3194f747c0a82b9939bfc48f352c5</id>
<content type='text'>
Fix corruption issue with dm-crypt on top of software raid5. Cancelled
readahead bio's that report no error, just have BIO_UPTODATE cleared
were reported as successful reads to the higher layers (and leaving
random content in the buffer cache). Already fixed in 2.6.19.

Signed-off-by: Christophe Saout &lt;christophe@saout.de&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] AGP: Allocate AGP pages with GFP_DMA32 by default</title>
<updated>2006-12-02T00:12:37Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@osdl.org</email>
</author>
<published>2006-11-22T23:59:02Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=00e7bb6cc1034c0240c7e4474a79c51b6a1a8cbe'/>
<id>urn:sha1:00e7bb6cc1034c0240c7e4474a79c51b6a1a8cbe</id>
<content type='text'>
Not all graphic page remappers support physical addresses over the 4GB
mark for remapping, so while some do (the AMD64 GART always did, and I
just fixed the i965 to do so properly), we're safest off just forcing
GFP_DMA32 allocations to make sure graphics pages get allocated in the
low 32-bit address space by default.

AGP sub-drivers that really care, and can do better, could just choose
to implement their own allocator (or we could add another "64-bit safe"
default allocator for their use), but quite frankly, you're not likely
to care in practice.

So for now, this trivial change means that we won't be allocating pages
that we can't map correctly by mistake on x86-64.

[ On traditional 32-bit x86, this could never happen, because GFP_KERNEL
  would never allocate any highmem memory anyway ]

Acked-by: Andi Kleen &lt;ak@suse.de&gt;
Acked-by: Dave Jones &lt;davej@redhat.com&gt;
Cc: Eric Anholt &lt;eric@anholt.net&gt;
Cc: Keith Packard &lt;keithp@keithp.com&gt;
Signed-off-by: Linus Torvalds &lt;torvalds@osdl.org&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>[PATCH] TG3: Add missing unlock in tg3_open() error path.</title>
<updated>2006-12-02T00:12:37Z</updated>
<author>
<name>Ira W. Snyder</name>
<email>kernel@irasnyder.com</email>
</author>
<published>2006-11-22T02:59:09Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=0832d6b41e42dc682a53b2ab0417e6d285a1d523'/>
<id>urn:sha1:0832d6b41e42dc682a53b2ab0417e6d285a1d523</id>
<content type='text'>
Sparse noticed a locking imbalance in tg3_open(). This patch adds an
unlock to one of the error paths, so that tg3_open() always exits
without the lock held.

Signed-off-by: Ira W. Snyder &lt;kernel@irasnyder.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
</feed>
