public inbox for ecos-patches@sourceware.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001716] MIPS malta + sead3 update
Date: Mon, 03 Jun 2013 13:43:00 -0000	[thread overview]
Message-ID: <bug-1001716-104-DDnqWQdwmx@http.bugs.ecos.sourceware.org/> (raw)
In-Reply-To: <bug-1001716-104@http.bugs.ecos.sourceware.org/>

Please do not reply to this email, use the link below.

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001716

--- Comment #6 from John Dallaway <john@dallaway.org.uk> ---
Charles

You wrote:

> - Retain compatibility with QEMU's malta emulator
> - Verified to still work with mipsisa32-elf-gcc toolchain (eCosCentric GNU
> tools 4.3.2-sw)

I've been experimenting with your latest patch (Attempt-2-20121225) using the
above mipsisa32-elf toolchain and Qemu 1.5.0 (qemu-system-mipsel). I am using
target "malta_mips32_4kc" with the "default" template, importing
mipsisa32-elf-malta_qemu.ecm and then setting CYG_HAL_STARTUP == "ROM".

I can run simple eCos tests such as the bin_sem0 kernel test and see the test
output in the console, but most tests are hanging when the scheduler starts.

Can you let me know which version of Qemu you are using and how you configured
eCos for correct operation with mipsisa32-elf tools and Qemu?

Many thanks

John Dallaway

-- 
You are receiving this mail because:
You are on the CC list for the bug.

      parent reply	other threads:[~2013-06-03 13:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-13  8:06 [Bug 1001716] New: " bugzilla-daemon
2012-12-13 16:06 ` [Bug 1001716] " bugzilla-daemon
2012-12-13 16:14 ` bugzilla-daemon
2012-12-13 16:14 ` bugzilla-daemon
2012-12-13 17:15 ` bugzilla-daemon
2012-12-25  7:44 ` bugzilla-daemon
2013-06-03 13:43 ` bugzilla-daemon [this message]

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=bug-1001716-104-DDnqWQdwmx@http.bugs.ecos.sourceware.org/ \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-patches@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).