X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7B1EB.8D923626@onstor-exch02.onstor.net>; Mon, 18 Jun 2007 12:59:25 -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: eee protocol and mgmt-bus driver - checkin 1
Date: Mon, 18 Jun 2007 12:59:25 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E043606BC@onstor-exch02.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E032587E3@onstor-exch02.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: eee protocol and mgmt-bus driver - checkin 1
Thread-Index: AcevkdcRlPL+nbdVTsaaFkfNz5sYdwCVsTLdAABbIeA=
References: <BB375AF679D4A34E9CA8DFA650E2B04E042A5370@onstor-exch02.onstor.net> <BB375AF679D4A34E9CA8DFA650E2B04E032587E3@onstor-exch02.onstor.net>
From: "Maxim Kozlovsky" <maxim.kozlovsky@onstor.com>
To: "Richard Beck" <richard.beck@onstor.com>
Cc: "Larry Scheer" <larry.scheer@onstor.com>,
	"Andy Sharp" <andy.sharp@onstor.com>

Bobcat-config - no change

linux/kernel/linux-mips-2.6/net/Kconfig - modified but is not part of
the change

I don't think the changes to linux/kernel/Makefile are right, there
should be some common method to get the kernel includes in the right
place. Nevermind, we'll let Larry figure this out.

Eee.h -=20

4: This will not compile, there is no nfx-types.h in this change.

Where is the change that enables CONFIG_NETEEE and CONFIG_MGMT_BUS?


-----Original Message-----
From: Richard Beck=20
Sent: Monday, June 18, 2007 1:43 PM
To: Maxim Kozlovsky
Cc: Larry Scheer
Subject: eee protocol and mgmt-bus driver - checkin 1

Max,

Checkin #1 is in:
p4 client:  richardb-linux
changelist: 24262

Changes for items 2 & 3 will be checked in later today.
--Rich

-----Original Message-----
From: Maxim Kozlovsky
Sent: Fri 6/15/2007 2:12 PM
To: Richard Beck; Tim Gardner; Andy Sharp
Subject: Next steps for eee protocol and mgmt-bus driver.
=20
Hello Richard,

Here is how I want us to proceed for the rest of your stay with us. I
don't expect that you (or any other person) will be able to have
complete debugged implementation of EEE protocol and the management bus
driver in a week. I would like to get checked in as much as possible of
code that we all agree works and passes some tests. On the other hand, I
don't really need the code that is not known to work since it will
probably be easier for us to start over than to do the debugging for
you. To accomplish that, I'd like to do the checkins and reviews in
steps. I will be always available to do the review in the regular
working hours and will do the review as fast as possible so you are not
slowed down by multiple reviews. I hope Andy will help as well.

Here is the list of the steps together with the exit criteria:

1)	Check in the kernel configuration changes with empty .c and .h
files. After these changes, the kernel make in the kernel directory
should compile the neteee and mgmt bus driver .c files. The
corresponding .h files should be installed in the appropriate place in
/usr/include/neteee as part of the build process.
2)	Check in the changes that add AF_EEE/PF_EEE protocol family.
After these changes, we should be able to create sockets with
socket(PF_EEE, SOCK_DGRAM, 0).
3)	Check in the changes that add the sockaddr_eee. After these
changes the following tests should pass:
a)	Bind a socket to a specified address
b)	Negative test for binding a socket with the same address as
another socket
c)	Negative test for binding a socket to invalid address
d)	Bind a socket to ADDR_ANY - should pickup the next available
address in reserved range
e)	Test to make sure the address is available again after bound
socket is closed
4)	Check in the changes to support connect call for AF_EEE sockets.
Should pass positive tests and negative tests for invalid address.
5)	Check in the code to support send and receive on the loopback
interfaces. Should pass simple client/server tests for SSC applications
only.
6)	Check in the code that registers the mgmtbus driver as the
network driver. Put just minimal amount of the code to make it
recognizable to the linux kernel, the input/output routines should do
nothing and just drop the packets. After that we expect to do ifconfig
on this device and assign ip and eee addresses to it.
7)	Check in the code for sending and receiving the packets through
the mgmt bus driver. The simple client/server tests between the
applications on txrx, fp, fc and ssc should pass.
8)	Check in the code to support fragmentation. The tests for
sending large packets between ssc and embedded cards should pass.
9)	Check in the code for IP forwarding. We will not be able to test
this part without a lot of other system running.

Max



