From: Francesco VIRLINZI <francesco.virlinzi@st.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH][RFC] sh: suspend interpreter V1
Date: Tue, 24 Mar 2009 13:41:10 +0000 [thread overview]
Message-ID: <49C8E2F6.3080703@st.com> (raw)
In-Reply-To: <20090323091739.25647.6773.sendpatchset@rx1.opensource.se>
Hi Magnus
> Right, I understand. This becomes a bit more complicated but it's not
> so strange. As long as the two pass setup() is ok (first pass without
> buffer) then I'm ok.
>
> But do we (you!) really need to jump forward?
>
Not really but I'd like to have no constraint if possible
>
>> And with an ADD or a SUB instruction also some delay can be built on top of
>> these instructions.
>>
>
> The opcode SH_PM_OP_ADD_IMM_R0 isn't enough?
>
Yes I think so.
Have you time to extend your code or is it ok for you if I do the
required update?
Regards
Francesco
next prev parent reply other threads:[~2009-03-24 13:41 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 9:17 [PATCH][RFC] sh: suspend interpreter V1 Magnus Damm
2009-03-23 15:35 ` Francesco VIRLINZI
2009-03-24 7:00 ` Francesco VIRLINZI
2009-03-24 11:08 ` Magnus Damm
2009-03-24 13:41 ` Francesco VIRLINZI [this message]
2009-03-25 10:10 ` Magnus Damm
2009-03-25 14:46 ` takasi-y
2009-03-30 2:45 ` Magnus Damm
2009-03-30 7:02 ` Francesco VIRLINZI
2009-03-31 8:42 ` Paul Mundt
2009-04-15 11:15 ` Magnus Damm
2009-04-15 11:23 ` Paul Mundt
2009-04-16 14:15 ` Francesco VIRLINZI
2009-04-16 14:22 ` Francesco VIRLINZI
2009-04-17 2:07 ` Magnus Damm
2009-04-17 6:44 ` Francesco VIRLINZI
2009-04-17 10:39 ` Magnus Damm
2009-04-17 12:00 ` Francesco VIRLINZI
2009-04-17 21:38 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-20 10:26 ` Magnus Damm
2009-04-20 12:27 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-20 12:33 ` Francesco VIRLINZI
2009-04-20 12:55 ` Francesco VIRLINZI
2009-04-20 13:03 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-20 13:15 ` Jean-Christophe PLAGNIOL-VILLARD
2009-04-20 13:30 ` Michael Trimarchi
2009-04-21 7:17 ` Francesco VIRLINZI
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=49C8E2F6.3080703@st.com \
--to=francesco.virlinzi@st.com \
--cc=linux-sh@vger.kernel.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