28 Jan, 2008

2 commits

  • * orion: (26 commits)
    [ARM] Orion: implement power-off method for QNAP TS-109/209
    [ARM] Orion: add support for QNAP TS-109/TS-209
    [ARM] Orion: I2C support
    [I2C] i2c-mv64xxx: Don't set i2c_adapter.retries
    [I2C] Split mv643xx I2C platform support
    [ARM] Orion: enable CONFIG_RTC_DRV_M41T80 for D-Link DNS-323
    [ARM] Orion defconfig
    [ARM] Orion: add support for Orion/MV88F5181 based D-Link DNS-323
    [ARM] Orion: MV88F5181 support bits
    [ARM] Orion: Buffalo/Revogear Kurobox Pro support
    [ARM] OrionNAS RD board support
    [ARM] Orion: support for Marvell Orion-2 (88F5281) Development Board
    [ARM] Orion: common platform setup for Gigabit Ethernet port
    [ARM] Orion: platform device registration for UART, USB and NAND
    [ARM] Orion: system timer support
    [ARM] Orion edge GPIO IRQ support
    [ARM] Orion: IRQ support
    [ARM] Orion: provide GPIO method for enabling hardware assisted blinking
    [ARM] Orion: GPIO support
    [ARM] Orion: programable address map support
    ...

    Conflicts:

    arch/arm/Kconfig
    arch/arm/Makefile

    Signed-off-by: Russell King

    Russell King
     
  • This patch contains the scheduled removal of legacy I2C RTC drivers with
    replacement drivers.

    Signed-off-by: Adrian Bunk
    Signed-off-by: Jean Delvare

    Adrian Bunk
     

26 Jan, 2008

1 commit

  • I2C adapter drivers are supposed to handle retries on nack by themselves
    if they do, so there's no point in setting .retries if they don't.

    As this retry mechanism is going away (at least in its current form),
    clean this up now so that we don't get build failures later.

    Signed-off-by: Jean Delvare
    Acked-by: Mark A. Greer

    Jean Delvare
     

25 Jan, 2008

2 commits

  • All kobjects require a dynamically allocated name now. We no longer
    need to keep track if the name is statically assigned, we can just
    unconditionally free() all kobject names on cleanup.

    Signed-off-by: Kay Sievers
    Signed-off-by: Greg Kroah-Hartman

    Kay Sievers
     
  • : Stefan Roese said:
    > ppc: 4xx: sysctl table check failed: /kernel/l2cr .1.31 Missing strategy
    >
    > I'm seeing this error message when booting an recent arch/ppc kernel on
    > 4xx platforms (tested on Ocotea and other 4xx platforms). Booting NFS
    > rootfs still works fine, but this message kind of makes me "nervous".
    > This is not seen on 4xx arch/powerpc platforms. Here the bootlog:

    Because the data field was never filled and a binary sysctl handler was
    never written this sysctl has never been usable through the sys_sysctl
    interface. So just remove the binary sysctl number. Making the kernel
    sanity checks happy.

    Signed-off-by: Eric W. Biederman
    Reported-by: Stefan Roese
    Cc: Josh Boyer
    Cc: Wolfgang Denk
    Cc: Paul Mackerras
    Cc: Benjamin Herrenschmidt
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Eric W. Biederman
     

07 Dec, 2007

1 commit


03 Dec, 2007

1 commit


20 Nov, 2007

2 commits


19 Nov, 2007

3 commits


13 Nov, 2007

1 commit

  • The context switch code in the kernel issues a dummy stwcx. to clear the
    reservation, as recommended by the architecture. However, some processors
    can have issues if this stwcx to address A occurs while the reservation
    is already held to a different address B. To avoid this problem, the dummy
    stwcx. needs to be paired with a dummy lwarx to the same address.

    This adds the dummy lwarx, and creates a cpu feature bit to indicate
    which cpus are affected. Tested on mpc8641_hpcn_defconfig in
    arch/powerpc; build tested in arch/ppc.

    Signed-off-by: Becky Bruce
    Signed-off-by: Paul Mackerras

    Becky Bruce
     

08 Nov, 2007

3 commits

  • …/powerpc-4xx into merge

    Paul Mackerras
     
  • Since commit 76d2160147f43f982dfe881404cfde9fd0a9da21, the NE2000 card
    is not working anymore on PPC and POWERPC and produces WATCHDOG
    timeouts.

    The patch below fixes that the same way it has been done on x86, x86_64
    and MIPS.

    Signed-off-by: Aurelien Jarno
    Signed-off-by: Paul Mackerras

    Aurelien Jarno
     
  • Fix build break and warnings in current mainline git:

    arch/ppc/syslib/m8260_setup.c: In function 'm8260_setup_arch':
    arch/ppc/syslib/m8260_setup.c:63: error: implicit declaration of function 'identify_ppc_sys_by_name_and_id'
    arch/ppc/syslib/m8260_setup.c:64: warning: passing argument 1 of 'in_be32' makes pointer from integer without a cast
    arch/ppc/syslib/m8260_setup.c: In function 'm8260_show_cpuinfo':
    arch/ppc/syslib/m8260_setup.c:158: warning: format '%08x' expects type 'unsigned int', but argument 5 has type 'long unsigned int'
    arch/ppc/syslib/m8260_setup.c:158: warning: format '%d' expects type 'int', but argument 6 has type 'long unsigned int'
    arch/ppc/syslib/m8260_setup.c:158: warning: format '%u' expects type 'unsigned int', but argument 7 has type 'long unsigned int'
    arch/ppc/syslib/m8260_setup.c:158: warning: format '%u' expects type 'unsigned int', but argument 8 has type 'long unsigned int'
    arch/ppc/syslib/m8260_setup.c:158: warning: format '%u' expects type 'unsigned int', but argument 9 has type 'long unsigned int'
    make[1]: *** [arch/ppc/syslib/m8260_setup.o] Error 1
    make[1]: *** Waiting for unfinished jobs....

    Signed-off-by: Olof Johansson
    Signed-off-by: Paul Mackerras

    Olof Johansson
     

01 Nov, 2007

4 commits

  • mmu_mapin_ram() loops over total_lowmem to setup page tables. However, if
    total_lowmem is less that 16M, the subtraction rolls over and results in
    a number just under 4G (because total_lowmem is an unsigned value).

    This patch rejigs the loop from countup to countdown to eliminate the
    bug.

    Special thanks to Magnus Hjorth who wrote the original patch to fix this
    bug. This patch improves on his by making the loop code simpler (which
    also eliminates the possibility of another rollover at the high end)
    and also applies the change to arch/powerpc.

    Signed-off-by: Grant Likely
    Signed-off-by: Josh Boyer

    Grant Likely
     
  • The 44x family has an interesting "feature" which is a virtually
    tagged instruction cache (yuck !). So far, we haven't dealt with
    it properly, which means we've been mostly lucky or people didn't
    report the problems, unless people have been running custom patches
    in their distro...

    This is an attempt at fixing it properly. I chose to do it by
    setting a global flag whenever we change a PTE that was previously
    marked executable, and flush the entire instruction cache upon
    return to user space when that happens.

    This is a bit heavy handed, but it's hard to do more fine grained
    flushes as the icbi instruction, on those processor, for some very
    strange reasons (since the cache is virtually mapped) still requires
    a valid TLB entry for reading in the target address space, which
    isn't something I want to deal with.

    Signed-off-by: Benjamin Herrenschmidt
    Signed-off-by: Josh Boyer

    Benjamin Herrenschmidt
     
  • On 4xx CPUs, the current implementation of flush_tlb_page() uses
    a low level _tlbie() assembly function that only works for the
    current PID. Thus, invalidations caused by, for example, a COW
    fault triggered by get_user_pages() from a different context will
    not work properly, causing among other things, gdb breakpoints
    to fail.

    This patch adds a "pid" argument to _tlbie() on 4xx processors,
    and uses it to flush entries in the right context. FSL BookE
    also gets the argument but it seems they don't need it (their
    tlbivax form ignores the PID when invalidating according to the
    document I have).

    Signed-off-by: Benjamin Herrenschmidt
    Acked-by: Kumar Gala
    Signed-off-by: Josh Boyer

    Benjamin Herrenschmidt
     
  • Don't allocate hose2 when when hose1 can't be allocated and free hose1 when
    hose2 can't be allocated.

    Signed-off-by: Roel Kluin
    Signed-off-by: Josh Boyer

    Roel Kluin
     

21 Oct, 2007

1 commit

  • Commit 9a39e273d4df0560c724c5fe71f6314a0583ca2b removed the boot directory
    addition to CFLAGS that was being used by the subdirectory builds. For the
    other files, that patch set EXTRA_CFLAGS, but Makefile.build explicitly
    sets that to empty as it is explicitly for a single directory only.
    Append to KBUILD_CFLAGS instead.

    Signed-off-by: Milton Miller
    Signed-off-by: Sam Ravnborg

    Milton Miller
     

