X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7CA42.1AFBEC79@onstor-exch02.onstor.net>; Thu, 19 Jul 2007 12:19:27 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: problem with first managment port on bobcat
Date: Thu, 19 Jul 2007 12:19:27 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E04936F9E@onstor-exch02.onstor.net>
In-Reply-To: <20070719131054.1ca8d047@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: problem with first managment port on bobcat
Thread-Index: AcfKQOkWqJz059yCSIObqT/oezR0yAAAPzRA
References: <20070719105417.0b59afcb@ripper.onstor.net><20070719105911.34e6bbb0@ripper.onstor.net><BB375AF679D4A34E9CA8DFA650E2B04E04936F56@onstor-exch02.onstor.net> <20070719131054.1ca8d047@ripper.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Warren Gale" <warren.gale@onstor.com>

We can upgrade the prom from the os if the second port is working there
by using the prom-upgrade daemon...

=20

> -----Original Message-----
> From: Andy Sharp=20
> Sent: Thursday, July 19, 2007 1:11 PM
> To: Brian Stark
> Cc: Warren Gale
> Subject: Re: problem with first managment port on bobcat
>=20
> Only one small problem: it's difficult to upgrade the prom=20
> w/o the first port working ~:^)  At least for me.  You=20
> hardware guys probably have special tools and stuff like=20
> that.  Soldering irons and things.
>=20
> Cheers,
>=20
> a
>=20
>=20
> On Thu, 19 Jul 2007 12:01:07 -0700 "Brian Stark"
> <brian.stark@onstor.com> wrote:
>=20
> > Geez Andy, I've only been back 1 day, and you've already managed to=20
> > break a Bobcat!
> >=20
> > I'm pretty sure that the PROM was written to only support transfers=20
> > out of the first mgmt interface, but we might be able to trick the=20
> > PROM into using the second.  During the PCI scan, if we program the=20
> > port 0 dp83816 to have port 1's base address and vice versa, it may=20
> > work using the second physical interface (port 1).  In the=20
> pci scan in=20
> > pci-bobcat.c, the following code exists:
> >=20
> > 	/*
> > 	 *  Port 0 DP83816 PCI master cycle, BAR
> > 	 */
> > 	pci_cfg_write(PCI1_SEC_BUS, PCI1_DP0_DEV, 0, 0x04, 0x02a00006);=20
> > pci_cfg_write(PCI1_SEC_BUS, PCI1_DP0_DEV, 0, 0x14,=20
> HW_DP83816_0_BASE);
> >=20
> > 	/*
> > 	 *  Port 1 DP83816 PCI master cycle, BAR
> > 	 */
> > 	pci_cfg_write(PCI1_SEC_BUS, PCI1_DP1_DEV, 0, 0x04, 0x02a00006);=20
> > pci_cfg_write(PCI1_SEC_BUS, PCI1_DP1_DEV, 0, 0x14,=20
> HW_DP83816_1_BASE);
> >=20
> >=20
> > We can try changing it to:
> >=20
> >=20
> > 	/*
> > 	 *  Port 0 DP83816 PCI master cycle, BAR
> > 	 */
> > 	pci_cfg_write(PCI1_SEC_BUS, PCI1_DP0_DEV, 0, 0x04, 0x02a00006);=20
> > pci_cfg_write(PCI1_SEC_BUS, PCI1_DP0_DEV, 0, 0x14,=20
> HW_DP83816_1_BASE);
> >=20
> > 	/*
> > 	 *  Port 1 DP83816 PCI master cycle, BAR
> > 	 */
> > 	pci_cfg_write(PCI1_SEC_BUS, PCI1_DP1_DEV, 0, 0x04, 0x02a00006);=20
> > pci_cfg_write(PCI1_SEC_BUS, PCI1_DP1_DEV, 0, 0x14,=20
> HW_DP83816_0_BASE);
> >=20
> >=20
> > Plug a wire into the second port and then give it a shot.
> >=20
> > Warren will put this change in, we'll test it out here, and=20
> then let=20
> > you know.
> >=20
> >=20
> > Brian
> >=20
> > =20
> >=20
> > > -----Original Message-----
> > > From: Andy Sharp
> > > Sent: Thursday, July 19, 2007 10:59 AM
> > > To: Warren Gale
> > > Cc: Brian Stark
> > > Subject: Re: problem with first managment port on bobcat
> > >=20
> > > On Thu, 19 Jul 2007 10:54:17 -0700 Andrew Sharp=20
> > > <andy.sharp@onstor.com>
> > > wrote:
> > >=20
> > > > Hi Warren,
> > > >=20
> > > > Since your prom-man, I thought I would ask you this. =20
> I've got a=20
> > > > bc that seems to have a frelled ethernet port on the first=20
> > > > management interface, so I thought I would try to use=20
> the second=20
> > > > one, but the PROM code doesn't seem to be able to=20
> handle this.  I=20
> > > > can
> > > set up an IP
> > > > address on it and whatnot, but when I try to send=20
> network traffic=20
> > > > through it, I get errors from the the box.  Can you confirm
> > > that the
> > > > PROM networking code makes assumptions about what port is
> > > being used
> > > > to tftp things?  Like, I was trying to tftp a new prom=20
> image or a=20
> > > > linux kernel, but it just spewed errors.
> > > >=20
> > > > Cheers,
> > > >=20
> > > > a
> > >=20
> > > Just for reference, here is some of the output from the filer:
> > >=20
> > > SSC-PROM> bsd ip show
> > > Interface Table     =20
> > > --------------------------------------------------------------
> > > Name                Mac-Addr                Op-St   Adm-St   =20
> > >   IP/Mask
> > > --------------------------------------------------------------
> > >           =20
> > > fp:0:0:0(NULL)      00-07-34-00-90-00       UP      DOWN      =20
> > > fp:0:0:1(NULL)      00-07-34-00-90-01       UP      UP       =20
> > >  10.0.0.53/24
> > >                                                              =20
> > >             =20
> > > fp:0:0:2(NULL)      08-08-00-00-01-02       UP      DOWN     =20
> > >  192.168.192.17/24
> > >                                                              =20
> > >                 =20
> > > lo:0:0:0(NULL)      00-00-00-00-00-00       UP      UP        =20
> > > SSC-PROM> bsd ping 10.0.0.53                                  =20
> > > File: if_ether.c, Line: 879
> > > arplookup 10.0.0.0 failed: host is not on local network
> > >                                                       =20
> > > File: if_ether.c, Line: 477
> > > arpresolve: can't allocate llinfo for 10.0.0.0rt
> > >                                                =20
> > > File: if_ether.c, Line: 879
> > > arplookup 10.0.0.53 failed: host is not on local network
> > >                                                        =20
> > > File: if_ether.c, Line: 477
> > > arpresolve: can't allocate llinfo for 10.0.0.53rt
> > >                                                 =20
> > > SSC-PROM> File: if_ether.c, Line: 879
> > > arplookup 10.0.0.53 failed: host is not on local network
> > >                                                        =20
> > > File: if_ether.c, Line: 477
> > > arpresolve: can't allocate llinfo for 10.0.0.53rt
> > >                                                 =20
> > >=20
> > > SSC-PROM> File: if_ether.c, Line: 879
> > > arplookup 10.0.0.53 failed: host is not on local network
> > >                                                        =20
> > > File: if_ether.c, Line: 477
> > > arpresolve: can't allocate llinfo for 10.0.0.53rt
> > >                                                 =20
> > > SSC-PROM> bsd rt show
> > > Route Table         =20
> > > --------------------------------------------------------------
> > > ------------------
> > > Dest                 Gateway               Flags    Intf     =20
> > >             refc(
> > > --------------------------------------------------------------
> > > ------------------
> > > 10.0.0.0       /8    10.0.0.53             0x1000803=20
> > > fp:0:0:1(NULL)      1(8115)
> > > 192.168.192.0  /24   00-00-00-00-00-00     0x101    =20
> > > fp:0:0:2(NULL)      0(8115)
> > > SSC-PROM>=20
> > >=20
>=20
