linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Gary Thomas <gdt@linuxppc.org>
To: Paul Mackerras <paulus@linuxcare.com>
Cc: Cort Dougan <cort@fsmlabs.com>
Cc: Cort Dougan <cort@fsmlabs.com>,
	Linux/PPC Developer list <linuxppc-dev@lists.linuxppc.org>
Subject: RE: insw/outsw in ide.h
Date: Wed, 01 Mar 2000 05:37:13 -0700 (MST)	[thread overview]
Message-ID: <XFMail.000301053713.gdt@linuxppc.org> (raw)
In-Reply-To: <00030117261302.01280@argo.linuxcare.com.au>



On 01-Mar-00 Paul Mackerras wrote:
>
> Is there any PPC platform that needs to use a byte-swapping insw/outsw in
> the IDE driver?  (I can't see why any platform would, but you never
> know...)
>
> I have changed the insw/outsw/insl/outsl in include/asm-ppc/io.h to be the
> non-swapping form (in my tree at least, I'll push it to bk soon).  I would
> like to take out the special definitions of insw/outsw in
> include/asm-ppc/ide.h and just let the ide driver use the standard
> (non-swapping) form.  Will this cause a problem for any PPC platforms?
>

I can't tell for sure, but won't this break existing [already installed]
systems?  I agree that the data path really doesn't matter, but once it's
on the media it probably does.

Have you tested this change on a system with an IDE drive that has a
live file system in place?

.. just my 2c

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2000-03-01 12:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-01  6:22 insw/outsw in ide.h Paul Mackerras
2000-03-01 12:37 ` Gary Thomas [this message]
2000-03-01 13:07   ` Geert Uytterhoeven
2000-03-03  9:32     ` Cort Dougan
2000-03-03  9:40       ` Geert Uytterhoeven
2000-03-03 21:36         ` Dan Malek
2000-03-03 22:07           ` Cort Dougan
  -- strict thread matches above, loose matches on Subject: below --
2000-03-06  6:58 David Monro

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=XFMail.000301053713.gdt@linuxppc.org \
    --to=gdt@linuxppc.org \
    --cc=cort@fsmlabs.com \
    --cc=paulus@linuxcare.com \
    /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).