qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Simon Safar" via <qemu-devel@nongnu.org>
To: "Max Filippov" <jcmvbkbc@gmail.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [PATCH v2] target/xtensa: import core lx106
Date: Sun, 24 Apr 2022 22:23:31 -0700	[thread overview]
Message-ID: <6c1d04ae-bbe5-4847-a2e1-5c1786c916fd@www.fastmail.com> (raw)
In-Reply-To: <CAMo8BfL__NZDQGkTRUXSbaNRoQJ7QhGmvVFy5NDGhDH5eJbguw@mail.gmail.com>

Hi Max,

On Sat, Apr 23, 2022, at 2:41 PM, Max Filippov wrote:
> I've noticed that this file is not from the original overlay (which I happen
> to have here:
> https://github.com/jcmvbkbc/xtensa-toolchain-build/blob/master/overlays/original/lx106.tar.gz),
> but has been changed (by adding '& ~1' to the 7th column), probably
> to make some older gdb version work.
> This change is not needed for the modern gdb versions.
> I've reverted this change and checked that the mainline gdb-11.1
> built with the original overlay for the xtensa-elf target correctly
> interacts with the QEMU. Can you please confirm that?

for simplicity, I just tried re-importing everything with your overlay (vs. the one from xtensa); both actual code execution & gdb seems to be working nicely. Yours is also nicer since there is about zero mismatch between what import-core.sh expects & what it has access to (... while I had to tweak it a bit, e.g. to skip core-matmap.inc, for it to be satisfied with the xtensa version).

Should I send a v3 with the results from importing your variant of the overlay? (although at this point my "contribution" is really just reordering cores.list after running the script :))

Simon


  reply	other threads:[~2022-04-25 13:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-23  4:08 [PATCH v2] target/xtensa: import core lx106 Simon Safar via
2022-04-23 21:41 ` Max Filippov
2022-04-25  5:23   ` Simon Safar via [this message]
2022-04-25 10:52     ` Max Filippov

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=6c1d04ae-bbe5-4847-a2e1-5c1786c916fd@www.fastmail.com \
    --to=qemu-devel@nongnu.org \
    --cc=jcmvbkbc@gmail.com \
    --cc=simon@simonsafar.com \
    /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).