root/trunk/libffado/support/tools/ffado-diag.1

Revision 2811, 0.9 kB (checked in by jwoithe, 3 years ago)

Cosmetic: "firewire" should be "FireWire?" when used as the bus name.

Similarly to r2802 and r2810, "FireWire?" should be used when referring to
the name of the bus. This patch corrects this throughout the source tree
for completeness. While there are a small number of mostly debug output
strings affected, most of the changes are to comments or developer documents
where they are of little consequence. Thanks to Pander who suggested the
need to look into this on the ffado-devel mailing list.

At least in theory, remaining instances of "firewire" in the source tree
should remain as they are because they refer to case-sensitive identifiers
defined externally (such as the "firewire" jackd backend name).

Line 
1 .TH FFADO\-DIAG 1 27\-Mar\-2012 "ffado\-diag"
2 .SH NAME
3 ffado\-diag \- print system diagnostic information related to FFADO.
4 \"
5 .SH SYNOPSIS
6 .BR ffado\-diag [\| \-\-static \||\| \-V \||\| \-\-version \||\| \-\-usage \|]
7 \"
8 .SH DESCRIPTION
9 .B ffado\-diag
10 prints out an extensive collection of diagnostic information about the
11 computer it is run on.  Information included is the FFADO version number,
12 the version number of libraries which FFADO depends on, the FireWire
13 interface card, interrupt usage, and so on.  This is useful for developers
14 to know when giving support via the FFADO mailing lists.  For anything other
15 than trivial issues, the output of
16 .B ffado\-diag
17 will be one of the first things asked fro when debugging a problem.
18 \"
19 .SH OPTIONS
20 .BR \-V ", " \-\-version
21 Display version information.
22 .B \-\-usage
23 Print a short usage message and exit.
24 .B \-\-static
25 Only display executable paths and libraries.
Note: See TracBrowser for help on using the browser.