<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/ide, branch v2.6.29.4</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/ide?h=v2.6.29.4</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/ide?h=v2.6.29.4'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2009-05-08T22:45:10Z</updated>
<entry>
<title>cs5536: define dma_sff_read_status() method</title>
<updated>2009-05-08T22:45:10Z</updated>
<author>
<name>Sergei Shtylyov</name>
<email>sshtylyov@ru.mvista.com</email>
</author>
<published>2009-05-05T11:34:34Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=80c2d4701095c98d01ae4cda681bd231625e4ac7'/>
<id>urn:sha1:80c2d4701095c98d01ae4cda681bd231625e4ac7</id>
<content type='text'>
commit 15da90b516e9da92cc1d90001e640fd6707d0e27 upstream.

The driver somehow got merged with the initializer for the dma_sff_read_status()
method missing which caused kernel panic on bootup.

This should fix the kernel.org bug #13026...

Signed-off-by: Sergei Shtylyov &lt;sshtylyov@ru.mvista.com&gt;
Reported-by: Arnd Hannemann &lt;hannemann@nets.rwth-aachen.de&gt;
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;bzolnier@gmail.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;


</content>
</entry>
<entry>
<title>hpt366: fix HPT370 DMA timeouts</title>
<updated>2009-04-27T17:37:01Z</updated>
<author>
<name>Sergei Shtylyov</name>
<email>sshtylyov@ru.mvista.com</email>
</author>
<published>2009-04-18T15:42:19Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=2a3403fd95cbf6f548198be0fd37a056d12a56fe'/>
<id>urn:sha1:2a3403fd95cbf6f548198be0fd37a056d12a56fe</id>
<content type='text'>
upstream commit: c018f1ee5cf81e58b93d9e93a2ee39cad13dc1ac

The big driver change in 2.4.19-rc1 introduced a regression for many HPT370[A]
chips -- DMA stopped to work completely, only causing endless timeouts...

The culprit has been identified (at last!): it turned to be the code resetting
the DMA state machine before each transfer. Stop doing it now as this counter-
measure has clearly caused more harm than good.

This should fix the kernel.org bug #7703.

Signed-off-by: Sergei Shtylyov &lt;sshtylyov@ru.mvista.com&gt;
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;bzolnier@gmail.com&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>ide-atapi: start DMA after issuing a packet command</title>
<updated>2009-04-27T17:36:54Z</updated>
<author>
<name>Borislav Petkov</name>
<email>petkovbb@gmail.com</email>
</author>
<published>2009-04-02T20:21:31Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=717ff472176c54e90a4074898a59037f9a4791f5'/>
<id>urn:sha1:717ff472176c54e90a4074898a59037f9a4791f5</id>
<content type='text'>
upstream commit: 2eba08270990b99fb5429b76ee97184ddd272f7f

Apparently¹, some ATAPI devices want to see the packet command first
before enabling DMA otherwise they simply hang indefinitely. Reorder the
two steps and start DMA only after having issued the command first.

[1] http://marc.info/?l=linux-kernel&amp;m=123835520317235&amp;w=2

Signed-off-by: Borislav Petkov &lt;petkovbb@gmail.com&gt;
Reported-by: Michael Roth &lt;mroth@nessie.de&gt;
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;bzolnier@gmail.com&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>ide: drivers/ide/ide-atapi.c needs &lt;linux/scatterlist.h&gt;</title>
<updated>2009-04-27T17:36:54Z</updated>
<author>
<name>Geert Uytterhoeven</name>
<email>geert@linux-m68k.org</email>
</author>
<published>2009-04-02T20:20:22Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=d7715a3e33ca1f6698ac9bec7d767a55f07fd65a'/>
<id>urn:sha1:d7715a3e33ca1f6698ac9bec7d767a55f07fd65a</id>
<content type='text'>
upstream commit: 479edf065576aeed7ac99d10838bb3b4f870b5f9

On m68k:
| drivers/ide/ide-atapi.c: In function 'ide_io_buffers':
| drivers/ide/ide-atapi.c:87: error: implicit declaration of function 'sg_page'
| drivers/ide/ide-atapi.c:87: warning: passing argument 1 of 'PageHighMem' makes pointer from integer without a cast
| drivers/ide/ide-atapi.c:91: warning: passing argument 1 of 'kmap_atomic' makes pointer from integer without a cast
| drivers/ide/ide-atapi.c:96: error: implicit declaration of function 'sg_virt'
| drivers/ide/ide-atapi.c:96: warning: assignment makes pointer from integer without a cast
| drivers/ide/ide-atapi.c:107: error: implicit declaration of function 'sg_next'
| drivers/ide/ide-atapi.c:107: warning: assignment makes pointer from integer without a cast

[bart: Dmitri Vorobiev submitted similar patch fixing MIPS]

Signed-off-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;
Cc: Dmitri Vorobiev &lt;dmitri.vorobiev@movial.com&gt;
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;bzolnier@gmail.com&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>ide: Fix code dealing with sleeping devices in do_ide_request()</title>
<updated>2009-04-27T17:36:51Z</updated>
<author>
<name>Elias Oltmanns</name>
<email>eo@nebensachen.de</email>
</author>
<published>2009-04-01T17:05:08Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=eddabbbaa0f368e82e2a9ee26fa5610df722ac10'/>
<id>urn:sha1:eddabbbaa0f368e82e2a9ee26fa5610df722ac10</id>
<content type='text'>
upstream commit: 9010941c5483a7a5bb1f7d97ee62491fb078bb51

