qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Fabien Chouteau <chouteau@adacore.com>
To: Sebastian Huber <sebastian.huber@embedded-brains.de>
Cc: blauwirbel@gmail.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] SPARC: Add and use CPU_FEATURE_CASA
Date: Fri, 14 Feb 2014 14:44:38 +0100	[thread overview]
Message-ID: <52FE1DC6.10205@adacore.com> (raw)
In-Reply-To: <52FDD6C1.6050108@embedded-brains.de>

On 02/14/2014 09:41 AM, Sebastian Huber wrote:
> On 2014-02-13 16:50, Fabien Chouteau wrote:
>>
>> This ASI 0x80 is really defined nowhere in Leon3 not even in the sources :)
>> Maybe there's a bug in binutils... Did you try to run this program on a real board?
> 
> Yes, I tested it on a NGMP board with a LEON4 processor (documentation is the same for CAS as in LEON3).
> 

Alright so we can use the patch as is. 

> The ASI 0x80 is defined in the SPARC V9 manual, Table 12—Address Space Identifiers (ASIs).  Here we have:
> 
> 0x80, ASI_PRIMARY, Unrestricted access, Primary address space
> 
> So should I change it to use User Data Access?
> 

No I think supervisor data access closer to the definition in Leon3's doc.

  reply	other threads:[~2014-02-14 13:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-13  9:52 [Qemu-devel] [PATCH v2] SPARC: Add and use CPU_FEATURE_CASA Sebastian Huber
2014-02-13 12:01 ` Fabien Chouteau
2014-02-13 13:00   ` Sebastian Huber
2014-02-13 14:55     ` Fabien Chouteau
2014-02-13 15:50       ` Fabien Chouteau
2014-02-14  8:41         ` Sebastian Huber
2014-02-14 13:44           ` Fabien Chouteau [this message]
2014-02-14 13:55             ` Andreas Färber
  -- strict thread matches above, loose matches on Subject: below --
2013-11-26 14:04 [Qemu-devel] [PATCH] " Sebastian Huber
2013-11-28 10:27 ` [Qemu-devel] [PATCH v2] " Sebastian Huber
2013-12-10  8:09   ` Sebastian Huber
2013-12-10 17:16     ` Fabien Chouteau

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=52FE1DC6.10205@adacore.com \
    --to=chouteau@adacore.com \
    --cc=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=sebastian.huber@embedded-brains.de \
    /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).