From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: linas@austin.ibm.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: [PATCH] ppc64 kernel 2.6 ide-related patches (revised)
Date: Sat, 13 Sep 2003 20:18:53 +0200 [thread overview]
Message-ID: <1063477133.9720.23.camel@gaston> (raw)
In-Reply-To: <20030912120037.A26892@forte.austin.ibm.com>
On Fri, 2003-09-12 at 19:00, linas@austin.ibm.com wrote:
> -- the current code does *not* auto-negotiate itself up into the
> highest possible performance mode. (i.e. 32 bit transfers, dma on,
> etc.) This appears to be due to the fact that this task is normally
> done by i386 BIOS, and the ppc open firmware doesn't do anything
> analogous, and there's nothing in the kernel (that I know of) to
> make up for this.
This is done in the kernel by the host chipset driver normally. It works
fine on pmac with ppc32 at least ;)
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2003-09-13 18:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-11 16:28 [PATCH] ppc64 kernel 2.6 ide-related patches (trivial) linas
2003-09-11 22:04 ` linas
2003-09-12 17:00 ` [PATCH] ppc64 kernel 2.6 ide-related patches (revised) linas
2003-09-13 18:18 ` Benjamin Herrenschmidt [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=1063477133.9720.23.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=linas@austin.ibm.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).