No | -Direction | -Function | -Reset | -Set | -
8 | -Output | -Switch Audio Amplifier | -Off | -On | -
11 | -Input | -Head Phone Detection | -TBD | -TBD | -
14 | -Input | -Unused (J113) | -User | -User | -
15 | -Input | -Unused (J114) | -User | -User | -
26 | -Output | -USB Power | -TBD | -TBD | -
27 | -Input | -Display Connected | -Display Attached |
- Display Disconnected |
-
29 | -Output | -USB HUB Reset | -TBD | -TBD | -
50 | -Output | -Display Reset | -Display Reset |
- Display Running |
-
60 | -Output | -Display Backlight | -Backlight Off |
- Backlight On (100 %) |
-
62 | -Input | -Bend | -Not pressed | -Pressed | -
Barebox contains a small text editor which can be used to edit -config files in /env. You can move the cursor around with the arrow keys -and type characters.
- -If called as sedit, the editor uses ansi codes to scroll the screen. - */ - BAREBOX_CMD_START(edit) .cmd = do_edit, .aliases = edit_aliases, @@ -568,4 +553,3 @@ BAREBOX_CMD_START(edit) BAREBOX_CMD_GROUP(CMD_GRP_CONSOLE) BAREBOX_CMD_HELP(cmd_edit_help) BAREBOX_CMD_END - diff --git a/commands/flash.c b/commands/flash.c index b50a32702..99d3cb7c3 100644 --- a/commands/flash.c +++ b/commands/flash.c @@ -19,11 +19,6 @@ * */ -/** - * @file - * @brief Flash memory support: erase, protect, unprotect - */ - #includeErase the flash memory handled by this device. Which area will be -erased depends on the device: If the device represents the whole flash -memory, the whole memory will be erased. If the device represents a -partition on a main flash memory, only this partition part will be -erased.
- -Refer to \ref addpart_command, \ref delpart_command and \ref -devinfo_command for partition handling. - - */ - static int do_protect(int argc, char *argv[]) { int fd; @@ -173,23 +154,6 @@ BAREBOX_CMD_START(protect) BAREBOX_CMD_HELP(cmd_protect_help) BAREBOX_CMD_END -/** - * @page protect_command - - -If the device represents the whole -flash memory the whole memory will be protected. If the device -represents a partition on a main flash memory, only this partition part -will be protected. - -Refer addpart_command, delpart_command and devinfo_command for partition -handling. - -\todo Rework this documentation, what is an 'area'? Explain more about -flashes here. - - */ - BAREBOX_CMD_HELP_START(unprotect) BAREBOX_CMD_HELP_TEXT("Unprotect the flash memory behind the device. It depends on the device") BAREBOX_CMD_HELP_TEXT("given, what area will be unprotected. If the device represents the whole") @@ -205,19 +169,3 @@ BAREBOX_CMD_START(unprotect) BAREBOX_CMD_GROUP(CMD_GRP_HWMANIP) BAREBOX_CMD_HELP(cmd_unprotect_help) BAREBOX_CMD_END - -/** - * @page unprotect_command - -It depends on the device given, -what area will be unprotected. If the device represents the whole flash memory -the whole memory will be unprotected. If the device represents a partition -on a main flash memory, only this partition part will be unprotected. - -Refer addpart_command, delpart_command and devinfo_command for partition -handling. - -\todo Rework this documentation, what does it mean? - - */ - diff --git a/commands/gpio.c b/commands/gpio.c index 4f2d93ee7..08ecc152d 100644 --- a/commands/gpio.c +++ b/commands/gpio.c @@ -107,65 +107,3 @@ BAREBOX_CMD_START(gpio_direction_output) BAREBOX_CMD_OPTS("GPIO VALUE") BAREBOX_CMD_GROUP(CMD_GRP_HWMANIP) BAREBOX_CMD_END - -/** - * @page gpio_for_users GPIO Handling - -@section regular_gpio General usage information - -These commands are available if the symbol @b CONFIG_GENERIC_GPIO and @b -CONFIG_CMD_GPIO are enabled in Kconfig. - -@note All gpio related commands take a number to identify the pad. This -number is architecture dependent and may not directly correlate with the -pad numbers. Due to this, it is also possible that the numbers changes -between @b barebox releases. - -@section gpio_dir_out Use Pad as GPIO Output -@verbatim -# gpio_direction_outputTo avoid glitches on the pad the routines will first set up the -pad's value and afterwards switch the pad to output (if the silicon is -able to do so). If the pad is already configured in non-GPIO mode (if -available), this command may silently fail.
- -@section gpio_dir_in Use Pad as GPIO Input -@verbatim -# gpio_direction_inputIf the pad is already configured in non-GPIO mode (if available), -this command may silently fail.
- -@section gpio_get_value Read Input Value from GPIO Pin -@verbatim -# gpio_get_valueReads the current value of a GPIO pin and return the value as a -shell return code. There is no visible output on stdout. You can check -the return value by using "echo $?".
- -A return code other than '0' or '1' specifies an error code.
- -If the pad is not configured in GPIO mode, this command may silently -fail and return garbage.
- -@section gpio_set_value Set Output Value on GPIO Pin -@verbatim -# gpio_set_value Set a new output value on pad with GPIO number \
If the pad is not configured in GPIO-mode, this command may silently -fail.
- -*/ diff --git a/commands/led.c b/commands/led.c index 62c72a331..354f74df8 100644 --- a/commands/led.c +++ b/commands/led.c @@ -70,15 +70,6 @@ static int do_led(int argc, char *argv[]) return 0; } -/** - * @page led_command - -The exact meaning ofOnly kernel images in bzImage format are supported by now. See \ref -x86_boot_preparation for more info about how to use this command.
- -For the video mode refer the Linux kernel documentation -'Documentation/fb/vesafb.txt' for correct VESA mode numbers. If the keyword -'ask' instead of a number is given, the starting kernel will ask for a number. -
- */ - BAREBOX_CMD_START(linux16) .cmd = do_linux16, BAREBOX_CMD_DESC("boot a linux kernel on x86 via real-mode code") @@ -349,57 +337,3 @@ BAREBOX_CMD_START(linux16) BAREBOX_CMD_GROUP(CMD_GRP_BOOT) BAREBOX_CMD_HELP(cmd_linux16_help) BAREBOX_CMD_END - -/** - * @file - * @brief Boot support for Linux on x86 - */ - -/** - * @page x86_boot_preparation Linux Preparation on x86 - * - * Due to some real mode constraints, starting Linux is somehow tricky. - * Currently only @p bzImages are supported, because @p zImages would - * interfere with the @a barebox runtime. - * Also older load header versions than 2.00 aren't supported. - * - * The memory layout immediately before starting the Linux kernel: - * -@verbatim - real mode space hole extended memory - |---------------------------------------------->|----------->|------------------------------> - 0 0x7e00 0x90000 0xa0000 0x100000 - <-1-|----------2-----------><-3- | - <-4--|-5--> |---------6-------------> -@endverbatim - * - * @li 1 = @a barebox's real mode stack - * @li 2 = @a barebox's code - * @li 3 = @a barebox's flat mode stack - * @li 4 = real mode stack, when starting the Linux kernel - * @li 5 = Kernel's real mode setup code - * @li 6 = compressed kernel image - * - * A more detailed memory layout for kernel's real mode setup code - * -@verbatim - - 0x90000 0x97fff 0x99000 0x990ff - ---|------------------------------------------|----------------|--------------------| - |<-------- max setup code size ----------->|<--heap/stack-->|<-- command line -->| - -@endverbatim - * - * The regular entry point into the setup code is 0x90200 (2nd sector) - * - * To start the kernel, it's own setup code will be called. To do so, it - * must be called in real mode. So, @a barebox switches back to real mode - * a last time and does a jump to the setup code entry point. Now its up to - * the setup code to deflate the kernel, switching to its own protected mode - * setup and starting the kernel itself. - * - * @note This scenario only works, if a BIOS is still present. In this case - * there is no need for @a barebox to forward any system related information - * to the kernel. Everything is detected by kernel's setup code. - * - */ diff --git a/commands/loadenv.c b/commands/loadenv.c index ba9261339..8b15af49d 100644 --- a/commands/loadenv.c +++ b/commands/loadenv.c @@ -112,15 +112,6 @@ BAREBOX_CMD_HELP_OPT("-s", "scrub old environment") BAREBOX_CMD_HELP_OPT("-d", "load default environment") BAREBOX_CMD_HELP_END -/** - * @page loadenv_command - -ENVFS can only handle files, directories are skipped silently. - -\todo This needs proper documentation. What is ENVFS, why is it FS etc. Explain the concepts. - - */ - BAREBOX_CMD_START(loadenv) .cmd = do_loadenv, BAREBOX_CMD_DESC("load environment from ENVFS") diff --git a/commands/miitool.c b/commands/miitool.c index b08be9c68..40e34e93c 100644 --- a/commands/miitool.c +++ b/commands/miitool.c @@ -293,12 +293,6 @@ BAREBOX_CMD_HELP_TEXT("Options:") BAREBOX_CMD_HELP_OPT("-v", "increase verbosity") BAREBOX_CMD_HELP_END -/** - * @page miitool_command -This utility checks or sets the status of a network interface's -Media Independent Interface (MII) unit. Most fast ethernet -adapters use an MII to autonegotiate link speed and duplex setting. - */ BAREBOX_CMD_START(miitool) .cmd = do_miitool, BAREBOX_CMD_DESC("view media-independent interface status") diff --git a/commands/mount.c b/commands/mount.c index 7aa155edb..939e9bc85 100644 --- a/commands/mount.c +++ b/commands/mount.c @@ -17,11 +17,6 @@ * */ -/** - * @file - * @brief Filesystem mounting support - */ - #includeIf an argument is given, printenv prints the content of an environment -variable to the terminal. If no argument is specified, all variables are -printed.
- - */ - BAREBOX_CMD_START(printenv) .cmd = do_printenv, BAREBOX_CMD_DESC("print value of environment variables") diff --git a/commands/saveenv.c b/commands/saveenv.c index d629a94c5..54b6fa1b7 100644 --- a/commands/saveenv.c +++ b/commands/saveenv.c @@ -15,11 +15,6 @@ * */ -/** - * @file - * @brief saveenv: Make the environment persistent - */ - #include\
This command is only available if the simple command line parser is -in use. Within the hush shell, \c setenv is not required.
- - */ - BAREBOX_CMD_START(setenv) .cmd = do_setenv, BAREBOX_CMD_DESC("set environment variable") diff --git a/commands/splash.c b/commands/splash.c index c61a1d76a..5d0c0ad18 100644 --- a/commands/splash.c +++ b/commands/splash.c @@ -89,17 +89,6 @@ BAREBOX_CMD_HELP_OPT ("-b COLOR", "background color in 0xttrrggbb") BAREBOX_CMD_HELP_OPT ("-o\t", "render offscreen") BAREBOX_CMD_HELP_END -/** - * @page bmp_command - -This command displays a graphics in the bitmap (.bmp) format on the -framebuffer. Currently the bmp command supports images with 8 and 24 bit -color depth. - -\todo What does the -o (offscreen) option do? - - */ - BAREBOX_CMD_START(splash) .cmd = do_splash, BAREBOX_CMD_DESC("display a BMP image") diff --git a/commands/usbserial.c b/commands/usbserial.c index 1c26246f7..e4c2f1802 100644 --- a/commands/usbserial.c +++ b/commands/usbserial.c @@ -92,10 +92,6 @@ BAREBOX_CMD_HELP_OPT ("-s", "Generic Serial") BAREBOX_CMD_HELP_OPT ("-d", "Disable the serial gadget") BAREBOX_CMD_HELP_END -/** - * @page usbserial_command - */ - BAREBOX_CMD_START(usbserial) .cmd = do_usbserial, BAREBOX_CMD_DESC("serial gadget enable/disable") diff --git a/common/kallsyms.c b/common/kallsyms.c index 121b77cc8..53e22cdc7 100644 --- a/common/kallsyms.c +++ b/common/kallsyms.c @@ -3,8 +3,6 @@ #include