<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel/linux.git/drivers/ide, branch linux-2.6.22.y</title>
<subtitle>Linux kernel stable tree (mirror)</subtitle>
<id>https://git.radix-linux.su/kernel/linux.git/atom?h=linux-2.6.22.y</id>
<link rel='self' href='https://git.radix-linux.su/kernel/linux.git/atom?h=linux-2.6.22.y'/>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/'/>
<updated>2007-11-21T17:25:56+00:00</updated>
<entry>
<title>ide: fix serverworks.c UDMA regression</title>
<updated>2007-11-21T17:25:56+00:00</updated>
<author>
<name>Tony Battersby</name>
<email>tonyb@cybernetics.com</email>
</author>
<published>2007-10-16T20:29:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=0b81a81aecb120cff349eec24c2553e88c94991c'/>
<id>urn:sha1:0b81a81aecb120cff349eec24c2553e88c94991c</id>
<content type='text'>
patch 0c824b51b338c808de650b440ba5f9f4a725f7fc in mainline.

The patch described by the following excerpt from ChangeLog-2.6.22 makes
it impossible to use UDMA on a Tyan S2707 motherboard (SvrWks CSB5):

commit 2d5eaa6dd744a641e75503232a01f52d0768884c
Author: Bartlomiej Zolnierkiewicz &lt;bzolnier@gmail.com&gt;
Date:   Thu May 10 00:01:08 2007 +0200

    ide: rework the code for selecting the best DMA transfer mode (v3)

    ...

This one-line patch against 2.6.23 fixes the problem.

Signed-off-by: Tony Battersby &lt;tonyb@cybernetics.com&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>qd65xx: fix PIO mode selection</title>
<updated>2007-07-08T13:21:58+00:00</updated>
<author>
<name>Bartlomiej Zolnierkiewicz</name>
<email>bzolnier@gmail.com</email>
</author>
<published>2007-07-08T13:21:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=4660897e6c2daa198fc8e3f47ae2a4aef69c80b0'/>
<id>urn:sha1:4660897e6c2daa198fc8e3f47ae2a4aef69c80b0</id>
<content type='text'>
PIO4 is a maximum PIO mode supported by a driver.  Using "255" as a max_mode
argument to ide_get_best_pio_mode() could result in wrong timings being used
by a driver (for "pio" equal to 5) or OOPS (for "pio" values &gt; 5 &amp;&amp; &lt; 255).

Signed-off-by: Bartlomiej Zolnierkiewicz &lt;bzolnier@gmail.com&gt;
Acked-by: Sergei Shtylyov &lt;sshtylyov@ru.mvista.com&gt;
Reviewed-by: Alan Cox &lt;alan@lxorguk.ukuu.org.uk&gt;
</content>
</entry>
<entry>
<title>sis5513: adding PCI-ID</title>
<updated>2007-07-08T13:21:58+00:00</updated>
<author>
<name>Uwe Koziolek</name>
<email>uwe.koziolek@gmx.net</email>
</author>
<published>2007-07-08T13:21:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=4c6c914e4c2e0f91775ce4051b5a800c55175462'/>
<id>urn:sha1:4c6c914e4c2e0f91775ce4051b5a800c55175462</id>
<content type='text'>
The SiS966 has one additional PCI-ID 1180.

If the chipset is using this PCI-ID, the primary channel is connected to the
first PATA-port. The secondary channel is connected to SATA-ports in IDE
emulation mode.  The legacy IO-ports are used.

The including of the PCI-ID into pata_sis is not sufficient, because the legacy
driver in drivers/ide is initialized before pata_sis.

Signed-off-by: Uwe Koziolek &lt;uwe.koziolek@gmx.net&gt;
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;bzolnier@gmail.com&gt;

</content>
</entry>
<entry>
<title>ide: ide_scan_pcibus(): check __pci_register_driver return value</title>
<updated>2007-07-03T20:28:36+00:00</updated>
<author>
<name>Andrew Morton</name>
<email>akpm@linux-foundation.org</email>
</author>
<published>2007-07-03T20:28:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=d61bcce9c1aa2c9f8a768d73c4c517f81d226725'/>
<id>urn:sha1:d61bcce9c1aa2c9f8a768d73c4c517f81d226725</id>
<content type='text'>
drivers/ide/setup-pci.c: In function 'ide_scan_pcibus':
drivers/ide/setup-pci.c:879: warning: ignoring return value of '__pci_register_driver', declared with attribute warn_unused_result

Signed-off-by: Andrew Morton &lt;akpm@linux-foundation.org&gt;
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;bzolnier@gmail.com&gt;
</content>
</entry>
<entry>
<title>ide: pdc202xx_new PLL input clock fix</title>
<updated>2007-07-03T20:28:36+00:00</updated>
<author>
<name>Albert Lee</name>
<email>albertcc@tw.ibm.com</email>
</author>
<published>2007-07-03T20:28:36+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=8006bf56e360a4db71d304df778870a371a9e930'/>
<id>urn:sha1:8006bf56e360a4db71d304df778870a371a9e930</id>
<content type='text'>
Recently the PLL input clock of Promise 2027x is sometimes detected
higher than expected (e.g. 20.027 MHz compared to 16.714 MHz).
It seems sometimes the mdelay() function is not as precise as it
used to be. Per Alan's advice, HT or power management might affect
the precision of mdelay().

