From: Tim Waugh <twaugh@redhat.com>
To: Jamie Lokier <lk@tantalophile.demon.co.uk>
Cc: Richard Zidlicky <rz@linux-m68k.org>,
tim@cyberelk.net, linux-kernel@vger.kernel.org,
Fred Barnes <Frederick.Barnes@cern.ch>
Subject: Re: insl/outsl in parport_pc and !CONFIG_PCI
Date: Thu, 31 May 2001 12:06:54 +0100 [thread overview]
Message-ID: <20010531120654.H13668@redhat.com> (raw)
In-Reply-To: <20010527191613.A2808@rz.informatik.uni-erlangen.de> <20010529021156.B6061@pcep-jamie.cern.ch>
In-Reply-To: <20010529021156.B6061@pcep-jamie.cern.ch>; from lk@tantalophile.demon.co.uk on Tue, May 29, 2001 at 02:11:56AM +0200
[-- Attachment #1: Type: text/plain, Size: 241 bytes --]
On Tue, May 29, 2001 at 02:11:56AM +0200, Jamie Lokier wrote:
> Will 4 * inb() cycles have the same effect as 1 * inl() cycle for an EPP
> mode read?
4 inb() cycles on the same port, yes, I think so (but not on
successive ports).
Tim.
*/
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
prev parent reply other threads:[~2001-05-31 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-27 17:16 insl/outsl in parport_pc and !CONFIG_PCI Richard Zidlicky
2001-05-29 0:11 ` Jamie Lokier
2001-05-31 11:06 ` Tim Waugh [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=20010531120654.H13668@redhat.com \
--to=twaugh@redhat.com \
--cc=Frederick.Barnes@cern.ch \
--cc=linux-kernel@vger.kernel.org \
--cc=lk@tantalophile.demon.co.uk \
--cc=rz@linux-m68k.org \
--cc=tim@cyberelk.net \
/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