X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7CA37.290113A1@onstor-exch02.onstor.net>; Thu, 19 Jul 2007 11:01:06 -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 11:01:07 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E04936F56@onstor-exch02.onstor.net>
In-Reply-To: <20070719105911.34e6bbb0@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: problem with first managment port on bobcat
Thread-Index: AcfKLoK6tzxwYjdzRQeAMGiZyBLzVQAB6mWg
References: <20070719105417.0b59afcb@ripper.onstor.net> <20070719105911.34e6bbb0@ripper.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	"Warren Gale" <warren.gale@onstor.com>

Geez Andy, I've only been back 1 day, and you've already managed to
break a Bobcat!

I'm pretty sure that the PROM was written to only support transfers out
of the first mgmt interface, but we might be able to trick the PROM into
using the second.  During the PCI scan, if we program the port 0 dp83816
to have port 1's base address and vice versa, it may work using the
second physical interface (port 1).  In the pci scan in pci-bobcat.c,
the following code exists:

	/*
	 *  Port 0 DP83816 PCI master cycle, BAR
	 */
	pci_cfg_write(PCI1_SEC_BUS, PCI1_DP0_DEV, 0, 0x04, 0x02a00006);
	pci_cfg_write(PCI1_SEC_BUS, PCI1_DP0_DEV, 0, 0x14,
HW_DP83816_0_BASE);

	/*
	 *  Port 1 DP83816 PCI master cycle, BAR
	 */
	pci_cfg_write(PCI1_SEC_BUS, PCI1_DP1_DEV, 0, 0x04, 0x02a00006);
	pci_cfg_write(PCI1_SEC_BUS, PCI1_DP1_DEV, 0, 0x14,
HW_DP83816_1_BASE);


We can try changing it to:


	/*
	 *  Port 0 DP83816 PCI master cycle, BAR
	 */
	pci_cfg_write(PCI1_SEC_BUS, PCI1_DP0_DEV, 0, 0x04, 0x02a00006);
	pci_cfg_write(PCI1_SEC_BUS, PCI1_DP0_DEV, 0, 0x14,
HW_DP83816_1_BASE);

	/*
	 *  Port 1 DP83816 PCI master cycle, BAR
	 */
	pci_cfg_write(PCI1_SEC_BUS, PCI1_DP1_DEV, 0, 0x04, 0x02a00006);
	pci_cfg_write(PCI1_SEC_BUS, PCI1_DP1_DEV, 0, 0x14,
HW_DP83816_0_BASE);


Plug a wire into the second port and then give it a shot.

Warren will put this change in, we'll test it out here, and then let you
know.


Brian

=20

> -----Original Message-----
> From: Andy Sharp=20
> 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.  I've got a bc=20
> > that seems to have a frelled ethernet port on the first management=20
> > interface, so I thought I would try to use the second one, but the=20
> > PROM code doesn't seem to be able to handle this.  I can=20
> set up an IP=20
> > address on it and whatnot, but when I try to send network traffic=20
> > through it, I get errors from the the box.  Can you confirm=20
> that the=20
> > PROM networking code makes assumptions about what port is=20
> being used=20
> > to tftp things?  Like, I was trying to tftp a new prom 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
> --------------------------------------------------------------
>           =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(=20
> --------------------------------------------------------------
> ------------------
> 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
