public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: EdV@macrolink.com
Cc: peterson@austin.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: PowerPC Linux and PCI
Date: Tue, 23 Apr 2002 20:59:13 -0700 (PDT)	[thread overview]
Message-ID: <20020423.205913.43844153.davem@redhat.com> (raw)
In-Reply-To: <11E89240C407D311958800A0C9ACF7D13A77B0@EXCHANGE>

   From: Ed Vance <EdV@macrolink.com>
   Date: Tue, 23 Apr 2002 10:16:16 -0700

   James L Peterson wrote: 
   > What does this mean?  This suggests that PCI controller for
   > big-endian systems are not interchangeable with PCI controllers
   > for little-endian systems, because the controller itself does
   > byte swapping (is that what you mean by "byte twisting"?)
   
   I think David's reference is to the system's PCI subsystem/interface rather
   than to the PCI cards plugged into it.

No, I'm talking about the "PCI host controller" the thing that
connects the PCI bus to the system bus :-)

And to address James's concern, yes unmodified such a PCI controller
won't work on a little-endian system, but any sane hardware designed
would add at least a jumper of some sort to switch the behavior of
the endianness features.

All of this has to do with what "byte X" within a word means when it
comes from a little endian vs. a big endian processor.

Can I ask you to have a stare at the following document before
continuing this thread further?

	http://www.sun.com/processors/manuals/802-7835.pdf

In particular, I wish you would read Chapter 10 "endianness support".
it starts on page 115.  Sun's controller does things right, compare it
with yours to see if it deals with the byte lanes correctly when
hooked up to a big endian processor :-)

Note your original problem is an absolutely trite example, if that
code in the kernel doesn't work you are going to have tons of other
problems elsewhere when accessing things on the PCI bus.

  reply	other threads:[~2002-04-24  4:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-23 17:16 PowerPC Linux and PCI Ed Vance
2002-04-24  3:59 ` David S. Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-24 16:45 Ed Vance
     [not found] <OF8A238806.80D1511C-ON87256B75.00773B75@boulder.ibm.com>
     [not found] ` <20020307220318.GA4664@haven>
2002-04-19 21:37   ` James L Peterson
2002-04-19 21:38     ` David S. Miller
2002-04-20  9:10       ` Paul Mackerras
2002-04-22 14:14         ` James L Peterson
2002-04-23  8:00           ` Paul Mackerras
2002-04-23  8:14             ` David S. Miller
2002-04-23 16:54               ` James L Peterson
2002-04-23 17:53             ` James L Peterson

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=20020423.205913.43844153.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=EdV@macrolink.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterson@austin.ibm.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