From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Marco Braga <marco.braga@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Au1500 and TI PCI1510 cardbus
Date: Tue, 20 Mar 2007 19:25:01 +0300 [thread overview]
Message-ID: <46000ADD.3050309@ru.mvista.com> (raw)
In-Reply-To: <d459bb380703200908t2ab759f0u352dc0014ebe0b17@mail.gmail.com>
Hello.
Marco Braga wrote:
>> > I think I'm beginning to make a lot of confusion. Is the problem that
>> the
>> > PCI1510 must NOT be behind a bridge, or the problem is that PCI1510
>> acts
>> as
>> > a bridge, so cardbus cards cannot work?
>> The second.
> Ok, at the risk of appearing totally dumb, I'll double check.. If the
> second
> ic correct, PCI1510 is a bridce, a cardbus card cannot work.
Yeah. Note that it's not totally broken -- you just can't use the "decent"
devices on it, i.e. ones with bus mastering.
>> You can see yourself that PCI1510 is a bridge (Cardbus-to-PCI bridge is
>> largely the same as PCI-to-PCI bridge).
> Ok.
Yeah, that's an importnat point. AMD docs don't say about CardBus
bridges, So, it was probably obvious to me only. :-)
>> So it seems that the 3Com card is behind a bus. Should this work? From
>> what
>> > I've understood, it should now work..
>> Think again. :-)
> Ok, that's a typo :-) It should NOT work. Is this better?
> Sounds like what's been told in the errata 32.
> It seems that Au1500 slowly faded into the shadows. Now it is owned by
> Raza, but there is no sign of an errata document, perhaps I've lost the
> magic moment when a lot of documentation was available.
The errata has been available only from the AMD's developer site.
> But still, the question remains: how can Takeyoshi's "Ricoh CardBus Bridge"
> work with a cardbus card if bridges cannot work with Au1500's PCI?
> Scrub scrub..
WBR, Sergei
next prev parent reply other threads:[~2007-03-20 16:24 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 [this message]
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=46000ADD.3050309@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox