All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Attila Kinali <attila@kinali.ch>
Cc: Marco Braga <marco.braga@gmail.com>, linux-mips@linux-mips.org
Subject: Re: Au1500 and TI PCI1510 cardbus
Date: Sat, 24 Mar 2007 17:16:31 +0300	[thread overview]
Message-ID: <460532BF.6080605@ru.mvista.com> (raw)
In-Reply-To: <20070324072308.c69557d0.attila@kinali.ch>

Hello.

Attila Kinali wrote:

>>To sum it up, Cardbus bridge is not a viable solution on Au1500 for
>>hotswapping devices, since any decent one (bus mastering) will not work.
>>USB2.0 should instead work with PCI based controllers, that must be
>>connected to the main PCI device (directly to Au1500).

> We are using a board with a Au1550 with cardbus (PCI1520) and
> USB2.0. The USB controller is directly connected to PCI.
> Although cardbus isn't fully tested yet, USB seems to work fine
> (atleast i haven't heard of any problems), but i don't know
> from the top of my head which chip they used.

> Also, the Au1550 doesn't seem to have the master-behind-bridge
> bug as the 1500 does (at least according to the datasheet),

    Reading revisions C and D of the Au1550 datasheet, I see:

4.3.9 System Considerations

The Au1550 PCI controller cannot be used with external PCI-to-PCI bridges that 
have PCI bus-mastering devices on the secondary bus which target the Au1550 
memory.

> so i guess cardbus should work also with "decent" cards :)

    OTOH, Au1550 errata I have is silent about the P2P bridges.

> HTH 
> 			Attila Kinali

WBR, Sergei

  reply	other threads:[~2007-03-24 14:16 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
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 [this message]
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=460532BF.6080605@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=attila@kinali.ch \
    --cc=linux-mips@linux-mips.org \
    --cc=marco.braga@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.