From: Greg Ungerer <gerg@uclinux.org>
To: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 1/3] m68k: implmenent more ColdFire 5208 interrupt controller functionality
Date: Fri, 19 Jun 2015 16:04:36 +1000 [thread overview]
Message-ID: <5583B0F4.80906@uclinux.org> (raw)
In-Reply-To: <CAEgOgz5KQkMznKg_qBzNVsgj=uAOeV2M941GZZq5qT=ATMokbw@mail.gmail.com>
Hi Peter,
On 19/06/15 15:24, Peter Crosthwaite wrote:
> On Mon, Aug 18, 2014 at 10:37 PM, <gerg@uclinux.org> wrote:
>> From: Greg Ungerer <gerg@uclinux.org>
>>
>> Implement the SIMR and CIMR registers of the 5208 interrupt controller.
>> These are used by modern versions of Linux running on ColdFire (not sure
>> of the exact version they were introduced, but they have been in for quite
>> a while now).
>>
>> Without this change when attempting to run a linux-3.5 kernel you will
>> see:
>>
>> qemu: hardware error: mcf_intc_write: Bad write offset 28
>>
>> and execution will stop and dump out.
>>
>> Signed-off-by: Greg Ungerer <gerg@uclinux.org>
>> ---
>> hw/m68k/mcf_intc.c | 14 ++++++++++++++
>> 1 file changed, 14 insertions(+)
>>
>> diff --git a/hw/m68k/mcf_intc.c b/hw/m68k/mcf_intc.c
>> index 621423c..37a9de0 100644
>> --- a/hw/m68k/mcf_intc.c
>> +++ b/hw/m68k/mcf_intc.c
>> @@ -102,6 +102,20 @@ static void mcf_intc_write(void *opaque, hwaddr addr,
>> case 0x0c:
>> s->imr = (s->imr & 0xffffffff00000000ull) | (uint32_t)val;
>> break;
>> + case 0x1c:
>> + if (val & 0x40) {
>> + s->imr = 0xffffffffffffffffull;
>
> ~0ull.
>
> Otherwise,
>
> Reviewed-by: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Thanks, I'll change that and add the reviewed-by.
> This introduces magic numbers which is generally discouraged, by this
> device has no macrofication at all so I guess it should be cleaned up
> at some stage.
Agreed. I stuck to the existing style in this case.
Regards
Greg
>> + } else {
>> + s->imr |= (0x1ull << (val & 0x3f));
>> + }
>> + break;
>> + case 0x1d:
>> + if (val & 0x40) {
>> + s->imr = 0ull;
>> + } else {
>> + s->imr &= ~(0x1ull << (val & 0x3f));
>> + }
>> + break;
>> default:
>> hw_error("mcf_intc_write: Bad write offset %d\n", offset);
>> break;
>> --
>> 1.9.1
>>
>>
>
next prev parent reply other threads:[~2015-06-19 6:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 5:37 [Qemu-devel] [PATCH 0/3] m68k: fix coldfire linux problems gerg
2014-08-19 5:37 ` [Qemu-devel] [PATCH 1/3] m68k: implmenent more ColdFire 5208 interrupt controller functionality gerg
2015-06-19 5:24 ` Peter Crosthwaite
2015-06-19 6:04 ` Greg Ungerer [this message]
2014-08-19 5:37 ` [Qemu-devel] [PATCH 2/3] m68k: implement move to/from usp register instruction gerg
2014-08-19 5:37 ` [Qemu-devel] [PATCH 3/3] m68k: fix usp processing on interrupt entry and exception exit gerg
2015-06-19 5:49 ` Peter Crosthwaite
2015-06-19 6:49 ` Greg Ungerer
2015-06-19 6:51 ` Peter Crosthwaite
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=5583B0F4.80906@uclinux.org \
--to=gerg@uclinux.org \
--cc=peter.crosthwaite@xilinx.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 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.