qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Hervé Poussineau" <hpoussin@reactos.org>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: qemu-devel@nongnu.org, Leon Alrae <leon.alrae@imgtec.com>
Subject: Re: [Qemu-devel] [PATCH] gt64xxx: access right I/O port when activating byte swapping
Date: Sat, 18 Jun 2016 22:48:34 +0200	[thread overview]
Message-ID: <12a1396e-6454-cda7-675d-163748e5a3d0@reactos.org> (raw)
In-Reply-To: <20160520195604.GA19765@aurel32.net>

Hi Aurélien,

Le 20/05/2016 à 21:56, Aurelien Jarno a écrit :
> On 2016-05-20 15:05, Hervé Poussineau wrote:
>> Incidentally, this fixes YAMON on big endian guest.
>>
>> Signed-off-by: Hervé Poussineau <hpoussin@reactos.org>
>> ---
>>  hw/mips/gt64xxx_pci.c | 62 +++++++++++++++++++++++++++++++++++++++++++++++++--
>>  1 file changed, 60 insertions(+), 2 deletions(-)
>>
>> diff --git a/hw/mips/gt64xxx_pci.c b/hw/mips/gt64xxx_pci.c
>> index 3f4523d..c76ee88 100644
>> --- a/hw/mips/gt64xxx_pci.c
>> +++ b/hw/mips/gt64xxx_pci.c
>> @@ -177,6 +177,7 @@
>>
>>  /* PCI Internal */
>>  #define GT_PCI0_CMD    		(0xc00 >> 2)
>> +#define   GT_CMD_MWORDSWAP      (1 << 10)
>>  #define GT_PCI0_TOR    		(0xc04 >> 2)
>>  #define GT_PCI0_BS_SCS10    	(0xc08 >> 2)
>>  #define GT_PCI0_BS_SCS32    	(0xc0c >> 2)
>> @@ -294,6 +295,62 @@ static void gt64120_isd_mapping(GT64120State *s)
>>      memory_region_add_subregion(get_system_memory(), s->ISD_start, &s->ISD_mem);
>>  }
>>
>> +static uint64_t gt64120_pci_io_read(void *opaque, hwaddr addr,
>> +                                    unsigned int size)
>> +{
>> +    GT64120State *s = opaque;
>> +    uint8_t buf[4];
>> +
>> +    if (s->regs[GT_PCI0_CMD] & GT_CMD_MWORDSWAP) {
>
> First of all, it should be noted that this bit doesn't control byte
> swapping, but swaps the 2 4-byte words in a 8-byte word.
>
>> +        addr = (addr & ~3) + 4 - size - (addr & 3);
>
> This looks complicated, and I don't think it is correct. In addition
> this doesn't behave correctly at the edges of the address space. For
> example a 2 byte access at address 0x3 would access address
> 0xffffffffffffffff.
>
> For sizes <= 4, swapping the 2 words should be done with addr ^= 4.
> Maybe you should also check for MBYTESWAP which also swaps the bytes
> within a 8-byte word.

The real word problem (ie the one from Yamon) is:
In LE Yamon, there is a read a 0x4d1 (len = 1). MWORDSWAP and MBYTESWAP are disabled
In BE Yamon, the same read is at address 0x4d2. MWORDSWAP is enabled while MBYTESWAP is disabled.

MWORDSWAP documentation is:
"The GT-64120 PCI master swaps the words of the incoming and outgoing PCI data (swap the 2 words of a long word)"

Do we have to ignore it, as QEMU only handles 4-bytes accesses?

Then, how to change this address 0x4d2 to 0x4d1, address where is located the i8259 ELCR register?
Next accesses are for the RTC, at address 0x72 in BE and address 0x71 in LE.
I think I'm missing something.

>
>> +    }
>> +
>> +    address_space_read(&address_space_io, addr, MEMTXATTRS_UNSPECIFIED,
>> +                       buf, size);
>> +
>> +    if (size == 1) {
>> +        return buf[0];
>> +    } else if (size == 2) {
>> +        return lduw_le_p(buf);
>> +    } else if (size == 4) {
>> +        return ldl_le_p(buf);
>> +    } else {
>> +        g_assert_not_reached();
>> +    }
>
> The device is configured is little endian, and then the little endian
> value converted into native endianness. Wouldn't it be simple to declare
> it as DEVICE_NATIVE_ENDIAN?

OK for this part, DEVICE_NATIVE_ENDIAN is indeed better and simplifies code.

Hervé

  reply	other threads:[~2016-06-18 20:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-20 13:05 [Qemu-devel] [PATCH] gt64xxx: access right I/O port when activating byte swapping Hervé Poussineau
2016-05-20 19:56 ` Aurelien Jarno
2016-06-18 20:48   ` Hervé Poussineau [this message]
2016-07-22 13:55     ` Aurelien Jarno
  -- strict thread matches above, loose matches on Subject: below --
2015-06-10 20:03 Hervé Poussineau

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=12a1396e-6454-cda7-675d-163748e5a3d0@reactos.org \
    --to=hpoussin@reactos.org \
    --cc=aurelien@aurel32.net \
    --cc=leon.alrae@imgtec.com \
    --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).