From: Thomas Huth <huth@tuxfamily.org>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>, qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Laurent Vivier" <laurent@vivier.eu>
Subject: Re: [Qemu-devel] [PATCH v2 3/4] m68k: Add NeXTcube machine
Date: Wed, 3 Jul 2019 19:00:14 +0200 [thread overview]
Message-ID: <6242593f-9472-8bc5-c65e-bea3aa0149c8@tuxfamily.org> (raw)
In-Reply-To: <9b4187dd-9079-b511-aea7-2b8c992a3067@posteo.de>
On 02/07/2019 19.43, Thomas Huth wrote:
> On 29/06/2019 14.26, Philippe Mathieu-Daudé wrote:
>> On 6/28/19 8:15 PM, Thomas Huth wrote:
[...]
>>> +static uint32_t mmio_readb(NeXTState *s, hwaddr addr)
>>> +{
>>> + switch (addr) {
>>> + case 0xc000:
>>> + return (s->scr1 >> 24) & 0xFF;
>>> + case 0xc001:
>>> + return (s->scr1 >> 16) & 0xFF;
>>> + case 0xc002:
>>> + return (s->scr1 >> 8) & 0xFF;
>>> + case 0xc003:
>>> + return (s->scr1 >> 0) & 0xFF;
>>
>> So you have a 32-bit implementation (DMA accessed device?).
>>
>> memory::access_with_adjusted_size() already does this work
>> for you if you use:
>>
>> .impl.min_access_size = 4,
>> .valid.min_access_size = 1,
>> .valid.max_access_size = 4,
>
> Yeah, it's old code from 2011 ... I'll try to rework it as you suggested.
That does not really seem to work. I'm then still seeing accesses to
0xc002 in my "readl" handler. Looks like access_with_adjusted_size() is
not really ready for that yet (see the FIXME in that function - it does
not take care of unaligned accesses yet).
Thomas
next prev parent reply other threads:[~2019-07-03 17:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 18:15 [Qemu-devel] [PATCH v2 0/4] m68k: Add basic support for the NeXTcube machine Thomas Huth
2019-06-28 18:15 ` [Qemu-devel] [PATCH v2 1/4] m68k: Add NeXTcube framebuffer device emulation Thomas Huth
2019-06-29 11:53 ` Philippe Mathieu-Daudé
2019-06-29 17:45 ` Thomas Huth
2019-07-02 16:01 ` Philippe Mathieu-Daudé
2019-06-28 18:15 ` [Qemu-devel] [PATCH v2 2/4] m68k: Add NeXTcube keyboard device Thomas Huth
2019-06-29 12:02 ` Philippe Mathieu-Daudé
2019-07-02 10:45 ` Thomas Huth
2019-06-28 18:15 ` [Qemu-devel] [PATCH v2 3/4] m68k: Add NeXTcube machine Thomas Huth
2019-06-29 12:26 ` Philippe Mathieu-Daudé
2019-06-29 12:36 ` Philippe Mathieu-Daudé
2019-07-02 17:43 ` Thomas Huth
2019-07-03 17:00 ` Thomas Huth [this message]
2019-07-03 17:36 ` Philippe Mathieu-Daudé
2019-06-28 18:15 ` [Qemu-devel] [PATCH v2 4/4] m68k: Add an entry for the NeXTcube machine to the MAINTAINERS file Thomas Huth
2019-06-29 12:27 ` Philippe Mathieu-Daudé
2019-06-29 14:40 ` [Qemu-devel] [PATCH v2 0/4] m68k: Add basic support for the NeXTcube machine Philippe Mathieu-Daudé
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=6242593f-9472-8bc5-c65e-bea3aa0149c8@tuxfamily.org \
--to=huth@tuxfamily.org \
--cc=f4bug@amsat.org \
--cc=laurent@vivier.eu \
--cc=peter.maydell@linaro.org \
--cc=philmd@redhat.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).