AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20071109182652.17fd5ab7@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<brian.stark@onstor.com>,<rick.lund@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	BB375AF679D4A34E9CA8DFA650E2B04E0103C4D8@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Fri, 9 Nov 2007 18:27:36 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Brian Stark" <brian.stark@onstor.com>
Cc: "Rick Lund" <rick.lund@onstor.com>
Subject: Re: prom changes
Message-ID: <20071109182736.36098c23@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E0103C4D8@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E0103C4D8@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

My comments were written with full understanding of that.  The short
version: set the value in the MAC and Linux will take care of the rest.

Currently on the cougarz, the mac addr comes out like thus:

coolcat:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 40:00:00:00:01:00  

Which I believe is what's sitting in the MAC when the linux driver gets
to it.

On Fri, 9 Nov 2007 18:09:05 -0800 "Brian Stark"
<brian.stark@onstor.com> wrote:

> It's not as simple as setting the mac addr register.  The transmit
> descriptor needs to tell the ethernet engine to use the value in this
> register.  Setting this bit in the descriptor has to be done in the
> driver, both the one in prom and linux...
> 
> 
> 
> 
> 
> -----Original Message-----
> From: Andy Sharp
> To: Brian Stark
> CC: Rick Lund
> Sent: Fri Nov 09 17:56:23 2007
> Subject: Re: prom changes
> 
> On Fri, 9 Nov 2007 17:38:41 -0800 "Brian Stark"
> <brian.stark@onstor.com> wrote:
> 
> > FYI, if we want to use the mac addr programmed into the SiByte MAC,
> > then the transmit descriptor needs to be modified to replace the
> > source address inserted by the DMA engine.  Right now in PROM, we
> > rely on the networking code to use the address from the SEEP. 
> > 
> > Andy, do you know how the driver is working in Linux?  Does it setup
> > the MAC address for each packet or does it set the bit in the
> > descriptor to use the register value?
> 
> It gets it from the MAC.  What it does after that, I don't know, but
> that's the important part.  If I were going to implement the code to
> use the seep, I would just take the value in the seep and write it
> into the MAC, the end.  Might make your PROM networking code go a lot
> faster to do the same?  Just a thought.
> 
> > 
> > Brian
> > 
> > 
> > > -----Original Message-----
> > > From: Andy Sharp 
> > > Sent: Monday, October 29, 2007 4:35 PM
> > > To: Brian Stark; Rick Lund
> > > Subject: prom changes
> > > 
> > > Hello Boyeeeeez,
> > > 
> > > Just dropping a note to remind of the prom changes:
> > > 
> > > * Map the RTC space in.
> > > 
> > > * One of the following: program the mac addr into the 
> > > ethernet controller or get the argument/environment stuff 
> > > working.  Preferably the former.  Because the latter might 
> > > actually be a kernel issue.
> > > 
> > > Cheers,
> > > 
> > > a
> > > 
