From: Jussi Laako <jussi.laako@kolumbus.fi>
To: linux-kernel@vger.kernel.org
Cc: alan@lxorguk.ukuu.org.uk
Subject: [Fwd: Promise driver (pdc202xx)]
Date: 10 Jun 2002 02:51:20 +0300 [thread overview]
Message-ID: <1023666681.1163.4.camel@vaarlahti> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 335 bytes --]
I'm forwarding my mail to lkml also.
As addition to the information, mobo is ASUS A7M266 and Promise BIOS
version is 2.20.0.12.
- Jussi Laako
--
PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B 39DD A4DE 63EB C216 1E4B
GPG key fingerprint: 0D10 D6D5 9F14 1A88 BA7F 7F17 ED92 8E98 EB43 8990
Available at PGP keyservers
[-- Attachment #1.2: Forwarded message - Promise driver (pdc202xx) --]
[-- Type: message/rfc822, Size: 3798 bytes --]
[-- Attachment #1.2.1.1: Type: text/plain, Size: 2934 bytes --]
Hello,
Is it normal to have pdc202xx driver to enable only UDMA33 on Ultra133
TX2 (PDC20269)? Disk is new 60GB Seagate Barracuda. U133TX2's BIOS says
it has enabled UDMA5.
Driver is: ide-2.4.19-p7.all.convert.10.patch.bz2
Here's some info from dmesg:
PDC20269: chipset revision 2
PDC20269: not 100%% native mode: will probe irqs later
ide2: BM-DMA at 0x5800-0x5807, BIOS settings: hde:pio, hdf:pio
ide3: BM-DMA at 0x5808-0x580f, BIOS settings: hdg:pio, hdh:pio
hde: ST360021A, ATA DISK drive
hde: host protected area => 1
hde: 117231408 sectors (60022 MB) w/2048KiB Cache, CHS=116301/16/63,
UDMA(33)
/proc/pci/ide/pdc202xx says only (nothing else):
PDC20269 TX2 Chipset.
And from "lspci -vvvxxx":
00:0c.0 Unknown mass storage controller: Promise Technology, Inc.:
Unknown device 4d69 (rev 02) (prog-if 85)
Subsystem: Promise Technology, Inc.: Unknown device 4d68
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B- ParErr- DEVSEL=slow >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 32 (1000ns min, 4500ns max), cache line size 08
Interrupt: pin A routed to IRQ 11
Region 0: I/O ports at 7000 [size=8]
Region 1: I/O ports at 6800 [size=4]
Region 2: I/O ports at 6400 [size=8]
Region 3: I/O ports at 6000 [size=4]
Region 4: I/O ports at 5800 [size=16]
Region 5: Memory at e6000000 (32-bit, non-prefetchable)
[size=16K]
Expansion ROM at <unassigned> [disabled] [size=16K]
Capabilities: [60] Power Management version 1
Flags: PMEClk- DSI+ D1+ D2- AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
00: 5a 10 69 4d 07 00 30 04 02 85 80 01 08 20 00 00
10: 01 70 00 00 01 68 00 00 01 64 00 00 01 60 00 00
20: 01 58 00 00 00 00 00 e6 00 00 00 00 5a 10 68 4d
30: 00 00 00 00 60 00 00 00 00 00 00 00 0b 01 04 12
40: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
50: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
60: 01 00 21 02 00 00 00 00 00 00 00 00 00 00 00 00
70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
Best regards,
- Jussi Laako (IRC: SonarNerd)
--
PGP key fingerprint: 161D 6FED 6A92 39E2 EB5B 39DD A4DE 63EB C216 1E4B
GPG key fingerprint: 0D10 D6D5 9F14 1A88 BA7F 7F17 ED92 8E98 EB43 8990
Available at PGP keyservers
[-- Attachment #1.2.1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 240 bytes --]
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]
next reply other threads:[~2002-06-09 23:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-09 23:51 Jussi Laako [this message]
2002-06-10 0:42 ` Andrew D Kirch
2002-06-10 11:23 ` Tomas Szepe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1023666681.1163.4.camel@vaarlahti \
--to=jussi.laako@kolumbus.fi \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®