1. 08 1月, 2009 5 次提交
    • A
      kconfig: add script to manipulate .config files on the command line · 8e54701e
      Andi Kleen 提交于
      I often change single options in .config files. Instead of using
      an editor or one of the frontends it's convenient to do this from
      the command line. It's also useful to do from automated build scripts
      when building different variants from a base config file.
      
      I extracted most of the CONFIG manipulation code from one of my
      build scripts into a new shell script scripts/config
      
      The script is not integrated with the normal Kconfig machinery
      and doesn't do any checking against Kconfig files, but just manipulates
      that text format. This is always done at make time anyways.
      
      I believe this script would be a useful standard addition for scripts/*
      
      Sample usage:
      
      ./scripts/config --disable smp
      Disable SMP in .config file
      
      ./scripts/config --file otherdir/.config --module e1000e
      Enable E1000E as module in otherdir/.config
      
      ./scripts/config --state smp
      y
      Check state of config option CONFIG_SMP
      
      After merging into git please make scripts/config executable
      Signed-off-by: NAndi Kleen <ak@linux.intel.com>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      8e54701e
    • J
      kbuild: reintroduce ALLSOURCE_ARCHS support for tags/cscope · 4f628248
      Jike Song 提交于
      This patch reintroduce the ALLSOURCE_ARCHS support for tags/TAGS/
      cscope targets. The Kbuild previously has this feature, but after
      moving the targets into scripts/tags.sh, ALLSOURCE_ARCHS disappears.
      
      It's something like this:
      
      	$ make ALLSOURCE_ARCHS="x86 mips arm" tags cscope
      Signed-off-by: NJike Song <albcamus@gmail.com>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      4f628248
    • A
      bootchart: improve output based on Dave Jones' feedback · 40c8c85a
      Arjan van de Ven 提交于
      Dave Jones, in his blog, had some feedback about the bootchart script:
      Primarily his complaint was that shorter delays weren't visualized.
      
      The reason for that was that too small delays will have their labels
      mixed up in the graph in an unreadable mess.
      
      This patch has a fix for this; for one, it makes the output wider,
      so more will fit.
      The second part is that smaller delays are now shown with a
      much smaller font for the label; while this isn't per se
      readable at a 1:1 zoom, at least you can zoom in with most SVG
      viewing applications and see what it is you are looking at.
      Signed-off-by: NArjan van de Ven <arjan@linux.intel.com>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      40c8c85a
    • S
      fix modules_install via NFS · 8b249b68
      Sam Ravnborg 提交于
      Rafael reported:
      
      I get the following error from 'make modules_install' on my test boxes:
      
        HOSTCC  firmware/ihex2fw
      /home/rafael/src/linux-2.6/firmware/ihex2fw.c:268: fatal error: opening dependency file firmware/.ihex2fw.d: Read-only file system
      compilation terminated.
      make[3]: *** [firmware/ihex2fw] Error 1
      make[2]: *** [_modinst_post] Error 2
      make[1]: *** [sub-make] Error 2
      make: *** [all] Error 2
      
      where the configuration is that the kernel is compiled on a build box
      with 'make O=<destdir> -j5' and then <destdir> is mounted over NFS read-only by
      each test box (full path to this directory is the same on the build box and on
      the test boxes).  Then, I cd into <destdir>, run 'make modules_install' and get
      the error above.
      
      The issue turns out to be that we when we install firmware pick
      up the list of firmware blobs from firmware/Makefile.
      And this triggers the Makefile rules to update ihex2fw.
      
      There were two solutions for this issue:
      1) Move the list of firmware blobs to a separate file
      2) Avoid ihex2fw rebuild by moving it to scripts
      
      As I seriously beleive that the list of firmware blobs should be
      done in a fundamental different way solution 2) was selected.
      Reported-and-tested-by: N"Rafael J. Wysocki" <rjw@sisk.pl>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Cc: David Woodhouse <dwmw2@infradead.org>
      8b249b68
    • A
      qnx: include <linux/types.h> for definitions of __[us]{8,16,32,64} types · 8d1a0a13
      Anders Larsen 提交于
      On 2008-12-30 11:32:33, Sam Ravnborg wrote:
      > We have added a few additional validation checks of the userspace headers:
      ...
      > 3) We should include <linux/types.h> and not <asm/types.h>
      > 4) If we use a __[us]{8,16,32,64} type then we must include <linux/types.h>
      
      Satisfy these requirements for the linux/qnx*.h headers.
      Signed-off-by: NAnders Larsen <al@alarsen.net>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      8d1a0a13
  2. 07 1月, 2009 35 次提交