<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/include/linux/libata.h, branch linux-2.6.31.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.31.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.31.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2009-07-29T01:07:09Z</updated>
<entry>
<title>libata: accept late unlocking of HPA</title>
<updated>2009-07-29T01:07:09Z</updated>
<author>
<name>Tejun Heo</name>
</author>
<published>2009-07-15T08:11:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5920dadfb4aec6c1372c5570e71bcd3b4837e63c'/>
<id>urn:sha1:5920dadfb4aec6c1372c5570e71bcd3b4837e63c</id>
<content type='text'>
On certain configurations, HPA isn't or can't be unlocked during
probing but it somehow ends up unlocked afterwards.  In the following
thread, the problem can be reliably reproduced after resuming from
STR.  The BIOS turns on HPA during boot but forgets to do it during
resume.

  http://thread.gmane.org/gmane.linux.kernel/858310

This patch updates libata revalidation such that it considers native
n_sectors.  If the device size has increased to match native
n_sectors, it's assumed that HPA has been unlocked involuntarily and
the device is recognized as the same one.  This should be fairly safe
while nicely working around the problem.

Signed-off-by: Tejun Heo &lt;tj@kernel.org&gt;
Reported-by: Christof Warlich &lt;christof@warlich.name&gt;
Signed-off-by: Jeff Garzik &lt;jgarzik@redhat.com&gt;
</content>
</entry>
<entry>
<title>libata: implement and use HORKAGE_NOSETXFER, take#2</title>
<updated>2009-07-15T02:41:46Z</updated>
<author>
<name>Tejun Heo</name>
</author>
<published>2009-07-09T00:27:50Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=d0cb43b35d64877b2944bd37719708be5d7bbf99'/>
<id>urn:sha1:d0cb43b35d64877b2944bd37719708be5d7bbf99</id>
<content type='text'>
PIONEER DVD-RW DVRTD08 times out SETXFER if no media is present.  The
device is SATA and simply skipping SETXFER works around the problem.
Implement ATA_HORKAGE_NOSETXFER and apply it to the device.

Reported by Moritz Rigler in the following thread.

  http://thread.gmane.org/gmane.linux.ide/36790

and by Lars in bko#9540.

Updated to whine and ignore NOSETXFER if PATA component is detected as
suggested by Alan Cox.

Signed-off-by: Tejun Heo &lt;tj@kernel.org&gt;
Reported-by: Moritz Rigler &lt;linux-ide@momail.e4ward.com&gt;
Reported-by: Lars &lt;lars21ce@gmx.de&gt;
Cc: Alan Cox &lt;alan@lxorguk.ukuu.org.uk&gt;
Signed-off-by: Jeff Garzik &lt;jgarzik@redhat.com&gt;
</content>
</entry>
<entry>
<title>ata: Report 16/32bit PIO as best we can</title>
<updated>2009-04-16T19:28:23Z</updated>
<author>
<name>Alan Cox</name>
</author>
<published>2009-04-09T16:31:17Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e3cf95dd6d352954b663d2934110d6e30af2406d'/>
<id>urn:sha1:e3cf95dd6d352954b663d2934110d6e30af2406d</id>
<content type='text'>
The legacy old IDE ioctl API for this is a bit primitive so we try
and map stuff sensibly onto it.

- Set PIO over DMA devices to report 32bit
- Add ability to change the PIO32 settings if the controller permits it
- Add that functionality into the sff drivers
- Add that functionality into the VLB legacy driver
- Turn on the 32bit PIO on the ninja32 and add support there

Signed-off-by: Alan Cox &lt;alan@linux.intel.com&gt;
Signed-off-by: Jeff Garzik &lt;jgarzik@redhat.com&gt;
</content>
</entry>
<entry>
<title>trivial: Fix misspelling of firmware</title>
<updated>2009-03-30T13:21:59Z</updated>
<author>
<name>Nick Andrew</name>
</author>
<published>2009-01-26T10:06:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=877d03105d04b2c13e241130277fa69c8d2564f0'/>
<id>urn:sha1:877d03105d04b2c13e241130277fa69c8d2564f0</id>
<content type='text'>
Fix misspelling of firmware.

Signed-off-by: Nick Andrew &lt;nick@nick-andrew.net&gt;
Signed-off-by: Jiri Kosina &lt;jkosina@suse.cz&gt;
</content>
</entry>
<entry>
<title>[libata] Improve timeout handling</title>
<updated>2009-03-25T02:52:39Z</updated>
<author>
<name>Alan Cox</name>
</author>
<published>2009-03-24T10:23:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c96f1732e25362d10ee7bcac1df8412a2e6b7d23'/>
<id>urn:sha1:c96f1732e25362d10ee7bcac1df8412a2e6b7d23</id>
<content type='text'>
On a timeout call a device specific handler early in the recovery so that
we can complete and process successful commands which timed out due to IRQ
loss or the like rather more elegantly.

