AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070523162223.63f7b0fc@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<brian.stark@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E03D91027@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 23 May 2007 16:23:37 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Brian Stark" <brian.stark@onstor.com>
Subject: Re: what bridge chip is used on Bobcat for PCI/PCMCIA
Message-ID: <20070523162337.1be9eef1@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E03D91027@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E03D91027@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Ha!  I think we can all agree that civilized men aren't responsible for
anything that happened last year.  Or more than 3 weeks ago.

Identifying the part and what code to use all happens "automagically",
the trick is making the code that is used actually work.  So far all
the keys to that trick seem to be eluding me.

Give me a ring when you get a chance.  Are you going to be down here
again this week?

Cheers,

a

On Wed, 23 May 2007 16:05:41 -0700 "Brian Stark"
<brian.stark@onstor.com> wrote:

> OK, you asked for it yesterday.  Here's the email in which I sent you
> the TI spec back on December 21.  Don't worry, I'm not going to rub it
> in anymore than I already have!
> 
> From what I've gathered so far, the interrupts on the TI part are
> reversed compared to the Cirrus part, e.g. INTA_L for Socket A and
> INTB_L for Socket B with TI, vice versa for Cirrus.  The functionality
> and conditions to generate an interrupt are the same.  I need to get
> onto the RoHS Bobcat here to take a look to confirm this, but I see
> that you're logged in to the terminal parts.  Can you log off of port
> 13 for a while?    
> 
> Another difference is that the ExCA registers are mapped at 0xb8010000
> when the TI part is installed versus 0xb8000000 when the Cirrus part
> is installed.  The ExCA registers are i/o mapped and are used to
> communicate with the CF controller and also set up windows to CF.  
> 
> In the BSD code that Dan did, the code looks to see which part is
> installed based on PCI vendor id and then configures accordingly.
> This probably does it with a hard-wired approach like with other
> stuff, but it should still serve as an example to illustrate
> differences between parts.  From the email that Warren sent earlier
> about this, the code id's the part with "is_cf_vendor_TI".  Finally,
> take a look at change ids 21194 and 21246 for more info on all of
> this.
> 
> I've also sent an email to Abdallah about the rework to the RoHS
> motherboard, and if he can't get to that soon, I'll bring my RoHS
> system down to Campbell for you to use.  This is the system that we'd
> use with the logic analyzer if need be, though, and that would most
> easily be done in P'town.
> 
> 
> Brian
> 
> 
> -----Original Message-----
> From: Brian Stark 
> Sent: Thursday, December 21, 2006 2:18 PM
> To: Andy Sharp
> Subject: RE: what bridge chip is used on Bobcat for PCI/PCMCIA
> 
> Andy,
> 
> We're using the TI PCI1520 for the PCI-to-PCMCIA bridge.  Spec is
> attached.  We are only using 16-bit PC Card support since that's the
> only mode that CF supports.  
> 
> 
> Brian
> 
> 
> > -----Original Message-----
> > From: Andrew Sharp [mailto:andy.sharp@onstor.com]
> > Sent: Thursday, December 21, 2006 2:16 PM
> > To: Brian Stark
> > Cc: Warren Gale
> > Subject: Q: what bridge chip is used on Bobcat for PCI/PCMCIA
> > 
> > I need to know what the PCMCIA bridge chip is on bobcat (I
> > understand the flash is actually controlled off a PCMCIA controller
> > or somesuch). I also need to know if I need cardbus or only pcmcia
> > 16 bit support. I assume I need at least 16 bit (PCCARD) support.
> > 
> > Cheers,
> > 
> > a
> > 
