Hi Philipp and Carlos,
Thanks for the reply.
When simpleImage.elf is loaded by a debugger, the debugger reads the elf image
header and places various sections of image into right place in the RAM. But
when I do it from already_running_code, I should manually unpack the elf and
place the
Add:
- Setup dts node for USB
- pin description and setup for SMC1 (serial interface)
Update and cleanup mgcoge_defconfig:
- enable: TIPC, UBIFS, USB_GADGET driver, SQUASHFS, HIGHRES timers
POSIX_MQUEUE, EMBEDDED
- disable: EXT3, PPC_PMAC
Signed-off-by: Holger Brunck
Hi Jimi,
It would really help me a lot if you could review and maybe merge
this with my earlier patch that splits this file.
http://patchwork.ozlabs.org/patch/109103/ All it does is split.. I
promise. You don't have to take the other stuff.. yet :)
Sorry it took so long to get to this.
Hi Jimi,
Some processors, like embedded, that already have a PID register that
is managed by the system. This patch separates the ACOP and PID
processing into separate files so that the ACOP code can be shared.
Signed-off-by: Jimi Xenidis ji...@pobox.com
Looks good.
Acked-by: Anton
Hi,
I am working on enabling CONFIG_RELOCATABLE for PPC44x Embedded PowerPC
boards as a foundation to enable CONFIG_CRASH_DUMP. After a discussion
on the linux-ppcdev we decided that we will follow the 'processing
relocation entries' approach for running the kernel from a different
address.
[Resending - Missed a few key people on the Cc list + Some more comments]
Hi,
I am working on enabling CONFIG_RELOCATABLE for PPC44x Embedded PowerPC
boards as a foundation to enable CONFIG_CRASH_DUMP. After a discussion
on the linux-ppcdev , we decided that we will follow the 'processing
Hi,
Looks like 8xxx GPIO driver cannot properly handle interrupts
when multiple GPIO controllers exist in the system.
On Freescale P1022 there are 3 GPIO controllers. All 3 use
the same interrupt line, internal interrupt 31. If all controllers
are defined in device tree
On Tue, Sep 27, 2011 at 04:59:28PM +0300, Felix Radensky wrote:
Hi,
Looks like 8xxx GPIO driver cannot properly handle interrupts
when multiple GPIO controllers exist in the system.
On Freescale P1022 there are 3 GPIO controllers. All 3 use
the same interrupt line, internal interrupt 31.
Hi Grant,
On 09/27/2011 09:29 PM, Grant Likely wrote:
On Tue, Sep 27, 2011 at 04:59:28PM +0300, Felix Radensky wrote:
Hi,
Looks like 8xxx GPIO driver cannot properly handle interrupts
when multiple GPIO controllers exist in the system.
On Freescale P1022 there are 3 GPIO controllers. All 3