From: Cort Dougan <cort@fsmlabs.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Gary Thomas <gdt@linuxppc.org>,
Paul Mackerras <paulus@linuxcare.com>,
Linux/PPC Developer list <linuxppc-dev@lists.linuxppc.org>
Subject: Re: insw/outsw in ide.h
Date: Fri, 3 Mar 2000 02:32:57 -0700 [thread overview]
Message-ID: <20000303023257.G8636@medea.fsmlabs.com> (raw)
In-Reply-To: <Pine.LNX.4.05.10003011405210.30603-100000@callisto.of.borg>; from Geert Uytterhoeven on Wed, Mar 01, 2000 at 02:07:11PM +0100
I think the 850's need this. I don't have one and haven't tested on one
but I recall some IDE silliness was necessary.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-03-03 9:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-01 6:22 insw/outsw in ide.h Paul Mackerras
2000-03-01 12:37 ` Gary Thomas
2000-03-01 13:07 ` Geert Uytterhoeven
2000-03-03 9:32 ` Cort Dougan [this message]
2000-03-03 9:40 ` Geert Uytterhoeven
2000-03-03 21:36 ` Dan Malek
2000-03-03 22:07 ` Cort Dougan
-- strict thread matches above, loose matches on Subject: below --
2000-03-06 6:58 David Monro
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=20000303023257.G8636@medea.fsmlabs.com \
--to=cort@fsmlabs.com \
--cc=gdt@linuxppc.org \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@linuxcare.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).