From: Ian Chilton <mailinglist@ichilton.co.uk>
To: Miloslaw Smyk <thorgal@wfmh.org.pl>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Anyone use HPT366 + UDMA in Linux?
Date: Fri, 15 Nov 2002 22:51:37 +0000 [thread overview]
Message-ID: <20021115225137.GB6625@buzz.ichilton.co.uk> (raw)
In-Reply-To: <3DD571F1.3010502@wfmh.org.pl>
Hello,
I booed 2.4.19 with HPT366 compiled in and i have not got it to fall
over yet :)
HPT366: onboard version of chipset, pin1=1 pin2=2
HPT366: IDE controller on PCI bus 00 dev 98
HPT366: chipset revision 1
HPT366: not 100% native mode: will probe irqs later
ide0: BM-DMA at 0xb400-0xb407, BIOS settings: hda:DMA, hdb:pio
HPT366: IDE controller on PCI bus 00 dev 99
HPT366: chipset revision 1
HPT366: not 100% native mode: will probe irqs later
ide1: BM-DMA at 0xc000-0xc007, BIOS settings: hdc:pio, hdd:pio
hda: IBM-DTLA-307045, ATA DISK drive
ide0 at 0xac00-0xac07,0xb002 on irq 15
hda: 90069840 sectors (46116 MB) w/1916KiB Cache, CHS=89355/16/63,
UDMA(44)
Partition check:
hda: [PTBL] [5606/255/63] hda1 hda3 hda4
[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 look normal?
Thanks!
Bye for Now,
Ian
\|||/
(o o)
/---------------------------ooO-(_)-Ooo---------------------------\
| Ian Chilton Web: http://www.ichilton.co.uk |
| E-Mail: ian@ichilton.co.uk Backup: ian@linuxfromscratch.org |
|-----------------------------------------------------------------|
| There are 10 types of people in the world: |
| Those who understand binary, and those who don't. |
\-----------------------------------------------------------------/
next prev parent reply other threads:[~2002-11-15 22:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-15 12:35 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 [this message]
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
2002-11-16 0:19 ` Kevin Krieser
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=20021115225137.GB6625@buzz.ichilton.co.uk \
--to=mailinglist@ichilton.co.uk \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ian@ichilton.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=thorgal@wfmh.org.pl \
/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®