Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
S
Software for White Rabbit PTP Core
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
32
Issues
32
List
Board
Labels
Milestones
Merge Requests
4
Merge Requests
4
CI / CD
CI / CD
Pipelines
Schedules
Wiki
Wiki
image/svg+xml
Discourse
Discourse
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Charts
Create a new issue
Commits
Issue Boards
Open sidebar
Projects
Software for White Rabbit PTP Core
Commits
97c2f4b9
Commit
97c2f4b9
authored
Nov 26, 2019
by
Grzegorz Daniluk
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc: improve description of packet class for the fabric interface
parent
c0ffd31c
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
12 additions
and
2 deletions
+12
-2
fabric.tex
doc/HDLdoc/fabric.tex
+12
-2
No files found.
doc/HDLdoc/fabric.tex
View file @
97c2f4b9
...
...
@@ -43,10 +43,20 @@ various information about Ethernet frame's structure and type:
it will be assigned from WRPC configuration)
\item
[]
\emph
{
vCRC
}
- the frame contains a valid CRC checksum
\item
[]
\emph
{
packet class
}
- the packet class assigned by the classifier
inside WRPC MAC module
inside WRPC MAC module
.
\end{itemize}
OOB data is used for passing the timestamp-related information for the incoming and
The packet class assigned by the classifier is one-hot encoded with 8 possible
values:
\textit
{
0x01
}
for class 0 to
\textit
{
0x80
}
for class 7. In its default
configuration WRPC assigns
{
\bf
class 0
}
(
\textit
{
0x01
}
) to all frames that shall be
processed inside the core (those are never exposed to the user through the
fabric interface);
{
\bf
class 7
}
(
\textit
{
0x80
}
to all Etherbone frames that are
either broadcast or unicast with matching destination MAC address;
{
\bf
class 6
}
(
\textit
{
0x40
}
) to all other traffic not qualified to any of the previous
classes.
\\
{
\bf
OOB data
}
is used for passing the timestamp-related information for the incoming and
outgoing Ethernet frames. Each frame received from a physical link is
timestamped inside the WRPC and this value is passed as Rx OOB
data. On the other hand, for each transmitted frame the Tx timestamp can be read
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment