An error occurred fetching the project authors.
- 13 Jun, 2009 11 commits
-
-
Mike Frysinger authored
Just the basic ftrace support here -- mcount and the ftrace stub. Signed-off-by:Mike Frysinger <vapier@gentoo.org>
-
Mike Frysinger authored
Signed-off-by: -
Yi Li authored
Signed-off-by:
Yi Li <yi.li@analog.com> Signed-off-by:
-
Robin Getz authored
Before we configure the early UART, check to make sure we are running on the expected processor - otherwise, we cause problems by configuring pins that don't exist (and causing an infinite loop of faults). Signed-off-by:
Robin Getz <robin.getz@analog.com> Signed-off-by:
-
Mike Frysinger authored
Rather than maintain a duplicate list of valid exceptions we can take in the kernel both in the first if() check and the switch() check, delay the oops check to after the switch(). All valid exceptions will have returned by this point leaving only the invalid ones. Signed-off-by: -
Mike Frysinger authored
The trap_c() code pushes the hardware trace status onto the stack, but doesn't always restore it when returning from some trap code paths. So unify the exit code paths to all head to the end of the function. Signed-off-by: -
Sonic Zhang authored
The KGDB code uses this when switching processors to make sure the icache is in a valid state. Signed-off-by:
Sonic Zhang <sonic.zhang@analog.com> Signed-off-by:
-
Robin Getz authored
Since the compiled-for cpu revision can be significant, include it in the cpuinfo output along side the cpu revision we're currently running on. Signed-off-by:
-
Mike Frysinger authored
Signed-off-by: -
Jie Zhang authored
The latter naming convention is much more common. Signed-off-by:
Jie Zhang <jie.zhang@analog.com> Signed-off-by:
-
Robin Getz authored
We don't need to handle CPLB protection violations unless we are running with the MPU on. Fix the entry code to call common trap_c, and remove the code which is never run. This allows the traps test suite to run on older boards with the MPU disabled. URL: http://blackfin.uclinux.org/gf/tracker/5129Signed-off-by:
-
- 12 Jun, 2009 28 commits
-
-
Mike Frysinger authored
The sparseirq changes (d7e51e66) played poorly with the Blackfin irqchip implementation as we're still using the old hardirq method. Our bad irq structure had a NULL kstat_irqs field so when all the common code tries to increment this field, everything goes big bada boom. Signed-off-by:
-
Mike Frysinger authored
The massive nommu update (8feae131) left the local variable "vml" unused, so punt it. Signed-off-by:
-
Robin Getz authored
We have some test code that runs in userspace that exercises the exception handling of the Blackfin pretty thoroughly. Part of the validation process is checking the exact exception triggered, so export the last one seen to userspace via debugfs when debugging is enabled for the test code to check. Signed-off-by:
-
Roel Kluin authored
The kgdb_ebin2mem() was decrementing the count variable to do parsing, but then later still tries to use it based on its original meaning. So leave it untouched and use a different variable to walk the memory. Signed-off-by:
Roel Kluin <roel.kluin@gmail.com> Signed-off-by:
-
Mike Frysinger authored
The Blackfin kgdb code was all passing back positive errno values when it really should have been using negative errno values. Reported-by:
-
Mike Frysinger authored
There is no need for the L1 attribute to be on the prototype of the access_ok() function as all consumers of the function do not care where it lives -- they'll always use pcrel calls to get to it. This prevents pointless recompiles of most of the system when this config option changes. Signed-off-by: -
Mike Frysinger authored
The EVT registers are all contiguous in the memory map, so using a loop to initialize them all rather than hardcoding the list results in much better generated code (a hardware loop rather than a whole bunch of individual loads). Signed-off-by: -
Mike Frysinger authored
The latest Blackfin toolchain has fixed its relocation scheme to match other ports: always use R_BFIN_ prefix and capitalize everything. This brings the kernel in line with those fixes. Signed-off-by: -
Graf Yang authored
Signed-off-by:
Graf Yang <graf.yang@analog.com> Signed-off-by:
-
Mike Frysinger authored
Due to a processor anomaly (05000263 to be exact), most Blackfin parts cannot keep the embedded filesystem image directly after the kernel in RAM. Instead, the filesystem needs to be relocated to the end of memory. As such, we need to tweak the map addr/size during boot for Blackfin systems. Signed-off-by: -
Michael Hennerich authored
First we fix the prototypes for functions that return boolean values by using "int" rather than "uint16_t". Then we introduce a get_gptimer_run() function for checking the current run status of a timer, and then we add a disable_gptimers_sync() function which parallels disable_gptimers() with corresponding normal "_sync" behavior. Signed-off-by:
Michael Hennerich <michael.hennerich@analog.com> Signed-off-by:
-
Robin Getz authored
People often copy & paste crash messages without surrounding context, so include common useful information like system/processor stats in the crash summary. This should smooth over the report/test cycle a bit more. Signed-off-by:
-
Robin Getz authored
Returning too fast with a bad RETI can trigger false errors. Signed-off-by:
-
Robin Getz authored
When displaying a crash dump, make sure accessing the stack is safe so we don't crash at the same time. Signed-off-by:
-
Robin Getz authored
This way we properly catch and kill applications that jump to a NULL ptr. Signed-off-by:
-
Graf Yang authored
Signed-off-by:
-
Graf Yang authored
For systems where the core cycles are not a usable tick source (like SMP or cycles gets updated), enable gptimer0 as an alternative. Signed-off-by:
-
Sonic Zhang authored
Detect and reject operating conditions for anomaly 05000274 since the problem cannot be worked around in software. Signed-off-by:
-
Mike Frysinger authored
The panic() function already handles newlines for us. Signed-off-by: -
Mike Frysinger authored
Signed-off-by: -
Graf Yang authored
Make sure we work around anomaly 05000287 by configuring different port preferences for the data cache. Signed-off-by:
-
Mike Frysinger authored
This init code existed only to dump a printk(), and not even a useful one. Signed-off-by: -
Robin Getz authored
Add a reminder note to avoid the DMA_DONE bit in our DMA core code. Signed-off-by:
-
Robin Getz authored
Our early L1 relocate code may implicitly call code which lives in L1 memory. This is due to the dma_memcpy() rewrite that made the DMA code lockless and safe to be used by multiple processes. If we start the early DMA memcpy to relocate things into L1 instruction but then our DMA memcpy code calls a function that lives in L1, things fall apart. As such, create a small dedicated DMA memcpy routine that we can assume sanity at boot time. Reported-by:
Filip Van Rillaer <filip.vanrillaer@oneaccess-net.com> Signed-off-by:
-
Michael Hennerich authored
Some drivers expect to be able to request both as GPIO and GPIO IRQ, so allow that use case. Signed-off-by:
Bryan Wu <cooloney@kernel.org> Signed-off-by:
-
Philippe Gerum authored
ipipe-2.6.28.9-blackfin-git95aafe6.patch Singed-off-by:
Philippe Gerum <rpm@xenomai.org> Signed-off-by:
-
Mike Frysinger authored
Make sure we flush all data caches and their write buffers before flushing icache, otherwise random edge cases could crop up where stale data is read into icache from external memory. As fallout, punt the combined icache + dcache flush function since we cannot safely do them back to back -- the SSYNC is needed between the dcache flush and the icache flush. Signed-off-by:
-
Robin Getz authored
Signed-off-by:
Robin Getz <rgetz@blackfin.uclinux.org> Signed-off-by:
-
- 27 May, 2009 1 commit
-
-
Mike Frysinger authored
Signed-off-by:
-
