From: Flavio Bruno Leitner <fbl@conectiva.com.br>
To: linux-kernel@vger.kernel.org
Subject: IDE disk information changed from 2.4 to 2.6
Date: Wed, 5 Nov 2003 15:23:10 -0200 [thread overview]
Message-ID: <20031105172310.GE5304@conectiva.com.br> (raw)
Upgrading from kernel 2.4 to 2.6 the CHS information for the same hardware
changed. This behaviour is correct?
Using 2.4:
hda: 12594960 sectors (6449 MB) w/2048KiB Cache, CHS=784/255/63, UDMA (33)
Using 2.6:
hda: 12594960 sectors (6449 MB) w/2048KiB Cache, CHS=13328/15/63, UDMA (33)
regards,
--
Flávio Bruno Leitner <fbl@conectiva.com.br>
[ E74B 0BD0 5E05 C385 239E 531C BC17 D670 7FF0 A9E0 ]
next reply other threads:[~2003-11-05 17:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-05 17:23 Flavio Bruno Leitner [this message]
2003-11-05 17:29 ` IDE disk information changed from 2.4 to 2.6 Bartlomiej Zolnierkiewicz
2003-11-05 17:57 ` Flavio Bruno Leitner
2003-11-11 11:46 ` Andries Brouwer
2003-11-11 12:13 ` Flavio Bruno Leitner
2003-11-11 16:21 ` bill davidsen
[not found] <20031105184203.GG5304@conectiva.com.br>
2003-11-05 19:41 ` Bartlomiej Zolnierkiewicz
2003-11-11 11:53 ` Andries Brouwer
2003-11-11 18:29 ` Bartlomiej Zolnierkiewicz
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=20031105172310.GE5304@conectiva.com.br \
--to=fbl@conectiva.com.br \
--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