linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Steve Rossi <srossi@ccrl.mot.com>
To: Jason Wohlgemuth <jsw-embedded@mindspring.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: QSPAN PCI wierdness
Date: Thu, 20 Apr 2000 19:35:48 -0500	[thread overview]
Message-ID: <38FFA264.4D436FB@ccrl.mot.com> (raw)
In-Reply-To: NCBBKJKKGDLPHKDPAFFMOECDCEAA.jsw-embedded@mindspring.com


That would be it. Thank you. I gues I've failed the #1 rule - always
check the archives first. In fact come to think of it, I saw your
posting the first time and I think I saved it away in a safe place so that
I could come back to it later. Duh!

Steve

Jason Wohlgemuth wrote:

>
> It seems that in the inline-assembly in qspan_pci.c the compiler doesn't
> recognize that the first argument to the assembly may be modified.  This
> resulted in a register getting trashed where it shouldn't have.  To fix the
> problem I modified the in-line assembly to tell the compiler that this
> register has been changed.
>
> 86c86
> <               : "=r"(x) : "r"(addr) : "%0")
> ---
> >               : "=r"(x) : "r"(addr))
>
> Jason <jwohlgem@mindspring.com>

--
-------------------------------------------------------
Steven K. Rossi                     srossi@ccrl.mot.com
Staff Engineer
Multimedia Communications Research Laboratory
Motorola Labs
-------------------------------------------------------


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2000-04-21  0:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-04-20 21:56 QSPAN PCI wierdness Steve Rossi
2000-04-20 21:35 ` Gabriel Paubert
2000-04-20 23:41   ` Steve Rossi
2000-04-20 23:02     ` Dan Malek
2000-04-20 23:09     ` Jason Wohlgemuth
2000-04-21  0:35       ` Steve Rossi [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=38FFA264.4D436FB@ccrl.mot.com \
    --to=srossi@ccrl.mot.com \
    --cc=jsw-embedded@mindspring.com \
    --cc=linuxppc-embedded@lists.linuxppc.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 NNTP newsgroup(s).