[Revised to exclude the timeout handling on a few devices that inherit from
 SFF but are not SFF enough to use the default timeout handler]

Signed-off-by: Alan Cox &lt;alan@redhat.com&gt;
Signed-off-by: Jeff Garzik &lt;jgarzik@redhat.com&gt;
</content>
</entry>
<entry>
<title>[libata] Drain data on errors</title>
<updated>2009-03-25T02:48:26Z</updated>
<author>
<name>Alan Cox</name>
</author>
<published>2009-03-24T10:23:19Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3d47aa8e7e7b2aa09256590388aa8dddc79280f9'/>
<id>urn:sha1:3d47aa8e7e7b2aa09256590388aa8dddc79280f9</id>
<content type='text'>
If the device is signalling that there is data to drain after an error we
should read the bytes out and throw them away. Without this some devices
and controllers get wedged and don't recover.

Based on earlier work by Mark Lord

Signed-off-by: Alan Cox &lt;alan@redhat.com&gt;
Signed-off-by: Jeff Garzik &lt;jgarzik@redhat.com&gt;
</content>
</entry>
<entry>
<title>[libata] Export ata_pio_queue_task() so that it can be used from sata_mv.</title>
<updated>2009-03-25T02:02:41Z</updated>
<author>
<name>Mark Lord</name>
</author>
<published>2009-02-25T20:18:32Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1a660164c291f41b2aa853a7269b310933574ef9'/>
<id>urn:sha1:1a660164c291f41b2aa853a7269b310933574ef9</id>
<content type='text'>
Signed-off-by: Mark Lord &lt;mlord@pobox.com&gt;
Signed-off-by: Jeff Garzik &lt;jgarzik@redhat.com&gt;
</content>
</entry>
<entry>
<title>libata: align ap-&gt;sector_buf</title>
<updated>2009-03-05T12:25:02Z</updated>
<author>
<name>Tejun Heo</name>
</author>
<published>2009-03-02T09:53:26Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=84bda12af31f930e4200c5244aa111de2485d7b0'/>
<id>urn:sha1:84bda12af31f930e4200c5244aa111de2485d7b0</id>
<content type='text'>
ap-&gt;sector_buf is used as DMA target and should at least be aligned on
cacheline.  This caused problems on some embedded machines.

Signed-off-by: Tejun Heo &lt;tj@kernel.org&gt;
Signed-off-by: Jeff Garzik &lt;jgarzik@redhat.com&gt;
</content>
</entry>
<entry>
<title>libata: fix dma_unmap_sg misuse</title>
<updated>2009-03-05T12:24:57Z</updated>
<author>
<name>FUJITA Tomonori</name>
</author>
<published>2009-02-27T08:35:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5825627c9463581fd9e70f8285685889ae5bb9bb'/>
<id>urn:sha1:5825627c9463581fd9e70f8285685889ae5bb9bb</id>
<content type='text'>
libata passes the returned value of dma_map_sg() to
dma_unmap_sg(),which is the misuse of dma_unmap_sg().

DMA-mapping.txt says:

To unmap a scatterlist, just call:

	pci_unmap_sg(pdev, sglist, nents, direction);

Again, make sure DMA activity has already finished.

PLEASE NOTE:  The 'nents' argument to the pci_unmap_sg call must be
              the _same_ one you passed into the pci_map_sg call,
	      it should _NOT_ be the 'count' value _returned_ from the
              pci_map_sg call.

Signed-off-by: FUJITA Tomonori &lt;fujita.tomonori@lab.ntt.co.jp&gt;
Acked-by: Bartlomiej Zolnierkiewicz &lt;bzolnier@gmail.com&gt;
Acked-by: Tejun Heo &lt;tj@kernel.org&gt;
Signed-off-by: Jeff Garzik &lt;jgarzik@redhat.com&gt;
</content>
</entry>
<entry>
<title>libata: change drive ready wait after hard reset to 5s</title>
<updated>2009-03-05T12:24:42Z</updated>
<author>
<name>Stuart Hayes</name>
</author>
<published>2009-03-04T19:59:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e7d3ef13d52a126438f687a1a32da65ff926ed57'/>
<id>urn:sha1:e7d3ef13d52a126438f687a1a32da65ff926ed57</id>
<content type='text'>
This fixes problems during resume with drives that take longer than 1s to
be ready.  The ATA-6 spec appears to allow 5 seconds for a drive to be
ready.

On one affected system, this patch changes "PM: resume devices took..."
message from 17 seconds to 4 seconds, and gets rid of a lot of ugly
timeout/error messages.

Without this patch, the libata code moves on after 1s, tries to send a
soft reset (which the drive doesn't see because it isn't ready) which also
times out, then an IDENTIFY command is sent to the drive which times out,
and finally the error handler will try to send another hard reset which
will finally get things working.

Signed-off-by: Stuart Hayes &lt;stuart_hayes@dell.com&gt;
Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Jeff Garzik &lt;jgarzik@redhat.com&gt;
</content>
</entry>
</feed>