This patch calls gettimeofday() to measure the time elapsed and
calculate the PLL input clock accordingly.

Signed-off-by: Albert Lee &lt;albertcc@tw.ibm.com&gt;
Cc: Alan Cox &lt;alan@lxorguk.ukuu.org.uk&gt;
Cc: Bahadir Balban &lt;bahadir.balban@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>it821x: fix incorrect SWDMA mask</title>
<updated>2007-07-03T20:28:35+00:00</updated>
<author>
<name>Bartlomiej Zolnierkiewicz</name>
<email>bzolnier@gmail.com</email>
</author>
<published>2007-07-03T20:28:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=52374f890c1d0d64148d55a20d995a0b3e0ae987'/>
<id>urn:sha1:52374f890c1d0d64148d55a20d995a0b3e0ae987</id>
<content type='text'>
SWDMA modes are unsupported by it821x.  Attempts to tune SWDMA modes always
fail (due to sanity check in -&gt;speedproc) and result in PIO being tuned.

* Fix incorrect SWDMA mask so core code won't try these modes and will just
  tune PIO if no other DMA modes are available.

* Bump driver version.

Signed-off-by: Bartlomiej Zolnierkiewicz &lt;bzolnier@gmail.com&gt;
Acked-by: Sergei Shtylyov &lt;sshtylyov@ru.mvista.com&gt;
</content>
</entry>
<entry>
<title>amd74xx: resume fix</title>
<updated>2007-07-03T20:28:35+00:00</updated>
<author>
<name>Bartlomiej Zolnierkiewicz</name>
<email>bzolnier@gmail.com</email>
</author>
<published>2007-07-03T20:28:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=603a0e2c0a160ad8c2d00d71a700bb95482be5de'/>
<id>urn:sha1:603a0e2c0a160ad8c2d00d71a700bb95482be5de</id>
<content type='text'>
* Driver can't skip programming transfer mode on the device in amd_set_drive()
  (similar fix has been applied to via82cxxx driver ages ago).

* While at it remove redundant warning (ide_config_drive_speed() already
  produces more valuable one).

* Bump driver version.

Signed-off-by: Bartlomiej Zolnierkiewicz &lt;bzolnier@gmail.com&gt;
</content>
</entry>
<entry>
<title>hpt366: use correct enablebits for HPT36x</title>
<updated>2007-07-03T20:28:35+00:00</updated>
<author>
<name>Sergei Shtylyov</name>
<email>sshtylyov@ru.mvista.com</email>
</author>
<published>2007-07-03T20:28:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=96dcc08b0c6b730474469b10ed5eeda06e617deb'/>
<id>urn:sha1:96dcc08b0c6b730474469b10ed5eeda06e617deb</id>
<content type='text'>
The HPT36x chips finally turned out to have the channel enable bits -- however,
badly implemented.  Make use of them despite it's probably only going to burden
the driver's code -- assuming both channels are always enabled by the HighPoint
BIOS anyway...

Signed-off-by: Sergei Shtylyov &lt;sshtylyov@ru.mvista.com&gt;
Acked-by: Linas Vepstas &lt;linas@austin.ibm.com&gt;
Cc: michal.kepien@poczta.onet.pl
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;bzolnier@gmail.com&gt;
</content>
</entry>
<entry>
<title>hpt366: blacklist MAXTOR STM3320620A for UltraDMA/66</title>
<updated>2007-07-03T20:28:35+00:00</updated>
<author>
<name>Sergei Shtylyov</name>
<email>sshtylyov@ru.mvista.com</email>
</author>
<published>2007-07-03T20:28:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=783353b1d3d1ed3ae4a0bd4ea4557bd4d77aa04e'/>
<id>urn:sha1:783353b1d3d1ed3ae4a0bd4ea4557bd4d77aa04e</id>
<content type='text'>
Add the MAXTOR STM3320620A drive into the UltraDMA/66 mode blacklist
for the HPT36x chips.

Signed-off-by: Sergei Shtylyov &lt;sshtylyov@ru.mvista.com&gt;
Acked-by: Linas Vepstas &lt;linas@austin.ibm.com&gt;
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;bzolnier@gmail.com&gt;
</content>
</entry>
<entry>
<title>ide: Fix a theoretical Ooops case</title>
<updated>2007-07-03T20:28:35+00:00</updated>
<author>
<name>Alan Cox</name>
<email>alan@redhat.com</email>
</author>
<published>2007-07-03T20:28:35+00:00</published>
<link rel='alternate' type='text/html' href='https://git.radix-linux.su/kernel/linux.git/commit/?id=785955752fde4c555a1d9f74ddfe1f7aca3e0c7f'/>
<id>urn:sha1:785955752fde4c555a1d9f74ddfe1f7aca3e0c7f</id>
<content type='text'>
Found by a static analyser. It is in theory possible we dereference
dev-&gt;id when it has become invalid. Re-order to avoid this.

Not needed for new-ide as we no longer support the crazy exabyte nest stuff

Signed-off-by: Alan Cox &lt;alan@redhat.com&gt;
Cc: Andrew Morton &lt;akpm@osdl.org&gt;
Signed-off-by: Bartlomiej Zolnierkiewicz &lt;bzolnier@gmail.com&gt;

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