From: Dan Sheets <dans@phx.mcd.mot.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: More on PREP IDE Fixes
Date: Fri, 22 Oct 1999 06:42:07 -0700 [thread overview]
Message-ID: <381069AF.655D9989@phx.mcd.mot.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 889 bytes --]
Cort asked me to ask people to test these changes.
Cort is planning on putting these changes in unless
people can find problems with the modifications.
Could someone else please try out these changes?
I've attached the diff. This diff is against vger 2.2,
Cort's request.
Since my original post I found an old Blackhawk
(PowerStack) that has IDE. I tried my original patch
on this board and it didn't work. Well, come to find
out the standard 2.2 PPC kernel also didn't support
IDE. So in the patch that's attached, I have also fixed
IDE on a Blackhawk.
I have tested this patch on a MTX, MCP750, MCPN750
and a Blackhawk.
Thanks
--
___________________________________________________________________
Dan Sheets Motorola Computer Group
Software Engineer, RTSS 2900 South Diablo Way, MD DW278
dans@phx.mcd.mot.com Tempe, AZ 85282
[-- Attachment #2: vger2.2Ide.udiff.gz --]
[-- Type: encoding/x-gzip, Size: 3284 bytes --]
reply other threads:[~1999-10-22 13:42 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=381069AF.655D9989@phx.mcd.mot.com \
--to=dans@phx.mcd.mot.com \
--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).