qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Daniel Verkamp <daniel@drv.nu>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ahci: add port I/O index-data pair
Date: Wed, 21 Sep 2011 14:34:41 +0200	[thread overview]
Message-ID: <4E79D9E1.4060602@redhat.com> (raw)
In-Reply-To: <1314436348-28837-1-git-send-email-daniel@drv.nu>

Am 27.08.2011 11:12, schrieb Daniel Verkamp:
> Implement an I/O space index-data register pair as defined by the AHCI
> spec, including the corresponding SATA PCI capability and BAR.
> 
> This allows real-mode code to access the AHCI registers; real-mode
> code cannot address the memory-mapped register space because it is
> beyond the first megabyte.
> 
> Signed-off-by: Daniel Verkamp <daniel@drv.nu>

Thanks, applied to the block branch.

> --- a/hw/ide/ich.c
> +++ b/hw/ide/ich.c
> @@ -72,6 +72,14 @@
>  #include <hw/ide/pci.h>
>  #include <hw/ide/ahci.h>
>  
> +#define ICH9_SATA_CAP_OFFSET    0xA8
> +
> +#define ICH9_IDP_BAR            4
> +#define ICH9_MEM_BAR            5
> +
> +#define ICH9_IDP_INDEX          0x10
> +#define ICH9_IDP_INDEX_LOG2     0x04

Just wondering, why did you choose 0x10 and not 0? The spec reads as if
the implementation could freely choose this, and I can't see what the
first 16 Bytes are used for.

Doesn't make it less correct, of course.

Kevin

  parent reply	other threads:[~2011-09-21 12:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-27  9:12 [Qemu-devel] [PATCH] ahci: add port I/O index-data pair Daniel Verkamp
2011-08-28 18:48 ` Alexander Graf
2011-08-30  3:07   ` Daniel Verkamp
2011-09-01 14:58     ` Alexander Graf
2011-09-08  7:33       ` Daniel Verkamp
2011-09-20 13:39   ` Kevin Wolf
2011-09-20 14:02     ` Alexander Graf
2011-09-21 12:34 ` Kevin Wolf [this message]
2011-09-21 12:57   ` Kevin Wolf

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=4E79D9E1.4060602@redhat.com \
    --to=kwolf@redhat.com \
    --cc=daniel@drv.nu \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).