20 Oct, 2007

3 commits

  • Quoting Randy:

    "It seems sad that this patch sources Kconfig.marker, a 7-line file,
    20-something times. Yes, you (we) don't want to put those 7 lines into
    20-something different files, so sourcing is the right thing.

    However, what you did for avr32 seems more on the right track to me: make
    _one_ Instrumentation support menu that includes PROFILING, OPROFILE, KPROBES,
    and MARKERS and then use (source) that in all of the arches."

    Signed-off-by: Mathieu Desnoyers
    Acked-by: Randy Dunlap
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Mathieu Desnoyers
     
  • define global BIT macro

    move all local BIT defines to the new globally define macro.

    Signed-off-by: Jiri Slaby
    Cc: Paul Mackerras
    Cc: Benjamin Herrenschmidt
    Cc: Kumar Gala
    Cc: Dmitry Torokhov
    Cc: Jeff Garzik
    Cc: James Bottomley
    Cc: "Antonino A. Daplas"
    Cc: Russell King
    Acked-by: Ralf Baechle
    Cc: "John W. Linville"
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Jiri Slaby
     
  • is_init() is an ambiguous name for the pid==1 check. Split it into
    is_global_init() and is_container_init().

    A cgroup init has it's tsk->pid == 1.

    A global init also has it's tsk->pid == 1 and it's active pid namespace
    is the init_pid_ns. But rather than check the active pid namespace,
    compare the task structure with 'init_pid_ns.child_reaper', which is
    initialized during boot to the /sbin/init process and never changes.

    Changelog:

    2.6.22-rc4-mm2-pidns1:
    - Use 'init_pid_ns.child_reaper' to determine if a given task is the
    global init (/sbin/init) process. This would improve performance
    and remove dependence on the task_pid().

    2.6.21-mm2-pidns2:

    - [Sukadev Bhattiprolu] Changed is_container_init() calls in {powerpc,
    ppc,avr32}/traps.c for the _exception() call to is_global_init().
    This way, we kill only the cgroup if the cgroup's init has a
    bug rather than force a kernel panic.

    [akpm@linux-foundation.org: fix comment]
    [sukadev@us.ibm.com: Use is_global_init() in arch/m32r/mm/fault.c]
    [bunk@stusta.de: kernel/pid.c: remove unused exports]
    [sukadev@us.ibm.com: Fix capability.c to work with threaded init]
    Signed-off-by: Serge E. Hallyn
    Signed-off-by: Sukadev Bhattiprolu
    Acked-by: Pavel Emelianov
    Cc: Eric W. Biederman
    Cc: Cedric Le Goater
    Cc: Dave Hansen
    Cc: Herbert Poetzel
    Cc: Kirill Korotaev
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Serge E. Hallyn
     

17 Oct, 2007

