From: Steven Scholz <steven.scholz@imc-berlin.de>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
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 14:38:53 +0100 [thread overview]
Message-ID: <45C09BED.2040500@imc-berlin.de> (raw)
In-Reply-To: <45C095B9.30504@ru.mvista.com>
Hi,
>> for (i = IDE_DATA_OFFSET; i <= IDE_STATUS_OFFSET; i++) {
>> hw.io_ports[i] = ide_virt_base + (i << 1);
>> }
>
>> hw.io_ports[IDE_CONTROL_OFFSET] = ide_virt_base + 0x10;
>
>> Thus it has an offset 0x10 from the base address.
>
>> ide0 at 0xc3856000-0xc3856007,0xc3856010 on irq 27
>
>> But I just noticed that A[2..0] should look like "110" when accessing the
>> "Device Control Register". Thus the offset should be 0x16 instead! Right?
>
> If your FPGA passes A[2..0] untouched to the IDE bus, it's certainly
> wrong. It must pass 110.
Stupid me. As I mentioned earlier CPU's A[3..1] are connected to HDD's
A[2..0]. And CPU's A4 is used for HDD's CS1 (inverted of course). Thus the
offset for IDE_CONTROL_OFFSET must be 0x1C (=0x10 + 0x6 << 1).
And volá
ide0 at 0xc3856000-0xc3856007,0xc385601c on irq 27
hda: max request size: 1024KiB
idedisk_supports_hpa(): cfs_enable_1=346b, cfs_enable_1=3469
idedisk_read_native_max_address_ext(): addr = 000004a852ff
idedisk_read_native_max_address_ext(): addr = 000004a852ff
idedisk_read_native_max_address_ext(): addr = 000004a85300
idedisk_read_native_max_address_ext(): addr = 000004a85300
hda: 78140160 sectors (40007 MB) w/8192KiB Cache, CHS=16383/255/63
hda: cache flushes supported
hda: hda1
idedisk_read_native_max_address_ext() works now. No HPA reported anymore!
Thanks a million to everyone!!!!
PS: Still I don't know why ARM reports "max request size: 1024KiB" and y86
reports only "max request size: 512KiB" ...
Steven
next prev parent reply other threads:[~2007-01-31 13:38 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
2007-01-31 13:08 ` Steven Scholz
2007-01-31 13:12 ` Sergei Shtylyov
2007-01-31 13:38 ` Steven Scholz [this message]
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=45C09BED.2040500@imc-berlin.de \
--to=steven.scholz@imc-berlin.de \
--cc=edmudama@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=sshtylyov@ru.mvista.com \
/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.