X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C82484.41EB0771@onstor-exch02.onstor.net>; Sun, 11 Nov 2007 08:59:44 -0800
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----_=_NextPart_001_01C82484.41EB0771"
References: <BB375AF679D4A34E9CA8DFA650E2B04E0103C4D8@onstor-exch02.onstor.net> <20071109182736.36098c23@ripper.onstor.net>
Content-class: urn:content-classes:message
Subject: RE: prom changes
Date: Sun, 11 Nov 2007 08:57:17 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E523472@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: prom changes
Thread-Index: AcgjQUGqXMJVkZgKTcq1fW0j6Gxx9QBQqihV
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>
Cc: "Rick Lund" <rick.lund@onstor.com>

This is a multi-part message in MIME format.

------_=_NextPart_001_01C82484.41EB0771
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Here's the MAC address that's present in that register while in PROM:
=20
Mac ethernet addr                 :00000100000c28001
=20
So either Linux is resetting the MAC address register from the one shown =
in your email or it's inserting the MAC on every packet that's being =
sent.  If it's the latter, then it's probably defaulting to that address =
since we're not passing it in from PROM.
=20

________________________________

From: Andy Sharp
Sent: Fri 11/9/2007 6:27 PM
To: Brian Stark
Cc: Rick Lund
Subject: Re: prom changes



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=20

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
> > >



------_=_NextPart_001_01C82484.41EB0771
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<HTML dir=3Dltr><HEAD><TITLE>Re: prom changes</TITLE>=0A=
<META http-equiv=3DContent-Type content=3D"text/html; charset=3Dunicode">=0A=
<META content=3D"MSHTML 6.00.2900.3199" name=3DGENERATOR></HEAD>=0A=
<BODY>=0A=
<DIV id=3DidOWAReplyText43708 dir=3Dltr>=0A=
<DIV dir=3Dltr><FONT face=3DArial color=3D#000000 size=3D2>Here's the =
MAC address that's present in that register while in PROM:</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>Mac ethernet =
addr&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nb=
sp;&nbsp;&nbsp;&nbsp;&nbsp; :00000100000c28001</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2>So either Linux is resetting =
the MAC address register from the one shown in your email or it's =
inserting&nbsp;the MAC&nbsp;on every packet that's being sent.&nbsp; If =
it's the latter, then it's probably defaulting to that address since =
we're not passing it in from PROM.</FONT></DIV>=0A=
<DIV dir=3Dltr><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV></DIV>=0A=
<DIV dir=3Dltr><BR>=0A=
<HR tabIndex=3D-1>=0A=
<FONT face=3DTahoma size=3D2><B>From:</B> Andy Sharp<BR><B>Sent:</B> Fri =
11/9/2007 6:27 PM<BR><B>To:</B> Brian Stark<BR><B>Cc:</B> Rick =
Lund<BR><B>Subject:</B> Re: prom changes<BR></FONT><BR></DIV>=0A=
<DIV>=0A=
<P><FONT size=3D2>My comments were written with full understanding of =
that.&nbsp; The short<BR>version: set the value in the MAC and Linux =
will take care of the rest.<BR><BR>Currently on the cougarz, the mac =
addr comes out like thus:<BR><BR>coolcat:~# =
ifconfig<BR>eth0&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Link encap:Ethernet&nbsp; =
HWaddr 40:00:00:00:01:00&nbsp;<BR><BR>Which I believe is what's sitting =
in the MAC when the linux driver gets<BR>to it.<BR><BR>On Fri, 9 Nov =
2007 18:09:05 -0800 "Brian Stark"<BR>&lt;brian.stark@onstor.com&gt; =
wrote:<BR><BR>&gt; It's not as simple as setting the mac addr =
register.&nbsp; The transmit<BR>&gt; descriptor needs to tell the =
ethernet engine to use the value in this<BR>&gt; register.&nbsp; Setting =
this bit in the descriptor has to be done in the<BR>&gt; driver, both =
the one in prom and =
linux...<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt;<BR>&gt; -----Original =
Message-----<BR>&gt; From: Andy Sharp<BR>&gt; To: Brian Stark<BR>&gt; =
CC: Rick Lund<BR>&gt; Sent: Fri Nov 09 17:56:23 2007<BR>&gt; Subject: =
Re: prom changes<BR>&gt;<BR>&gt; On Fri, 9 Nov 2007 17:38:41 -0800 =
"Brian Stark"<BR>&gt; &lt;brian.stark@onstor.com&gt; =
wrote:<BR>&gt;<BR>&gt; &gt; FYI, if we want to use the mac addr =
programmed into the SiByte MAC,<BR>&gt; &gt; then the transmit =
descriptor needs to be modified to replace the<BR>&gt; &gt; source =
address inserted by the DMA engine.&nbsp; Right now in PROM, we<BR>&gt; =
&gt; rely on the networking code to use the address from the =
SEEP.<BR>&gt; &gt;<BR>&gt; &gt; Andy, do you know how the driver is =
working in Linux?&nbsp; Does it setup<BR>&gt; &gt; the MAC address for =
each packet or does it set the bit in the<BR>&gt; &gt; descriptor to use =
the register value?<BR>&gt;<BR>&gt; It gets it from the MAC.&nbsp; What =
it does after that, I don't know, but<BR>&gt; that's the important =
part.&nbsp; If I were going to implement the code to<BR>&gt; use the =
seep, I would just take the value in the seep and write it<BR>&gt; into =
the MAC, the end.&nbsp; Might make your PROM networking code go a =
lot<BR>&gt; faster to do the same?&nbsp; Just a thought.<BR>&gt;<BR>&gt; =
&gt;<BR>&gt; &gt; Brian<BR>&gt; &gt;<BR>&gt; &gt;<BR>&gt; &gt; &gt; =
-----Original Message-----<BR>&gt; &gt; &gt; From: Andy Sharp<BR>&gt; =
&gt; &gt; Sent: Monday, October 29, 2007 4:35 PM<BR>&gt; &gt; &gt; To: =
Brian Stark; Rick Lund<BR>&gt; &gt; &gt; Subject: prom changes<BR>&gt; =
&gt; &gt;<BR>&gt; &gt; &gt; Hello Boyeeeeez,<BR>&gt; &gt; &gt;<BR>&gt; =
&gt; &gt; Just dropping a note to remind of the prom changes:<BR>&gt; =
&gt; &gt;<BR>&gt; &gt; &gt; * Map the RTC space in.<BR>&gt; &gt; =
&gt;<BR>&gt; &gt; &gt; * One of the following: program the mac addr into =
the<BR>&gt; &gt; &gt; ethernet controller or get the =
argument/environment stuff<BR>&gt; &gt; &gt; working.&nbsp; Preferably =
the former.&nbsp; Because the latter might<BR>&gt; &gt; &gt; actually be =
a kernel issue.<BR>&gt; &gt; &gt;<BR>&gt; &gt; &gt; Cheers,<BR>&gt; &gt; =
&gt;<BR>&gt; &gt; &gt; a<BR>&gt; &gt; =
&gt;<BR></FONT></P></DIV></BODY></HTML>
------_=_NextPart_001_01C82484.41EB0771--
