From: Neil Russell <caret@c-side.com>
To: Adrian Cox <apc@agelectronics.co.uk>,
LinuxPPC-Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: ppc_ide_md.insw
Date: Fri, 20 Oct 2000 01:31:35 -0700 [thread overview]
Message-ID: <20001020013135.I21761@lx.c-side.com> (raw)
In-Reply-To: <39EEECA5.459D0C93@agelectronics.co.uk>; from Adrian Cox on Thu, Oct 19, 2000 at 01:44:21PM +0100
They are used by macros in include/asm-ppc/ide.h called "insw" and "outsw".
I know they are called because I have traced them. You can just fix the
versions in the arch/ppc/kernel directory to do what you want.
Normally, there is logic to convert 16-bit accesses from a CPU into a pair
of 8-bit accesses for IDE (a hangover from the ISA bus). Our hardware does
this but I'm not entirely convinced that this is necessary. Anyhow, if you
are using one of the PPCs in the 8xx family, or the 8260 you can define a
chip select line for IDE that has an 8-bit bus width, obviating any need
to change software.
Neil
On Thu, Oct 19, 2000 at 01:44:21PM +0100, Adrian Cox wrote:
> Do ppc_ide_md.insw and .outsw actually do anything in recent 2.2
> kernels? My grepping has left me unclear.
>
> I need to implement a driver for a compact flash interface which can't
> take 16-bit cycles. Do I need to invent my own mechanism to replace the
> insw and outsw operations in drivers/block/ide.c?
>
> - Adrian Cox, AG Electronics
>
--
Neil Russell <caret@c-side.com>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-10-20 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-19 12:44 ppc_ide_md.insw Adrian Cox
2000-10-20 8:31 ` Neil Russell [this message]
2000-10-20 9:08 ` ppc_ide_md.insw Adrian Cox
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=20001020013135.I21761@lx.c-side.com \
--to=caret@c-side.com \
--cc=apc@agelectronics.co.uk \
--cc=linuxppc-dev@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).