public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Andre Hedrick <andre@linux-ide.org>,
	Russell King <rmk@arm.linux.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: VIA, 32bit PIO and 2.5.x kernel
Date: Sun, 14 Apr 2002 00:49:24 +0200	[thread overview]
Message-ID: <3CB8B5F4.8040402@evision-ventures.com> (raw)
In-Reply-To: <E16wRU9-0000hL-00@the-village.bc.nu>

Alan Cox wrote:
>>>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?
>>
> 
> What if the user doesn't know the precise innards of their hardware. IDE
> more than anything else has to automagically do the right thing. Given the
> size of the PIO transfer loop and the way for some boards its weirdly 
> dependant on hardware magic and wonder is there any reason for not just 
> making the host controller provide the function or reference an ide library
> function for "sane" hardware ?

Alan - that's not the issue here.


  parent reply	other threads:[~2002-04-13 23:52 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
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 [this message]
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=3CB8B5F4.8040402@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=andre@linux-ide.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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