Search results

Jump to: navigation, search

Page title matches

  • ...with ''printenv'' and ''setenv''. It can be helpful to read and set these variables from Linux as well. The U-Boot distribution has sources for these commands ...this file, you need to know information about where U-Boot stores its env variables. Specifically, you need the mtd device name, the device offset, the env si
    4 KB (582 words) - 08:38, 31 August 2012
  • == Part B – Using Built-in and User-Defined Variables == In this part, we will add some user-defined variables and built-in variables to simplify and help the makefile more readable. You will also have a chanc
    4 KB (767 words) - 12:26, 17 July 2012

Page text matches

  • ** apart from the buffer cache data itself also some other variables might need restoring
    28 KB (4,409 words) - 10:21, 18 May 2015
  • and making all variables static. These options are still supported by gcc, but not longer offered in
    17 KB (2,620 words) - 00:14, 27 September 2014
  • And finally the _text, _etext, _end and similar variables are now declared extern void instead of extern char, or even extern int. Th
    12 KB (1,858 words) - 09:57, 1 July 2014
  • ...program stack and also the argument strings to the program and environment variables that the program inherited. When setup_arg_pages() instantiates the new VM
    36 KB (6,111 words) - 19:23, 16 March 2015
  • -o causes target to output the required environment variables *use the -o option with "target setenv" to output the environment variables to a file, then source that file in the current environment
    24 KB (3,743 words) - 09:50, 12 December 2006
  • These set the config variables CONFIG_FASTBOOT and CONFIG_FASTBOOT_LPJ.
    17 KB (2,668 words) - 13:36, 7 August 2015
  • * Set environment variables for cross compile
    16 KB (2,346 words) - 17:44, 17 May 2010
  • *environment variables for script: {{{INPUT_DIR, RESULT_DIR, KERN_SRC}}} *environment variables for kernel building: {{{ARCH, CROSS_COMPILE, PATH}}}
    5 KB (714 words) - 05:44, 14 July 2007
  • # Dhrystone 2 using register variables
    2 KB (325 words) - 04:10, 10 August 2016
  • and set up your GIT variables (probably in ~/.bashrc)
    10 KB (1,734 words) - 13:57, 27 October 2011
  • ...fford to follow head, but fix package versions. The OE framework (bitbake, variables, behaviour) changes too much.
    7 KB (1,076 words) - 00:07, 21 June 2014
  • === Configuration variables === The patch introduces (or modifies) the following configuration variables:
    11 KB (1,613 words) - 08:15, 23 November 2015
  • Environment Variables ; ARCH :=arm , CROSS_COMPILER="your arm-toolchain directory"
    3 KB (376 words) - 01:39, 28 October 2011
  • DTrace gives you three built-in variables:
    14 KB (2,008 words) - 03:05, 27 October 2011
  • (1)Dhrystone 2 using register variables
    7 KB (1,159 words) - 12:57, 10 February 2008
  • ** or tftpboot (requires a tftp server and setting the environment variables ethaddr, ipaddr and serverip)
    4 KB (559 words) - 16:56, 15 April 2011
  • Before you can use the cross-compiler, its helpful to set up some environment variables (this will also depend on which shell you are using.) As I am using bash, I
    13 KB (2,110 words) - 12:27, 24 September 2007
  • * Global variables are declared as static, so are global within the file.
    6 KB (804 words) - 13:34, 27 October 2011
  • ...and downward through the called modules, you can isolate and preserve the variables unique to each recursive step and simply loop a given piece of code to achi
    54 KB (8,136 words) - 13:37, 12 April 2011
  • User program object code + user global variables: 16320 bytes available
    19 KB (3,082 words) - 03:38, 28 April 2012

View (previous 20 | next 20) (20 | 50 | 100 | 250 | 500)