lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 19 Jul 2006 02:29:59 +0200 (MEST)
From:	Mikael Pettersson <mikpe@...uu.se>
To:	mikpe@...uu.se, sshtylyov@...mvista.com
Cc:	alan@...hat.com, albertcc@...ibm.com, linux-ide@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: libata pata_pdc2027x success on sparc64

On Tue, 18 Jul 2006 22:07:44 +0400, Sergei Shtylyov wrote:
>> In contrast, the old IDE pdc202xx_new driver had lots
>> of problems with CRC errors causing it to disable DMA.
>
>    Hm, from my experience it usually falls back to UltraDMA/44 and then the 
>thing startrt working...
>
>> I wasn't able to manually tune it above udma3 without
>> getting more errors. This isn't sparc64-specific: I've
>> had similar negative experience with the old IDE Promise
>> drivers in a PowerMac.
>
>    This happens because the "old" driver misses the PLL calibration code.
>    You may want to try these Albert's patches:
>
>http://marc.theaimsgroup.com/?t=110992452800002&r=1&w=2
>http://marc.theaimsgroup.com/?t=110992471500002&r=1&w=2
>http://marc.theaimsgroup.com/?t=110992490100002&r=1&w=2
>http://marc.theaimsgroup.com/?t=111019238400003&r=1&w=2
>
>    It looks like they were never considered for accepting into the kernel
>while they succesfully solve this issue. Maybe Albert could try pushing them 
>into -mm tree once more?

Thank you for these links. After fixing up whitespace damage in
these four messages the patches applied OK and more importantly
eliminated _all_ misbehaviour from pdc202xx_new on both my sparc64
and my PowerMac.

These fixes belong in Linus' kernel, not some semi-obscure
mailing list archive.

/Mikael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