Skip to content
Projects
Groups
Snippets
Help
Loading...
Sign in
Toggle navigation
S
SDB - Self-describing Bus
Project
Project
Details
Activity
Cycle Analytics
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Charts
Issues
0
Issues
0
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
SDB - Self-describing Bus
Commits
af5c077e
Commit
af5c077e
authored
Oct 05, 2014
by
Alessandro Rubini
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
sdbfs/doc: document new sdb-read option (commit 088045d8)
Signed-off-by:
Alessandro Rubini
<
rubini@gnudd.com
>
parent
8d6417ea
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
15 additions
and
1 deletion
+15
-1
sdbfs.in
sdbfs/doc/sdbfs.in
+15
-1
No files found.
sdbfs/doc/sdbfs.in
View file @
af5c077e
...
...
@@ -516,7 +516,8 @@ to the use of relative addresses.
@section sdb-read
The @i
{
sdb-read
}
program can be used to access an @i
{
sdbfs
}
image
stored in a disk file. It works both as @i
{
ls
}
(to list the files
stored in a disk file or an FPGA area in physical memory.
It works both as @i
{
ls
}
(to list the files
included in the image) and as @i
{
cat
}
(to print to its own @i
{
stdout
}
one of the files that live in the binary image).
...
...
@@ -559,11 +560,24 @@ The following option flags are supported:
Specify the offset of the magic number in the image file.
@item -m <size>@@<addr>
@itemx -m <addr>+<size>
Either form is used to specify a memory range. This is the
preferred way to read from a memory-mapped area, like an FPGA
memory space. Please note that in general you should not
read a ``file'' in FPGA space, because this would mean read
all device registers. The form ``@t
{
<image-file> <filename>
}
''
is thus discouraged for in-memory SDB trees (i.e. where
@t
{
<image-file>
}
is @t
{
/dev/mem
}
).
@item -r
Register the device with a @i
{
read
}
method instead of the @i
{
data
}
pointer (@ref
{
The Filesystem Structure
}
). In this way the
tool can be used to test the library with either access method.
If @i
{
mmap
}
fails on the file (e.g., it is a non-mappable device),
@i
{
read
}
is used automatically, irrespective of @t
{
-r
}
.
@end table
...
...
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