All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Scholz <steven.scholz@imc-berlin.de>
To: Alan <alan@lxorguk.ukuu.org.uk>
Cc: linux-ide@vger.kernel.org
Subject: Re: HPA and failed opcode was: 0x37 ?
Date: Tue, 30 Jan 2007 17:46:16 +0100	[thread overview]
Message-ID: <45BF7658.1090204@imc-berlin.de> (raw)
In-Reply-To: <20070130164401.295f9913@localhost.localdomain>

Alan,

>> hda: Host Protected Area detected.
>>         current capacity is 78140160 sectors (40007 MB)
>>         native  capacity is 185074430006016 sectors (94758108163 MB)
> 
> This comes from the identify data (bit 10 of the
> cfs_enable_1/command_set_1 fields in drivers ide) indicate the drive has
> an HPA so we try and read it. As there is no error report it seems the
> drive replied fine and we turn it into a rather bizarre value, but all our
> endian and the like code appears correct here.
> 
> Is your IDE controller LBA48 capable ?

Well TBH I have no contoller. As I said I am using an embedded ARM board.
The HDD is connected via a FPGA. The internal HDD registers simply memory
mapped. Works fine. Usually. By now we seem to have trouble with that
Seagate drive...

So I don't see any problems with LBA48 ...

>> hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
>> hda: task_no_data_intr: error=0x04 { DriveStatusError }
>> ide: failed opcode was: 0x37
> 
> We try and set the disk size to 185074430006016 sectors.. it objects
> unsuprisingly to this proposal.
;-)

Steven

  reply	other threads:[~2007-01-30 16:46 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-30 14:02 HPA and failed opcode was: 0x37 ? Steven Scholz
2007-01-30 14:07 ` Steven Scholz
2007-01-30 15:44   ` Eric D. Mudama
2007-01-30 15:50     ` Eric D. Mudama
2007-01-30 15:54       ` Steven Scholz
2007-01-30 15:53     ` Steven Scholz
2007-01-30 16:44 ` Alan
2007-01-30 16:46   ` Steven Scholz [this message]
2007-01-30 17:26     ` Alan
2007-01-30 17:19       ` Steven Scholz
2007-01-30 18:07         ` Alan
2007-01-30 18:04           ` Steven Scholz
2007-01-30 18:23             ` Eric D. Mudama
2007-01-30 18:32             ` Sergei Shtylyov
2007-01-30 19:56               ` Eric D. Mudama
2007-01-30 20:01                 ` Eric D. Mudama
2007-01-31  8:29                 ` Steven Scholz
2007-01-31 12:54                   ` Sergei Shtylyov
2007-01-31 13:08                     ` Steven Scholz
2007-01-31 13:12                       ` Sergei Shtylyov
2007-01-31 13:38                         ` Steven Scholz
2007-01-31  9:51               ` Steven Scholz
2007-01-31 12:50                 ` Sergei Shtylyov
2007-01-31 13:04                   ` Steven Scholz
2007-01-31 13:33                     ` Alan
2007-01-31 13:26                       ` Steven Scholz

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=45BF7658.1090204@imc-berlin.de \
    --to=steven.scholz@imc-berlin.de \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-ide@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.