From: Paul Mackerras <paulus@cs.anu.edu.au>
To: trini@disparity.net
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Trying a Promise Ultra/66 on powerpc
Date: Mon, 9 Aug 1999 16:02:28 +1000 [thread overview]
Message-ID: <199908090602.QAA13922@tango.anu.edu.au> (raw)
In-Reply-To: <Pine.BSF.3.96.990808165209.16262c-100000@silver.teardrop.net> (message from Tom Rini on Sun, 8 Aug 1999 16:55:01 -0400 (EDT))
Tom Rini <trini@disparity.net> wrote:
> Would this be one of the things solved/cleaned up by seperating ide-pmac.c
> and the CONFIG option for it into generic enable IDE stuff and a driver
> for the builtin IDE on some machines? Last I tried, I needed to enable
> both cmd646 and ide-pmac on myy blue&white (trying to do this is on my
> todo list, someplace.. :))
There's no problem about enabling both cmd646 and ide-pmac with the
current vger sources, is there? You do need to select experimental
drivers as well as "Generic PCI IDE chipset support"
(CONFIG_BLK_DEV_IDEPCI) and "Generic PCI bus-master DMA support"
(CONFIG_BLK_DEV_IDEDMA) before you get asked about the CMD646, though.
Paul.
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting. ]]
next prev parent reply other threads:[~1999-08-09 6:02 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <19990727112137.A897@drow.res.cmu.edu>
[not found] ` <Pine.LNX.3.96.990727160229.10158B-100000@Astro.Dyer.Vanderbilt.Edu>
[not found] ` <19990727102627.A370@drow.res.cmu.edu>
[not found] ` <Pine.LNX.3.96.990727093644.6993B-100000@Astro.Dyer.Vanderbilt.Edu>
[not found] ` <19990727235430.D1046@albireo.ucw.cz>
1999-07-28 3:04 ` Trying a Promise Ultra/66 on powerpc Daniel Jacobowitz
1999-07-28 5:48 ` Michel Lanners
1999-07-28 7:17 ` Andre M. Hedrick
1999-08-08 19:54 ` Michel Lanners
1999-08-08 20:55 ` Tom Rini
1999-08-08 21:01 ` Michel Lanners
1999-08-09 3:22 ` Daniel Jacobowitz
1999-08-09 6:02 ` Paul Mackerras [this message]
1999-08-09 19:28 ` Tom Rini
1999-08-09 20:06 ` Michel Lanners
1999-08-09 3:26 ` Daniel Jacobowitz
1999-08-09 21:13 ` Michel Lanners
1999-08-12 20:05 ` Michel Lanners
1999-08-13 8:43 ` Geert Uytterhoeven
1999-08-09 5:13 ` Paul Mackerras
1999-08-09 5:18 ` David A. Gatwood
1999-08-09 5:33 ` Paul Mackerras
1999-08-09 5:38 ` David A. Gatwood
1999-08-09 6:50 ` Benjamin Herrenschmidt
1999-08-09 20:15 ` Michel Lanners
1999-08-09 20:23 ` Michel Lanners
1999-08-10 0:10 ` Paul Mackerras
1999-08-10 5:38 ` Michel Lanners
1999-08-10 8:45 ` Benjamin Herrenschmidt
1999-08-15 9:20 ` Martin Mares
1999-08-10 12:56 ` Geert Uytterhoeven
1999-08-12 17:30 ` Michel Lanners
1999-07-28 6:18 ` Tom Rini
1999-07-28 8:07 ` Martin Mares
1999-07-29 0:31 ` Andre M. Hedrick
1999-08-01 7:23 ` Michel Lanners
1999-07-29 9:16 Benjamin Herrenschmidt
1999-08-08 20:00 ` Michel Lanners
1999-08-08 20:52 ` Geert Uytterhoeven
1999-08-08 21:21 ` Michel Lanners
1999-08-08 21:27 ` Geert Uytterhoeven
1999-08-15 9:23 ` Martin Mares
-- strict thread matches above, loose matches on Subject: below --
1999-08-13 14:28 Justin McKillican
[not found] <199908092022.WAA00327@piglet.cpu.lu>
1999-08-15 9:39 ` Martin Mares
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=199908090602.QAA13922@tango.anu.edu.au \
--to=paulus@cs.anu.edu.au \
--cc=Paul.Mackerras@cs.anu.edu.au \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@disparity.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;
as well as URLs for NNTP newsgroup(s).