From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: lm32 simulator configuration file question
Date: Sun, 05 Apr 2015 01:32:00 -0000 [thread overview]
Message-ID: <0D043000-66CE-41AE-A66A-6EC12FF8896E@oarcorp.com> (raw)
In-Reply-To: <20150405011520.GA16816@vapier>
On April 4, 2015 8:20:24 PM CDT, Mike Frysinger <vapier@gentoo.org> wrote:
>On 04 Apr 2015 19:27, Joel Sherrill wrote:
>> Once we get by this one, I noticed that the lm32timer only
>> lets you instance it once. The real board has two timers.
>> Is there an example of a device which can be instanced
>> multiple times?
>
>i glanced at the lm32timer device code and it looks correct to me --
>there is no
>global state (it's all attached to the instance via HW_ZALLOC (me,
>...), and all
>accesses go through the passed in "me" hw).
>
>why do you think it only lets you instantiate it once ?
When I configure two timers, it looks like the second address registration attempt is ignored based on the trace and faulting code. I can have timer 0 or 1 but not both. Two interrupt attaches seem to be honored.
I will finish putting together a kit for you tomorrow. The RTEMS tester framework uses the gdb/mi so I can automate runs of the rtems test suite. It was looking pretty good using gdb but something is wrong with run.
Enjoy your Saturday night and Easter Sunday. I will get the kit to you before I fly out Monday.
>-mike
--joel
next prev parent reply other threads:[~2015-04-05 1:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-02 22:19 Joel Sherrill
2015-04-03 1:41 ` Mike Frysinger
2015-04-03 20:21 ` Joel Sherrill
2015-04-03 23:21 ` Mike Frysinger
2015-04-04 0:00 ` Joel Sherrill
2015-04-04 2:57 ` Mike Frysinger
2015-04-04 13:49 ` Joel Sherrill
2015-04-04 21:08 ` Mike Frysinger
2015-04-05 0:27 ` Joel Sherrill
2015-04-05 1:20 ` Mike Frysinger
2015-04-05 1:32 ` Joel Sherrill [this message]
2015-04-05 2:05 ` Mike Frysinger
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=0D043000-66CE-41AE-A66A-6EC12FF8896E@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=gdb@sourceware.org \
--cc=vapier@gentoo.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).