mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ed Vance <EdV@macrolink.com>
To: "'David S. Miller'" <davem@redhat.com>
Cc: peterson@austin.ibm.com, linux-kernel@vger.kernel.org
Subject: RE: PowerPC Linux and PCI
Date: Wed, 24 Apr 2002 09:45:44 -0700	[thread overview]
Message-ID: <11E89240C407D311958800A0C9ACF7D13A77B8@EXCHANGE> (raw)

Hi Dave,

David S. Miller wrote:
> 
>    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 :-)

Hi Dave,

Yup, same thing I was talking about. In technical terms, the thingy that 
marries the processor to the PCI bus. Some SBC's have more than one bus in
front of the PCI bus. Hmmm... I've heard that such marriages are illegal in
Texas. ;-)

Hi Jim,

Any time two unlike buses have a nexus, the nexus hardware has the major 
responsibility to resolve the issues of that nexus, whatever they may be. 
Nothing new here. Ordering of the PCI bus is always the same, as specified
in the spec, regardless of how you get there. ... And it's not always
obvious from the code what is going on in the hardware, especially if it's
_good_ hardware that makes the driver writer's life easier. 

It's all magic ...

Ed

---------------------------------------------------------------- 
Ed Vance              edv@macrolink.com
Macrolink, Inc.       1500 N. Kellogg Dr  Anaheim, CA  92807
----------------------------------------------------------------


             reply	other threads:[~2002-04-24 16:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-24 16:45 Ed Vance [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-23 17:16 Ed Vance
2002-04-24  3:59 ` David S. Miller
     [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=11E89240C407D311958800A0C9ACF7D13A77B8@EXCHANGE \
    --to=edv@macrolink.com \
    --cc=davem@redhat.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

all inboxes | Powered by JetHome®