OpenCores
URL https://opencores.org/ocsvn/fade_ether_protocol/fade_ether_protocol/trunk

Subversion Repositories fade_ether_protocol

[/] [fade_ether_protocol/] [trunk/] [stable_jumbo_frames_version/] - Rev 43

Rev

Go to most recent revision | Details | Compare with Previous | Blame

Filtering Options

Clear current filter

Rev Log message Author Age Path
22 Sources reorganized so, that each ".xci" is in a separate directory.
Added script for rebuilding of Vivado project for KC705.
Just run the build_proj_kc705 script, and the project
will be created as kc705_10g3.xpr in the kc705_10g3 drirectory.
You can open it later on in Vivado 2014.3 and build the bitstream.		 wzab 3529d 14h /fade_ether_protocol/trunk/stable_jumbo_frames_version
21 Changed the top entity for KC705, so that the FADE core is correctly reset
by the RESETMAC command.
Changed sending of the FCMD_RESET command form driver to the FPGA (as it
is not confirmed - the reinitialized core can't confirm the command).
Changed the receiver2t demo program so that it sends RESETMAC three times
before the transmission is started.

In the future, probably there should be a STATUS ioctl, which would
verify, that the core has been reset by RESETMAC.
Then the program should send RESETMAC, and afterwards read the STATUS,
verifying, that RESETMAC arrived FPGA. If not it should repeat the
above procedure (not implemented yet).		 wzab 3529d 21h /fade_ether_protocol/trunk/stable_jumbo_frames_version
20 Cured problem with dta_eod missed, when buffer was full at the moment
when dta_eod was asserted.
It caused the client program to hang, as no end of data was transmitted
and no new data arrived...		 wzab 3530d 12h /fade_ether_protocol/trunk/stable_jumbo_frames_version
19 The send_cmd function protected to attempt to call it if the Ethernet device was not
claimed before (previously it caused a problem with NULL pointer dereference
in the ioctl in kernel code).

Moved the Ethernet device name to a macro, so it is easier to modify it, when
someone tests in different machines (e.g. the 10Gb/s NIC for tests with
KC705 is p4p1, while 1Gb/s NIC for tests with Atlys is eth0)		 wzab 3530d 14h /fade_ether_protocol/trunk/stable_jumbo_frames_version
18 Changed handling of commands so, that all commands are now confirmed - even start and stop
(which previously were not confirmed - successful reception of start was confirmed
by sending of data packets (what if there was no data at the moment?), successful
reception of stop was confirmed by end of data stream).
Added also flushing of data stream after reception of stop command.
The receiver2t.c implements suggested method of communication with the FADE driver.
One thread is responsible for reception and processing of data, while another thread
is responsible for sending of control commands.		 wzab 3531d 10h /fade_ether_protocol/trunk/stable_jumbo_frames_version
17 Corrected mutex management in ioctl. wzab 3537d 14h /fade_ether_protocol/trunk/stable_jumbo_frames_version
16 Introduced inline functions simplifying reading and writing of packets' contents. wzab 3537d 15h /fade_ether_protocol/trunk/stable_jumbo_frames_version
15 The previous experimental implemenation for 10Gb/s links has been replaced with the
new, rewritten implementation, which uses sequential numbering of packets instaed
of "sets of packets". This allowed to simplify the driver, and improve its performance.
Additionally a possibility to send user defined commands to the FPGA was added.		 wzab 3545d 12h /fade_ether_protocol/trunk/stable_jumbo_frames_version

< Prev 1 2

Show All

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.