ethernet driver

[<fra...@ya...>]

Ok, I think I juste have to precise some few things :

My driver is a study on how using IP over 1394 with
less efforts.
For linux, my driver is a network driver that use
kernel ethernet
facilities. So I have keept ethernet packet headers
(and I use
it). With my solution, I avoid to rewrite the ARP
protocol for 1394
(I keep using the ethernet ARP protocol). But I had to
choose
arbitrary hardware addresses for my IEEE 1394 boards,
and I had to
build a very simple external protocol manage to found
which node got
which hardware address.

Moreover, I only uses unified write transactions to
transfer ethernet
packets. To do that, I have just added one line in
ieee1394_core.c
which prevent the write response paquet to be
transmitted while the
CSR address of the paquet recieved match with those my
driver is in
charge. Of course, I write a new unified write
transaction which
complete when the 1394 packet is transmitted by the
low-level device
driver. This solution save bandwidth but might be not
safe (the only
acknowledgment sent for a received paquet is the 1394
link layer 8 bit
ack). I think that TCP or other higher level protocol
can ensure data
integrity.


My driver work (more or less), but is not as general
as might be a
real implementation of IP over 1394 using (for
exemple) RFC 2734.


I will soon post my source code and report bugs that I
found.


Franck Bonin

___________________________________________________________
Do You Yahoo!?
Achetez, vendez! À votre prix! Sur http://encheres.yahoo.fr