From: Andre Hedrick <andre@linux-ide.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
linux-kernel@vger.kernel.org
Subject: Re: IDE janitoring comments
Date: Sat, 24 Aug 2002 14:01:30 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.10.10208241400360.20141-100000@master.linux-ide.org> (raw)
In-Reply-To: <1030220051.3196.5.camel@irongate.swansea.linux.org.uk>
Yep, just be careful of how to decouple the hwif->iops from procfs for pci
and the general lameness of x86 centric issues.
On 24 Aug 2002, Alan Cox wrote:
> On Sat, 2002-08-24 at 16:15, Benjamin Herrenschmidt wrote:
> > - Do we really want to keep all those _P versions around ?
> > A quick grep showed _only_ by the non-portable x86 specific
> > recovery timer stuff that taps ISA timers (well, I think ports
> > 0x40 and 0x43 and an ISA timer). I would strongly suggest to
>
> I'd like to keep them around for the moment. They should be using
> udelay() but thats a general issue with _p inb/outb etc.
>
> > After much thinking about the above, I came to the conslusion
> > we probably want to just kill all the IN_BYTE, OUT_BYTE, etc.
>
> Agreed entirely
>
>
> > Also, getting rid of the _P version would make things a lot
> > easier as well here too.
>
> What currently uses the _P versions ?
>
Andre Hedrick
LAD Storage Consulting Group
next prev parent reply other threads:[~2002-08-24 20:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-24 15:15 IDE janitoring comments Benjamin Herrenschmidt
2002-08-24 20:14 ` Alan Cox
2002-08-24 21:01 ` Andre Hedrick [this message]
2002-08-24 22:28 ` Benjamin Herrenschmidt
2002-08-24 20:56 ` Andre Hedrick
-- strict thread matches above, loose matches on Subject: below --
2002-08-24 15:09 Benjamin Herrenschmidt
2002-09-23 22:01 ` Richard Zidlicky
2002-09-23 7:29 ` Benjamin Herrenschmidt
2002-09-24 0:28 ` Andre Hedrick
2002-09-24 9:27 ` Richard Zidlicky
2002-09-24 11:35 ` Benjamin Herrenschmidt
2002-09-24 12:41 ` Benjamin Herrenschmidt
2002-09-25 3:57 ` Andre Hedrick
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=Pine.LNX.4.10.10208241400360.20141-100000@master.linux-ide.org \
--to=andre@linux-ide.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.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).