From: David Balazic <david.balazic@uni-mb.si>
To: linux-kernel@vger.kernel.org
Subject: weird /proc/ide/hdx/settings
Date: Fri, 23 Feb 2001 15:02:37 +0100 [thread overview]
Message-ID: <3A966D7D.550A631B@uni-mb.si> (raw)
Running kernel 2.4.2 :
cat /proc/ide/hdc/settings
name value min max mode
---- ----- --- --- ----
bios_cyl 89355 0 65535 rw
bios_head 16 0 255 rw
bios_sect 63 0 63 rw
breada_readahead 4 0 127 rw
bswap 0 0 1 r
current_speed 69 0 69 rw
file_readahead 0 0 2097151 rw
ide_scsi 0 0 1 rw
init_speed 12 0 69 rw
io_32bit 1 0 3 rw
keepsettings 0 0 1 rw
lun 0 0 7 rw
max_kb_per_request 128 1 127 rw
multcount 0 0 8 rw
nice1 1 0 1 rw
nowerr 0 0 1 rw
number 2 0 3 rw
pio_mode write-only 0 255 w
slow 0 0 1 rw
unmaskirq 1 0 1 rw
using_dma
--------------------%X---------------
max_kb_per_request has value 128 , but max is 127 !?
max for multcount is 8 , but my drive supports 16 sectors. ( see hdparm output below )
If I set multcount to 8 sectors ( hdparm -m 8 /dev/hdc )
then /proc/ide/hdc/settings will show :
multcount 4 0 8 rw
The values are divided by 2. Why ?
hdparm -i /dev/hdc :
/dev/hdc:
Model=IBM-DTLA-307045, FwRev=TX6OA60A, SerialNo=YMEYMML9342
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=off
CurCHS=16383/16/63, CurSects=-66060037, 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 udma0 udma1 udma2 udma3 udma4 *udma5
IDE interface is VIA xxx686b ( ATA-100 )
IDE driver is VIA IDE v4.3
--
David Balazic
--------------
"Be excellent to each other." - Bill & Ted
- - - - - - - - - - - - - - - - - - - - - -
next reply other threads:[~2001-02-23 14:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-23 14:02 David Balazic [this message]
2001-02-25 5:10 ` weird /proc/ide/hdx/settings Andre Hedrick
2001-02-26 19:29 ` David Balazic
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=3A966D7D.550A631B@uni-mb.si \
--to=david.balazic@uni-mb.si \
--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;
as well as URLs for NNTP newsgroup(s).