From: Jimi Xenidis <jimix@watson.ibm.com>
To: Simon Vallet <svallet@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: atomic_clear_mask() on PPC ?
Date: Fri, 15 Dec 2006 09:08:19 -0500 [thread overview]
Message-ID: <37F182F3-71D2-4A8C-84B0-A036684B447B@watson.ibm.com> (raw)
In-Reply-To: <6473fb3e0612150325w3c6f01b0rdd4953dc9cb6430e@mail.gmail.com>
powerpc 32-bit seems to have it:
arch/powerpc/kernel/misc_32.S _GLOBAL 742 _GLOBAL(atomic_clear_mask)
Assuming its the "thing" you actually want, since atomic_t is always
an int, the exact same code sequence will be fine under 64bit, I
guess PPc64 never needed it?
Perhaps we should move it to misc.S?
-JX
On Dec 15, 2006, at 6:25 AM, Simon Vallet wrote:
> Hi,
>
> I'm currently trying to "port" a binary-only driver to Linux/PPC :
> the card manufacturer
> provides MacOS X and Linux/i386 drivers, providing *some* sources
> with the Linux driver.
>
> The plan is to use the provided sources, and to get the remaining
> symbols & code from the MacOSX
> object -- Unfortunately, one of those components makes a call to
> atomic_clear_mask(), which doesn't
> seem available on PPC yet.
>
> So the question is : is there a workaround for this, and if not,
> how would you implement this call
> (I have absolutely no knowledge of PPC assembly). Quickly grepping
> through kernel headers reveals it
> is present for i386, arm and x86_64, but not sparc or ppc. Is there
> a reason for this ?
>
> Simon
>
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
next prev parent reply other threads:[~2006-12-15 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 11:25 atomic_clear_mask() on PPC ? Simon Vallet
2006-12-15 14:08 ` Jimi Xenidis [this message]
2006-12-15 19:58 ` Simon Vallet
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=37F182F3-71D2-4A8C-84B0-A036684B447B@watson.ibm.com \
--to=jimix@watson.ibm.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=svallet@gmail.com \
/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).