Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
spec-sw
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Analyze
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
This is an archived project. Repository and other project resources are read-only.
fmc-projects
spec
spec-sw
Commits
ba06cc43
Commit
ba06cc43
authored
12 years ago
by
Alessandro Rubini
Browse files
Options
Downloads
Patches
Plain Diff
doc: trivial typos
parent
ab7810ae
Branches
Branches containing commit
Tags
Tags containing commit
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/fmc-bus.in
+2
-2
2 additions, 2 deletions
doc/fmc-bus.in
with
2 additions
and
2 deletions
doc/fmc-bus.in
+
2
−
2
View file @
ba06cc43
...
...
@@ -191,7 +191,7 @@ struct fmc_operations {
}
;
@end smallexample
The
y
perform the following tasks:
The
individual methods
perform the following tasks:
@table @code
@item readl
...
...
@@ -212,7 +212,7 @@ They perform the following tasks:
The carrier enumerates FMC devices by loading a standard (or
@i
{
golden
}
FPGA binary that allows EEPROM access. Each driver, then,
will need to reprogram the FPGA for its own use by calling this
function. If @i
{
reprogram
}
is called with NULL argument
e
s, the
function. If @i
{
reprogram
}
is called with NULL arguments, the
carrier will reprogram the golden binary -- which will happen
after @i
{
remove
}
time in any case.
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment