From: Samuel Flory <sflory@rackable.com>
To: Ian Chilton <ian@ichilton.co.uk>
Cc: Leopold Gouverneur <lgouv@pi.be>, linux-kernel@vger.kernel.org
Subject: Re: Anyone use HPT366 + UDMA in Linux?
Date: Fri, 15 Nov 2002 11:15:25 -0800 [thread overview]
Message-ID: <3DD547CD.8000307@rackable.com> (raw)
In-Reply-To: 20021115183407.GA32543@buzz.ichilton.co.uk
Ian Chilton wrote:
>[root@buzz:~/hdparm-5.2]# ./hdparm -i /dev/hda
>
>/dev/hda:
>
> Model=IBM-DTLA-307045, FwRev=TX6OA5AA, SerialNo=YZDYZNM1366
> Config={ HardSect NotMFM HdSw>15uSec Fixed DTR>10Mbs }
> RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=40
> BuffType=DualPortCache, BuffSize=1916kB, MaxMultSect=16, MultSect=16
> CurCHS=65535/1/63, CurSects=4128705, LBA=yes, LBAsects=90069840
> IORDY=on/off, tPIO={min:240,w/IORDY:120}, tDMA={min:120,rec:120}
> PIO modes: pio0 pio1 pio2 pio3 pio4
> DMA modes: mdma0 mdma1 mdma2
> UDMA modes: udma0 udma1 udma2 *udma3 udma4 udma5
> AdvancedPM=yes: disabled (255) WriteCache=enabled
> Drive conforms to: ATA/ATAPI-5 T13 1321D revision 1: 2 3 4 5
>
>
>Does this mean it's already using udma3?
>
>
>
>
Yes. hdparm -X 69 /dev/hda attempt to enable udma5, but may crash
your system. hdparm -X 67 /dev/hda should revert things. Be carefull.
next prev parent reply other threads:[~2002-11-15 19:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-15 12:35 Anyone use HPT366 + UDMA in Linux? Ian Chilton
2002-11-15 14:39 ` Alan Cox
2002-11-15 18:42 ` Ian Chilton
2002-11-15 19:10 ` Samuel Flory
2002-11-15 22:44 ` Ian Chilton
2002-11-15 22:15 ` Miloslaw Smyk
2002-11-15 22:51 ` Ian Chilton
2002-11-15 23:29 ` Miloslaw Smyk
2002-11-16 11:18 ` Zdenek SUTR Kaminski
2002-11-15 16:27 ` Leopold Gouverneur
2002-11-15 16:28 ` Ian Chilton
[not found] ` <20021115173120.GA1152@gouv>
2002-11-15 18:34 ` Ian Chilton
2002-11-15 19:15 ` Samuel Flory [this message]
2002-11-16 0:19 ` Kevin Krieser
-- strict thread matches above, loose matches on Subject: below --
2002-11-15 21:04 Ian Castle
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=3DD547CD.8000307@rackable.com \
--to=sflory@rackable.com \
--cc=ian@ichilton.co.uk \
--cc=lgouv@pi.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.