linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Steven Scholz <steven.scholz@imc-berlin.de>
Cc: "Eric D. Mudama" <edmudama@gmail.com>, linux-ide@vger.kernel.org
Subject: Re: HPA and failed opcode was: 0x37 ?
Date: Wed, 31 Jan 2007 15:54:10 +0300	[thread overview]
Message-ID: <45C09172.1030304@ru.mvista.com> (raw)
In-Reply-To: <45C0536F.5020005@imc-berlin.de>

Hello.

Steven Scholz wrote:

>>Maybe the FPGA is discarding the taskfile writes once the HOB bit is
>>set?  It wouldn't affect the READ NATIVE MAX ADDRESS EXT command being
>>issued since the only the command register matters for that, but it
>>would affect SET MAX ADDRESS EXT working properly.

>>Without a device > 137GB to test with, and without errors on the
>>device, you might not see any odd behavior in normal usage.

>>It's *really* unlikely the drive doesn't have a working taskfile.

> I am sorry. But I don't understand what a "working taskfile" means.
> I don't have CONFIG_IDE_TASK_IOCTL enabled if that means anything.

> The FPGA does nothing except decoding adresseses from the ARM cpu,
> controlling the A[2..0], CS[1..0], IOR, IOW lines of the HDD.

    I've not seen you quoting the code that sets ofsset for the 
IDE_CONTROL_REG, BTW... Without this register, LBA48 is completely broken

> In linux all I do is setting up some hw_regs_t struct (with hw.io_ports[])
> according to my memory map and call ide_register_hw() ...

> So looks like I need to find out more about that taskfile stuff.

    Taskfile is another (and probably an older one) anme for the IDE command 
block registers.

> Steven

MBR, Sergei

  reply	other threads:[~2007-01-31 12:54 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
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 [this message]
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=45C09172.1030304@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=edmudama@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=steven.scholz@imc-berlin.de \
    /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).