- 09 Mar, 2010 40 commits
-
-
Mike Frysinger authored
We don't support core dumps (yet?), but this should make things easier. Signed-off-by:Mike Frysinger <vapier@gentoo.org>
-
Mike Frysinger authored
Signed-off-by: -
Mike Frysinger authored
We don't want to let user space modify the SYSCFG register arbitrarily as the settings are system wide (SNEN/CNEN) and can cause misbehavior. The only other bit here (SSSTEP) has proper controls via PTRACE_SINGLESTEP. Signed-off-by: -
Christoph Hellwig authored
Use the generic ptrace_resume code for PTRACE_SYSCALL, PTRACE_CONT, PTRACE_KILL and PTRACE_SINGLESTEP. This implies defining arch_has_single_step in <asm/ptrace.h> and implementing the user_enable_single_step and user_disable_single_step functions, which also causes the breakpoint information to be cleared on fork, which could be considered a bug fix. Also the TIF_SYSCALL_TRACE thread flag is now cleared on PTRACE_KILL which it previously wasn't which is consistent with all architectures using the modern ptrace code. Signed-off-by:
Christoph Hellwig <hch@lst.de> Signed-off-by:
-
Barry Song authored
Signed-off-by:
Barry Song <barry.song@analog.com> Signed-off-by:
-
Graf Yang authored
This functions are implicitly called by core functions like cpu_relax(), and since those functions may be called early on before common code has initialized the per-cpu data area, we need to tweak the stats gathering. Now the statistics are maintained in common bss which makes these funcs safe to use as soon as the C runtime env is setup. Signed-off-by:
Graf Yang <graf.yang@analog.com> Signed-off-by:
-
Graf Yang authored
Signed-off-by:
-
Barry Song authored
The ASoC codec driver was generalized and renamed, so update the board resources accordingly. Signed-off-by:
-
Yi Li authored
Since GCC doesn't support __builtin_frame_address(n) where n!=0, add our own function to walk the stack frame pointers. Signed-off-by:
Yi Li <yi.li@analog.com> Signed-off-by:
-
Mike Frysinger authored
Signed-off-by: -
Graf Yang authored
This allows things to be shared between the different watchdog sources. Signed-off-by:
-
Barry Song authored
Some IRQ handlers need to disable a DMA channel without waiting. Signed-off-by:
-
Mike Frysinger authored
Signed-off-by: -
Mike Frysinger authored
Signed-off-by: -
Mike Frysinger authored
Signed-off-by: -
Barry Song authored
Signed-off-by:
-
Graf Yang authored
Signed-off-by:
-
Barry Song authored
Restore support for CONFIG_EXCPT_IRQ_SYSC_L1 in the MPU CPLB manager. Signed-off-by:
-
Barry Song authored
Rather than declaring pin resources in the drivers, do it in the board. Signed-off-by:
-
Barry Song authored
Signed-off-by:
-
Michael Hennerich authored
This makes room for off-chip IRQ controllers. Signed-off-by:
Michael Hennerich <michael.hennerich@analog.com> Signed-off-by:
-
Barry Song authored
Some userspace applications use this member in diagnosing crashes. It also makes some LTP tests pass (i.e. the Blackfin arch behaves more like everyone else). Signed-off-by:
-
Mike Frysinger authored
Just generate a random MAC on the demo board since the ADF702x lacks dedicated storage for such things. Signed-off-by: -
Yi Li authored
Signed-off-by:
-
Harald Krapfenbauer authored
Signed-off-by:
Harald Krapfenbauer <harald.krapfenbauer@bluetechnix.at> Signed-off-by:
-
Barry Song authored
When the kernel is executing out of parallel flash (XIP), we can't have the flash go into an erase/programming cycle, otherwise the instruction fetching steps fail and everything crashes. Signed-off-by:
-
Cliff Cai authored
Signed-off-by:
Cliff Cai <cliff.cai@analog.com> Signed-off-by:
-
Graf Yang authored
The locking code in the address dumper needs to grab the mm's mmap_sem so that other CPUs do not get an inconsistent view. On UP systems this really wasn't a problem, but it is easy to trigger a race on SMP systems when another CPU removes a mapping. Signed-off-by:
-
Barry Song authored
Signed-off-by:
-
Mike Frysinger authored
Signed-off-by: -
Roel Kluin authored
This condition allowed only decoding of opcode 0x0040 Signed-off-by:
Roel Kluin <roel.kluin@gmail.com> Signed-off-by:
-
Barry Song authored
Signed-off-by:
-
Barry Song authored
During very early init, the stack pointer is given a slightly incorrect value (&init_thread_union). The value is later adjusted to the right one during early init (&init_thread_union + THREAD_SIZE), but it is used a few times in between. While the few functions used don't actually put things onto the stack (due to optimization), it's best if we simply use the right value from the start. Signed-off-by:
-
Barry Song authored
Use the common attribute rather than setting the section name directly. The common linker script defines expect the newer naming. Signed-off-by:
-
Barry Song authored
Signed-off-by:
-
Jie Zhang authored
Since we are now discarding .exit.text at runtime instead of link time, we need to place all .text sections ahead of the .data sections. Otherwise, a really large attached initramfs may cause link errors as it pushes the PC relative relocations behind the limits of the Blackfin ISA (~16meg). The instructions in the .exit.text are unable to call back into the .text sections leading to a link failure. Signed-off-by:
Jie Zhang <jie.zhang@analog.com> Signed-off-by:
-
Yi Li authored
Signed-off-by:
-
Yi Li authored
There is no need to use {get,put}_cpu() when we already have a spinlock to protect against multiple processors running simultaneously. Signed-off-by: -
Graf Yang authored
Signed-off-by:
-
Yi Li authored
SMP systems require per-cpu local clock event devices in order to enable HRT support. One a BF561, we can use local core timer for this purpose. Originally, there was one global core-timer clock event device set up for core A. To accomplish this feat, we need to split the gptimer0/core timer logic so that each is a standalone clock event. There is no requirement that we only have one clock event source anyways. Once we have this, we just define per-cpu clock event devices for each local core timer. Signed-off-by:
-
