From: Yasushi SHOJI <yashi@atmark-techno.com>
To: linuxppc-dev@ozlabs.org
Subject: where should readb based/platform specific memcpy_fromio() be?
Date: Sat, 01 Oct 2005 05:02:17 +0900 [thread overview]
Message-ID: <87irwifho6.wl@mail2.atmark-techno.com> (raw)
Hello,
I'd like to add a variant of memcpy_fromio() for 16bit bus. In-tree
implementations seem to me that most, if not all, arch have either
readb() or memcpy() based mempy_fromio.
powerpc doesn't currently have readb() based. I assume that means all
ppc boards are 32bit clean.
if I'd like merge this readb() based or optimized for 16bit bus
version, where should I put it? obviously I have to add ifdef in
include/asm-ppc/io.h, but should I do either:
- add extern in io.h and body under platform/..../xxxx.c
- add extern in io.h and body under arch/ppc/lib/io.c
- add static inline version in io.h
- add static inline version in platform/..../xxxxx.h which is
included from asm-ppc/io.h
regards,
--
yashi
reply other threads:[~2005-09-30 20:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87irwifho6.wl@mail2.atmark-techno.com \
--to=yashi@atmark-techno.com \
--cc=linuxppc-dev@ozlabs.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).