From: Martin Dalecki <dalecki@evision-ventures.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
Petr Vandrovec <vandrove@vc.cvut.cz>,
linux-kernel@vger.kernel.org
Subject: Re: VIA, 32bit PIO and 2.5.x kernel
Date: Sat, 13 Apr 2002 15:23:26 +0200 [thread overview]
Message-ID: <3CB8314E.7050707@evision-ventures.com> (raw)
In-Reply-To: <20020412001029.GA1172@ppc.vc.cvut.cz> <20020412102021.A18037@ucw.cz> <3CB694FC.2060701@evision-ventures.com> <20020413111229.B19090@flint.arm.linux.org.uk>
Russell King wrote:
> On Fri, Apr 12, 2002 at 10:04:12AM +0200, Martin Dalecki wrote:
>
>>3. Make 32 bit PIO transfers the global default.
>
>
> This is fine, as long as you allow some interfaces to say "I really want
> to be 16-bit PIO only".
>
> I *need* 16-bit transfers for many ARM-based IDE stuff. 32-bit is not
> an option on many, if not all ARM-based PCMCIA stuff.
What I wan't to disable is just the *unconditional* fallback to 16 bit IO
at some places. This and not more. This doens't even affect the physical setup
between the host chip and the controller on disc.
The global "wheee I'm a poor and can't afford 32 bit IO" option will remain
there of course.
So we have no issue here. OK?
next prev parent reply other threads:[~2002-04-13 14:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-12 0:10 VIA, 32bit PIO and 2.5.x kernel Petr Vandrovec
2002-04-12 0:56 ` VIA and 2.5.8-pre kernels doesn't boot! Anton Altaparmakov
2002-04-12 7:46 ` Martin Dalecki
2002-04-12 10:10 ` Anton Altaparmakov
2002-04-12 8:20 ` VIA, 32bit PIO and 2.5.x kernel Vojtech Pavlik
2002-04-12 8:04 ` Martin Dalecki
2002-04-13 10:12 ` Russell King
2002-04-13 10:15 ` Vojtech Pavlik
2002-04-13 13:23 ` Martin Dalecki [this message]
2002-04-13 17:06 ` Andre Hedrick
2002-04-13 17:38 ` Alan Cox
2002-04-13 18:15 ` Andre Hedrick
2002-04-13 22:49 ` Martin Dalecki
2002-04-12 8:41 ` Jens Axboe
2002-04-12 9:15 ` Andre Hedrick
2002-04-12 8:53 ` Martin Dalecki
2002-04-12 10:16 ` Jens Axboe
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=3CB8314E.7050707@evision-ventures.com \
--to=dalecki@evision-ventures.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=vandrove@vc.cvut.cz \
--cc=vojtech@suse.cz \
/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