linux-kernel - Re: libata limiting to UDMA/33 instead of UDMA/100

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-prev] [day] [month] [year] [list]

Message-ID: <20070610184536.7e29fe65@the-village.bc.nu>
Date:	Sun, 10 Jun 2007 18:45:36 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	"Udo A. Steinberg" <us15@...inf.tu-dresden.de>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: libata limiting to UDMA/33 instead of UDMA/100

> The patch fixes my cable detection problem. Now everything is back to
> UDMA/100 again. I noticed that ata1/ata2 claim to be using irq0, although
> they do in fact use irq10. This seems to be a purely cosmetical problem.

I think Tejun posted a patch for that one already - its purely cosmetic
and caused by soem of the core cleanup. The cmd/ctl/bmdma values are also
currently mis-reported from similar updates.

> ata1.01: ata_hpa_resize 1: sectors = 241254720, hpa_sectors = 241254720
> ata1.01: configured for UDMA/100

Will double check the and then push upstream
-
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/