Unfortunately, I missed a catch when reviewing the patch committed as
201bffa4. Here is the fix to the currently broken handling of sleeping
devices. In particular, this is required to get the disk shock
protection code working again.

Reported-by: Christian Thaeter &lt;ct@pipapo.org&gt;
Cc: stable@kernel.org
Signed-off-by: Elias Oltmanns &lt;eo@nebensachen.de&gt;
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;bzolnier@gmail.com&gt;
Signed-off-by: Chris Wright &lt;chrisw@sous-sol.org&gt;
</content>
</entry>
<entry>
<title>ide: save the returned value of dma_map_sg</title>
<updated>2009-03-13T20:16:13Z</updated>
<author>
<name>FUJITA Tomonori</name>
<email>fujita.tomonori@lab.ntt.co.jp</email>
</author>
<published>2009-03-13T20:16:13Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5d82720a7f41f0c877e026c7d17e3bf20ccdbae0'/>
<id>urn:sha1:5d82720a7f41f0c877e026c7d17e3bf20ccdbae0</id>
<content type='text'>
dma_map_sg could return a value different to 'nents' argument of
dma_map_sg so the ide stack needs to save it for the later usage
(e.g. for_each_sg).

The ide stack also needs to save the original sg_nents value for
pci_unmap_sg.

Signed-off-by: FUJITA Tomonori &lt;fujita.tomonori@lab.ntt.co.jp&gt;
[bart: backport to Linus' tree]
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;bzolnier@gmail.com&gt;
</content>
</entry>
<entry>
<title>ide-floppy: do not map dataless cmds to an sg</title>
<updated>2009-03-13T20:16:12Z</updated>
<author>
<name>Borislav Petkov</name>
<email>petkovbb@gmail.com</email>
</author>
<published>2009-03-13T20:16:12Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=3eb76c1ccde496c3c0bfda23d1c803e40b762ce6'/>
<id>urn:sha1:3eb76c1ccde496c3c0bfda23d1c803e40b762ce6</id>
<content type='text'>
since it fails the virt_to_page() translation check with DEBUG_VIRTUAL
enabled.

Signed-off-by: Borislav Petkov &lt;petkovbb@gmail.com&gt;
[bart: backport to Linus' tree]
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;bzolnier@gmail.com&gt;
</content>
</entry>
<entry>
<title>ide: add at91_ide driver</title>
<updated>2009-03-05T15:10:58Z</updated>
<author>
<name>Stanislaw Gruszka</name>
<email>stf_xl@wp.pl</email>
</author>
<published>2009-03-05T15:10:58Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6e5f1e1115bb041993f9f247036996364b4c84d5'/>
<id>urn:sha1:6e5f1e1115bb041993f9f247036996364b4c84d5</id>
<content type='text'>
This is IDE host driver for AT91 (SAM9, CAP9, AT572D940HF) Static Memory
Controller with Compact Flash True IDE Mode logic.

Driver have to switch 8/16 bit bus width when accessing Task Tile or Data
Register. Moreover some extra things need to be done when setting PIO mode.
Only PIO mode is used, hardware have no DMA support. If interrupt line is
connected through GPIO extra quirk is needed to cope with fake interrupts.

Signed-off-by: Stanislaw Gruszka &lt;stf_xl@wp.pl&gt;
Cc: Andrew Victor &lt;avictor.za@gmail.com&gt;
Acked-by: Sergei Shtylyov &lt;sshtylyov@ru.mvista.com&gt;
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;bzolnier@gmail.com&gt;
</content>
</entry>
<entry>
<title>ide: allow to wrap interrupt handler</title>
<updated>2009-03-05T15:10:57Z</updated>
<author>
<name>Stanislaw Gruszka</name>
<email>stf_xl@wp.pl</email>
</author>
<published>2009-03-05T15:10:57Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=849d7130001ab740a5a4778a561049841fdd77c9'/>
<id>urn:sha1:849d7130001ab740a5a4778a561049841fdd77c9</id>
<content type='text'>
Signed-off-by: Stanislaw Gruszka &lt;stf_xl@wp.pl&gt;
Cc: Andrew Victor &lt;linux@maxim.org.za&gt;
[bart: minor checkpatch.pl / CodingStyle fixups]
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;bzolnier@gmail.com&gt;
</content>
</entry>
<entry>
<title>ide-iops: fix odd-length ATAPI PIO transfers</title>
<updated>2009-03-05T15:10:56Z</updated>
<author>
<name>Sergei Shtylyov</name>
<email>sshtylyov@ru.mvista.com</email>
</author>
<published>2009-03-05T15:10:56Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=a509538d4fb4f99cdf0a095213d57cc3b2347615'/>
<id>urn:sha1:a509538d4fb4f99cdf0a095213d57cc3b2347615</id>
<content type='text'>
Commit 9567b349f7e7dd7e2483db99ee8e4a6fe0caca38 (ide: merge -&gt;atapi_*put_bytes
and -&gt;ata_*put_data methods) introduced a regression  WRT the odd-length ATAPI
PIO transfers -- the final word didn't get written (causing command timeouts).

Signed-off-by: Sergei Shtylyov &lt;sshtylyov@ru.mvista.com&gt;
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;bzolnier@gmail.com&gt;
</content>
</entry>
</feed>
