public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Lanttor <lanttor.guo@freescale.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: linux-m68k@vger.kernel.org,
	uClinux development list <uclinux-dev@uclinux.org>
Subject: Re: Interrupt issue on m68k platform and some fix
Date: Thu, 02 Jul 2009 18:06:44 +0800	[thread overview]
Message-ID: <4A4C86B4.2000101@freescale.com> (raw)
In-Reply-To: <m38wj7tpxk.fsf@hase.home>

>
> No.  Byte would be addqb.
I think you're right, I am not familiar coldfire assembly and
instruction. I just touched it no long time.

addqb instruction is not supported on coldfire platform.

Which better way to replace it? I tried to use addql, but it proves that
it's incorrect.

I guess my patch could be better way to replace it now.

Regards,
Lanttor




------------------------------------------------------------------------
*From:* Andreas Schwab <schwab@linux-m68k.org>
*Sent:* 07/02/2009 5:05:59 PM +0800
*To:* Lanttor <lanttor.guo@freescale.com>
*CC:* linux-m68k@vger.kernel.org, uClinux development list
<uclinux-dev@uclinux.org>
*Subject:* Interrupt issue on m68k platform and some fix

> Lanttor <lanttor.guo@freescale.com> writes:
>
>   
>> So this code sets value 1 to the second byte of preempt_count field.
>>     
>
> No.  Byte would be addqb.
>
> Andreas.
>
>   

  reply	other threads:[~2009-07-02 10:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-02  4:07 Interrupt issue on m68k platform and some fix Lanttor
2009-07-02  8:24 ` Andreas Schwab
2009-07-02  8:58   ` Lanttor
2009-07-02  9:05     ` Andreas Schwab
2009-07-02 10:06       ` Lanttor [this message]
2009-07-02 20:25       ` Roman Hodek
2009-07-03  3:18         ` Lanttor

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=4A4C86B4.2000101@freescale.com \
    --to=lanttor.guo@freescale.com \
    --cc=linux-m68k@vger.kernel.org \
    --cc=schwab@linux-m68k.org \
    --cc=uclinux-dev@uclinux.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