Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
S
Simple PCIe FMC carrier SPEC - Software
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
3
Issues
3
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
Simple PCIe FMC carrier SPEC - Software
Commits
9741856f
Commit
9741856f
authored
Jul 15, 2012
by
Alessandro Rubini
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
doc: document firmware comes from fmc/ (and submodule too)
Conflicts: doc/spec-sw.in
parent
b5701917
Show whitespace changes
Inline
Side-by-side
Showing
2 changed files
with
14 additions
and
6 deletions
+14
-6
spec-sw.in
doc/spec-sw.in
+13
-5
spec-core.c
kernel/spec-core.c
+1
-1
No files found.
doc/spec-sw.in
View file @
9741856f
...
...
@@ -159,27 +159,35 @@ at the default address (0x80000). IF you you pass a different value
than 1, it will be used as the load address (for example:
``@code
{
insmod lm32=0xc0000
}
'').
@b
{
Note:
}
all three files are looked-for in @i
{
/lib/firmware/fmc
}
,
because our own installations share firmware for COTS peripherals
but mount a host-specific NFS subdirectory. This is incompatible
with previous versions of this package, but the error message should
be clear enough for our users to sort the problem out. (Actually, I
tried to add a backward-compatible second choice, but it would have
messed up the code quite a lot).
The three files being looked for are named like this, assuming here
the card is seen under PCIe bus number 2:
@table @code
@item spec-B0002.bin
@item
fmc/
spec-B0002.bin
This is the name of the @i
{
gateware
}
file, which is looked-for
in @code
{
/lib/firmware
}
by the @i
{
hotplug
}
or @i
{
udev
}
program.
@item spec-B0002-cpu.bin
@item
fmc/
spec-B0002-cpu.bin
This is the program code for the embedded CPU. Again, it must
live in @code
{
/lib/firmware
}
live in @code
{
/lib/firmware
}
.
@item spec-B0002.ko
@item
fmc/
spec-B0002.ko
The kernel sub-module. It is loaded using @i
{
modprobe
}
, so
it should live in the same place where @code
{
spec.ko
}
is found.
Also, please run ``@code
{
depmod -a
}
'' after copying or renaming
the file
the file
.
@end table
...
...
kernel/spec-core.c
View file @
9741856f
...
...
@@ -50,7 +50,7 @@ static int spec_build_names(struct spec_dev *dev)
static
char
*
templates
[]
=
{
[
SPEC_NAME_FW
]
=
"fmc/spec-%s.bin"
,
[
SPEC_NAME_PROG
]
=
"fmc/spec-%s-cpu.bin"
,
/* will be .elf */
[
SPEC_NAME_SUBMOD
]
=
"spec-%s"
,
/* .ko added by modprobe */
[
SPEC_NAME_SUBMOD
]
=
"
fmc/
spec-%s"
,
/* .ko added by modprobe */
};
for
(
si
=
spec_name
,
so
=
basename
;
*
si
;
si
++
)
{
...
...
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