mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andries Brouwer <aebr@win.tue.nl>
To: Andre Hedrick <andre@linux-ide.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
	Lionel Bergeret <lbergeret@swing.be>,
	JunHyeok Heo <jhheo@idis.co.kr>,
	Linux Kernel Development <linux-kernel@vger.kernel.org>,
	linux-ide@vger.kernel.org
Subject: Re: [PATCH] Bogus LBA48 drives
Date: Wed, 31 Mar 2004 20:34:10 +0200	[thread overview]
Message-ID: <20040331183410.GA3796@pclin040.win.tue.nl> (raw)
In-Reply-To: <Pine.LNX.4.10.10403300821520.11654-100000@master.linux-ide.org>

Geert Uytterhoeven wrote:

>> Apparently some IDE drives (e.g. a pile of 80 GB ST380020ACE drives I have
>> access to) advertise to support LBA48, but don't.
>> One problem with those drives is that the lba_capacity_2 field in their drive
>> identification is set to 0.


Andre Hedrick replies:

> Actually this issue an errata correction in ATA-6 and changed in ATA-7.
> 
> 48-bit command set support is different than capacity.


Hmm. I read in my copy of ATA7:

 6.16.55 Words (103:100): Maximum user LBA for 48-bit Address feature set
 Words (103:100) contain a value that is one greater than the maximum LBA
 in user accessable space when the 48-bit Addressing feature set is supported.
 The maximum value that shall be placed in this field is 0000FFFFFFFFFFFFh.
 Support of these words is mandatory if the 48-bit Address feature set is supported.

Do you read differently?

  parent reply	other threads:[~2004-03-31 18:34 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-30 15:22 Geert Uytterhoeven
2004-03-30 15:26 ` Geert Uytterhoeven
2004-03-30 15:28 ` Geert Uytterhoeven
2004-03-30 15:51 ` Bartlomiej Zolnierkiewicz
2004-03-30 16:38 ` Andre Hedrick
2004-03-30 16:50   ` Jeff Garzik
2004-03-31 18:34   ` Andries Brouwer [this message]
2004-03-31 18:58     ` Jeff Garzik
2004-04-01  9:06       ` Geert Uytterhoeven
2004-04-01 18:24         ` Jeff Garzik

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=20040331183410.GA3796@pclin040.win.tue.nl \
    --to=aebr@win.tue.nl \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=andre@linux-ide.org \
    --cc=geert@linux-m68k.org \
    --cc=jhheo@idis.co.kr \
    --cc=lbergeret@swing.be \
    --cc=linux-ide@vger.kernel.org \
    --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®