AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080730163112.0f3b03a9@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<brian.stark@onstor.com>,<warren.gale@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	46839	BB375AF679D4A34E9CA8DFA650E2B04E0B192333@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Wed, 30 Jul 2008 16:33:12 -0700
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Brian Stark" <brian.stark@onstor.com>
Cc: "Warren Gale" <warren.gale@onstor.com>
Subject: Re: kernel and telnet info
Message-ID: <20080730163312.4c919a32@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0B192333@onstor-exch02.onstor.net>
References: <20080730111500.4ac195c1@ripper.onstor.net>
 <BB375AF679D4A34E9CA8DFA650E2B04E0B192333@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

Whoops, this languished in my Drafts folder and was sorta forgotten...


My first thought is, fix the hardware.  It seems doubtful considering
what we know that it's supposed to be working that way, so something
must be "hooked up backwards" on some of these boards (a phrase not to
be taken literally) because some of them work as is.

Unless our particular hardware is designed to work this way and we
don't know it.

I want to continue to look at the driver to see if pinging between sc0
and sc1 can be made to work properly.

So basically I think we have more work to do in hardware and software
at this point, to see why some boards are supposedly fine as is, and
some aren't.  And to see if the problem of pinging between eth0 and
eth1 can be found.

Restricting the ports to 10/100 is not sitting well with me at all.
We've also announced the hardware capabilities at this point, so we
might get some push back from customers at this point.

On Wed, 30 Jul 2008 13:19:44 -0700 "Brian Stark"
<brian.stark@onstor.com> wrote:

> I tried this kernel on Rendell's problem child board, and both ports
> worked when pinging sc0 and sc1 at GigE.  This was the case when going
> direct connect to another system as well as going through a GigE
> switch. So, flipping the clock edge bit to a 1 definitely is making
> the ports work at GigE.
> 
> I haven't heard anything back from Broadcom yet on my theory about the
> user's manual having an incorrect definition.  We need to make a
> decision on how to proceed and have 2 options:
> 
> - Put the clock change into both PROM and kernel, which will allow sc0
> and sc1 to run at GigE
> - Limit the PHY speed to 100Mbit in PROM, no change to kernel
> 
> Thoughts?
> 
> 
> > -----Original Message-----
> > From: Andy Sharp 
> > Sent: Wednesday, July 30, 2008 11:15 AM
> > To: Brian Stark; Warren Gale
> > Subject: kernel and telnet info
> > 
> > Kernel is attached (vmlinux.bin) and telnet is
> > 
> > telnet 10.2.10.235 9044
> > 