4 commits

  • Paul Mackerras
     
  • Instead of having in the makefile all the option that
    requires rheap, we define a configuration symbol
    and when needed we make sure it's selected.

    Signed-off-by: Sylvain Munaut
    Signed-off-by: Grant Likely

    Sylvain Munaut
     
  • * git://git.kernel.org/pub/scm/linux/kernel/git/sam/kbuild: (40 commits)
    kbuild: introduce ccflags-y, asflags-y and ldflags-y
    kbuild: enable 'make CPPFLAGS=...' to add additional options to CPP
    kbuild: enable use of AFLAGS and CFLAGS on commandline
    kbuild: enable 'make AFLAGS=...' to add additional options to AS
    kbuild: fix AFLAGS use in h8300 and m68knommu
    kbuild: check for wrong use of CFLAGS
    kbuild: enable 'make CFLAGS=...' to add additional options to CC
    kbuild: fix up CFLAGS usage
    kbuild: make modpost detect unterminated device id lists
    kbuild: call export_report from the Makefile
    kbuild: move Kai Germaschewski to CREDITS
    kconfig/menuconfig: distinguish between selected-by-another options and comments
    kconfig: tristate choices with mixed tristate and boolean values
    include/linux/Kbuild: remove duplicate entries
    kbuild: kill backward compatibility checks
    kbuild: kill EXTRA_ARFLAGS
    kbuild: fix documentation in makefiles.txt
    kbuild: call make once for all targets when O=.. is used
    kbuild: pass -g to assembler under CONFIG_DEBUG_INFO
    kbuild: update _shipped files for kconfig syntax cleanup
    ...

    Fix up conflicts in arch/um/sys-{x86_64,i386}/Makefile manually.

    Linus Torvalds
     
  • We have had complaints where a threaded application is left in a bad state
    after one of it's threads is killed when we hit a VM: out_of_memory
    condition.

    Killing just one of the process threads can leave the application in a bad
    state, whereas killing the entire process group would allow for the
    application to restart, or be otherwise handled, and makes it very obvious
    that something has gone wrong.

    This change allows the entire process group to be taken down, rather
    than just the one thread.

    Signed-off-by: Will Schmidt
    Cc: Richard Henderson
    Cc: Ivan Kokshaysky
    Cc: Russell King
    Cc: Ian Molton
    Cc: Haavard Skinnemoen
    Cc: Mikael Starvik
    Cc: David Howells
    Cc: Andi Kleen
    Cc: "Luck, Tony"
    Cc: Hirokazu Takata
    Cc: Geert Uytterhoeven
    Cc: Roman Zippel
    Cc: Ralf Baechle
    Cc: Kyle McMartin
    Cc: Matthew Wilcox
    Cc: Paul Mackerras
    Cc: Benjamin Herrenschmidt
    Cc: Heiko Carstens
    Cc: Martin Schwidefsky
    Cc: Paul Mundt
    Cc: Kazumoto Kojima
    Cc: Richard Curnow
    Cc: William Lee Irwin III
    Cc: "David S. Miller"
    Cc: Chris Zankel
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Will Schmidt
     

16 Oct, 2007

2 commits

  • The variable CPPFLAGS is a wellknown variable and the usage by
    kbuild may result in unexpected behaviour.

    This patch replace use of CPPFLAGS with KBUILD_CPPFLAGS all over the
    tree and enabling one to use:
    make CPPFLAGS=...
    to specify additional CPP commandline options.

    Patch was tested on following architectures:
    alpha, arm, i386, x86_64, mips, sparc, sparc64, ia64, m68k, s390

    Signed-off-by: Sam Ravnborg

    Sam Ravnborg
     
  • The variable AFLAGS is a wellknown variable and the usage by
    kbuild may result in unexpected behaviour.
    On top of that several people over time has asked for a way to
    pass in additional flags to gcc.

    This patch replace use of AFLAGS with KBUILD_AFLAGS all over
    the tree.

    Patch was tested on following architectures:
    alpha, arm, i386, x86_64, mips, sparc, sparc64, ia64, m68k, s390

    Signed-off-by: Sam Ravnborg

    Sam Ravnborg
     

15 Oct, 2007

2 commits

  • The variable CFLAGS is a wellknown variable and the usage by
    kbuild may result in unexpected behaviour.
    On top of that several people over time has asked for a way to
    pass in additional flags to gcc.

    This patch replace use of CFLAGS with KBUILD_CFLAGS all over the
    tree and enabling one to use:
    make CFLAGS=...
    to specify additional gcc commandline options.

    One usecase is when trying to find gcc bugs but other
    use cases has been requested too.

    Patch was tested on following architectures:
    alpha, arm, i386, x86_64, mips, sparc, sparc64, ia64, m68k

    Test was simple to do a defconfig build, apply the patch and check
    that nothing got rebuild.

    Signed-off-by: Sam Ravnborg

    Sam Ravnborg
     
  • Only in very rare cases is it needed to change CFLAGS
    outside of arch/*/Makefile.
    Fix up all wrong cases - in most cases
    the use of EXTRA_CFLAGS is the only thing needed.

    Signed-off-by: Sam Ravnborg

    Sam Ravnborg
     

09 Oct, 2007

1 commit


04 Oct, 2007

1 commit

  • Commit 8112753bb2c0045398c89d0647792b39805f6d40 made 44x in
    ARCH=powerpc builds use cpu setup routines in cpu_setup_44x.S,
    but didn't make a similar change for ARCH=ppc, and consequently
    the ARCH=ppc builds fail with undefined symbols (since both use
    the same cputable.c).

    This fixes it by including cpu_setup_44x.S in the ARCH=ppc builds,
    and by taking out the now-redundant FPU initialization in
    arch/ppc/kernel/head_44x.S.

    Signed-off-by: Paul Mackerras

    Paul Mackerras
     

03 Oct, 2007

6 commits