Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Marco Braga <marco.braga@gmail.com>
Cc: Michael Stickel <michael@cubic.org>, linux-mips@linux-mips.org
Subject: Re: Au1500 and TI PCI1510 cardbus
Date: Mon, 19 Mar 2007 15:36:06 +0300	[thread overview]
Message-ID: <45FE83B6.3040100@ru.mvista.com> (raw)
In-Reply-To: <d459bb380703180617i6e50539bx13ad405fb306fe44@mail.gmail.com>

Marco Braga wrote:
>> I am sory, I meant the datasheet of the Au1500. I do not find the
>> paragraph anymore, but can tell you more on monday.

    I think Michael actually mean the specification update, not datasheet.
Indeed, errata 32

> Thank you. I've checked the data book but I've not found anything so
> explicit. Paragraph 4.3.10 "Other notes" states:

> "The Au1500 PCI contoller cannot be used with external PCI-to-PCI bridges
> that have PCI bus-mastering devices on the
> secondary bus which target the Au1500 memory."

> But this is not exactly an explanation.. I've found nothing regarding race
> conditions or delayed transactions. I'll wait eagerly for monday when all
> the truths will be revealed. :)

    Hrm, this seems enough of an explanation -- it basically says that you 
can't use any decent PCI device behind the bridge.  The abovementioned errata 
tells that "any mastering device on the other side of a P2P bridge, where the 
target is the Au1500 processor, will eventually lead to a lock-up condition of 
the PCI bus or even the entire system".

> Thanks!!

WBR, Sergei

  reply	other threads:[~2007-03-19 12:36 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-16 18:29 Au1500 and TI PCI1510 cardbus Marco Braga
2007-03-17  9:49 ` Michael Stickel
2007-03-17 12:54   ` Marco Braga
2007-03-17 13:45     ` Michael Stickel
2007-03-18 13:17       ` Marco Braga
2007-03-19 12:36         ` Sergei Shtylyov [this message]
2007-03-19 14:42           ` Marco Braga
     [not found]           ` <d459bb380703190741w3d0bef6fw101c64da8d81d422@mail.gmail.com>
2007-03-19 14:45             ` Sergei Shtylyov
2007-03-19 14:55               ` Marco Braga
2007-03-20  2:04                 ` Takeyoshi Kikuchi
2007-03-20  7:32                   ` Marco Braga
2007-03-20  9:02                     ` Takeyoshi Kikuchi
2007-03-20 14:21                   ` Sergei Shtylyov
2007-03-20 14:47                     ` Marco Braga
2007-03-20 14:47                       ` Marco Braga
2007-03-20 15:32                       ` Sergei Shtylyov
2007-03-20 15:50                         ` Marco Braga
2007-03-20 16:00                           ` Sergei Shtylyov
2007-03-20 16:08                             ` Marco Braga
2007-03-20 16:25                               ` Sergei Shtylyov
2007-03-20 16:33                                 ` Marco Braga
2007-03-24  6:23                                   ` Attila Kinali
2007-03-24 14:16                                     ` Sergei Shtylyov
2007-03-24 16:00                                       ` Attila Kinali

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=45FE83B6.3040100@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=linux-mips@linux-mips.org \
    --cc=marco.braga@gmail.com \
    --cc=michael@cubic.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