Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
F
FMC Bus
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
1
Issues
1
List
Board
Labels
Milestones
Merge Requests
0
Merge Requests
0
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
FMC Bus
Commits
bb34638b
Commit
bb34638b
authored
Oct 15, 2012
by
Alessandro Rubini
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc: some typos (most fixed by Erik) and remove 1.0 release
Signed-off-by:
Alessandro Rubini
<
rubini@gnudd.com
>
parent
9c201c62
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
4 additions
and
4 deletions
+4
-4
fmc-bus.in
doc/fmc-bus.in
+4
-4
No files found.
doc/fmc-bus.in
View file @
bb34638b
...
...
@@ -40,7 +40,7 @@
@titlepage
@title FMC Bus Abstraction for Linux
@subtitle
Version 1.0,
@value
{
update-month
}
@subtitle @value
{
update-month
}
@subtitle A kernel bus to support FMC mezzanines and carriers
@author Alessandro Rubini for CERN (BE-CO-HT)
@end titlepage
...
...
@@ -61,7 +61,7 @@ I/O devices, in the context of White Rabbit and related hardware.
In our I/O environments we need to write drivers for each mezzanine
card, and such drivers must work independent of the carrier being used.
To achieve this, we abstract the FMC interface
To achieve this, we abstract the FMC interface
.
We have a carrier for PCI-E called @i
{
SPEC
}
and one for VME called
@i
{
SVEC
}
, but more are planned. Also, we support stand-alone devices
...
...
@@ -154,7 +154,7 @@ the current structure defining a device. Please note that all
the machinery is in place but some details may still change in the future.
For this reason, there is a version field at the beginning of the structure.
As usual, the minor number will change for compatible changes (like a new
flag) and the m
in
or number will increase when an incompatible change
flag) and the m
aj
or number will increase when an incompatible change
happens (for example, a change in layout of some @i
{
fmc
}
data structures).
Device writers should just set it to the
value @t
{
FMC
_
VERSION
}
, and be ready to get back @t
{
-EINVAL
}
at
...
...
@@ -233,7 +233,7 @@ The individual methods perform the following tasks:
These functions access FPGA registers by whatever means the
carrier offers. They are not expected to fail, and most of the time
they will just make a memory access to the host bus. If the
carrier provids a @i
{
base
}
pointer, the driver may use direct
carrier provid
e
s a @i
{
base
}
pointer, the driver may use direct
access through that pointer. For this reason the header offers
the inline functions @i
{
fmc
_
readl
}
and @i
{
fmc
_
writel
}
that
access @i
{
base
}
if the respective method is NULL. A driver that
...
...
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