Commit 816ad74 (ARM: i.MX53: Add full iomux support for mx53) renamed some of the pad names.
Make the changes accordingly so that mx53_loco and mx53_cmd can build without errors.
Signed-off-by: Fabio Estevam <redacted>
---
arch/arm/mach-mx5/board-mx53_loco.c | 25 +++++++++++++------------
arch/arm/mach-mx5/board-mx53_smd.c | 24 ++++++++++++------------
2 files changed, 25 insertions(+), 24 deletions(-)
On mx53_loco only UART1 is used and its signals go to connector J16.
Remove UART2 and UART3 as they are not used on this board.
Signed-off-by: Fabio Estevam <redacted>
---
arch/arm/mach-mx5/board-mx53_loco.c | 24 +-----------------------
1 files changed, 1 insertions(+), 23 deletions(-)
Yong,
Can you ack these?
Sascha
On Tue, Jan 25, 2011 at 01:08:33PM -0200, Fabio Estevam wrote:
quoted hunk
Commit 816ad74 (ARM: i.MX53: Add full iomux support for mx53) renamed some of the pad names.
Make the changes accordingly so that mx53_loco and mx53_cmd can build without errors.
Signed-off-by: Fabio Estevam <redacted>
---
arch/arm/mach-mx5/board-mx53_loco.c | 25 +++++++++++++------------
arch/arm/mach-mx5/board-mx53_smd.c | 24 ++++++++++++------------
2 files changed, 25 insertions(+), 24 deletions(-)
From: Richard Zhao <hidden> Date: 2011-01-27 09:30:44
Hi Fabio,
Sorry I didn't see your patch. I just sent out a patch to include all pad
configure for imx53_loco.
I have some comments below.
On Thu, Jan 27, 2011 at 08:30:09AM +0100, Sascha Hauer wrote:
Yong,
Can you ack these?
Sascha
On Tue, Jan 25, 2011 at 01:08:33PM -0200, Fabio Estevam wrote:
quoted
Commit 816ad74 (ARM: i.MX53: Add full iomux support for mx53) renamed some of the pad names.
Make the changes accordingly so that mx53_loco and mx53_cmd can build without errors.
Signed-off-by: Fabio Estevam <redacted>
---
arch/arm/mach-mx5/board-mx53_loco.c | 25 +++++++++++++------------
arch/arm/mach-mx5/board-mx53_smd.c | 24 ++++++++++++------------
2 files changed, 25 insertions(+), 24 deletions(-)
As per the subject the intention of this patch is to fix the build for mx53_loco and mx53_smd.
In this patch I just changed the pad names to fix the build issue.
Right, these are removed later in my patch series.
After my patch series is applied we have a working UART1 console.
Can we apply them?
Regards,
Fabio Estevam
As per the subject the intention of this patch is to fix the build for mx53_loco and mx53_smd.
In this patch I just changed the pad names to fix the build issue.
Right, these are removed later in my patch series.
I didn't see your patch series in my freescale mailbox, until Sascha replied.
After my patch series is applied we have a working UART1 console.
Can we apply them?
Sure. My two coins, why don't you squash patch 2 and 3. They're both small and
modifying the same thing. It don't matter much. If you choose to send it again,
you can merge my second patch.
From: Nick Pelling <hidden> Date: 2011-01-27 12:58:02
Hi everyone,
I've been looking for a good source of information on getting Linux
working on a new ARM target, including a checklist of things to cover
such as putc(), arch_decomp_setup(), etc. So far, pretty much the
best source of information I've found is Wookey & Tak-Shing's
"Porting the Linux Kernel to a New ARM Platform"...
http://www.glomationinc.com/PortingLinuxKernel.pdf
...but I can't help but notice that this is from 2002.
Is there an updated version of this document (or perhaps a book
chapter covering this) you would recommend?
Cheers, ....Nick Pelling....
Hi Richard,
On Thu, Jan 27, 2011 at 10:19 AM, Richard Zhao [off-list ref] wrote:
....
quoted
Right, these are removed later in my patch series.
I didn't see your patch series in my freescale mailbox, until Sascha replied.
quoted
After my patch series is applied we have a working UART1 console.
Can we apply them?
Sure. My two coins, why don't you squash patch 2 and 3. They're both small and
modifying the same thing. It don't matter much. If you choose to send it again,
you can merge my second patch.
I preferred to split the patch as I did originally:
1/3: Fix the build issue on MX53_LOCO and MX53_SMD
2/3: Make UART1 functional on MX53_LOCO
3/3: Remove UART2 and UART3.
(http://www.spinics.net/lists/arm-kernel/msg112234.html )
You can then send a patch for adding the additional peripherals of
MX53_LOCO board after these patch series are merged.
Does it sound good for you?
....
will you fix iomux issue here? I didn't see any other fix in your patch series.
UART1 IOMUX is fixed in patch 2/3.
Regards,
Fabio Estevam
From: Richard Zhao <hidden> Date: 2011-01-28 12:46:46
On Tue, Jan 25, 2011 at 01:08:33PM -0200, Fabio Estevam wrote:
Commit 816ad74 (ARM: i.MX53: Add full iomux support for mx53) renamed some of the pad names.
Make the changes accordingly so that mx53_loco and mx53_cmd can build without errors.
Signed-off-by: Fabio Estevam <redacted>
--
1.6.0.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
--
1.6.0.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
From: Richard Zhao <hidden> Date: 2011-01-28 12:48:58
On Tue, Jan 25, 2011 at 01:08:35PM -0200, Fabio Estevam wrote:
On mx53_loco only UART1 is used and its signals go to connector J16.
Remove UART2 and UART3 as they are not used on this board.
Signed-off-by: Fabio Estevam <redacted>
--
1.6.0.4
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
From: Steve Chen <hidden> Date: 2011-02-03 14:31:04
On Thu, Jan 27, 2011 at 6:58 AM, Nick Pelling [off-list ref] wrote:
Hi everyone,
I've been looking for a good source of information on getting Linux working
on a new ARM target, including a checklist of things to cover such as
putc(), arch_decomp_setup(), etc. So far, pretty much the best source of
information I've found is Wookey & Tak-Shing's "Porting the Linux Kernel to
a New ARM Platform"...
? ? ? ?http://www.glomationinc.com/PortingLinuxKernel.pdf
...but I can't help but notice that this is from 2002.
Is there an updated version of this document (or perhaps a book chapter
covering this) you would recommend?
Cheers, ....Nick Pelling....
Hello,
I took a quick look at the document. Much of the information still
applies to the latest kernel. The biggest change that I can see is
that the directories were moved and files renames. For example
arch/arm/deconfigs/ is now arch/arm/configs
config.in is now Kconfig
include/asm-arm/arch-xxx is moved to arch/arm/mach-xxx/include
By the way, include/asm is a symlink points to
include/asm-arm/arch-xxxx in the older kernels. The link is created
by the make. If I were to get Linux to boot on a new board, I would
start by looking at code for a similar target with the same SoC.
I hope that helps.
Steve
From: Russell King - ARM Linux <hidden> Date: 2011-02-03 14:36:30
On Thu, Feb 03, 2011 at 08:31:04AM -0600, Steve Chen wrote:
By the way, include/asm is a symlink points to
include/asm-arm/arch-xxxx in the older kernels.
In old kernels, include/asm was pointed at include/asm-arm. We had a
second symlink for include/asm-arm/arch which pointed at
include/asm-arm/arch-xxx. Even older kernels had another symlink for
include/asm-arm/proc pointing at either include/asm-arm/proc-armv or
.../proc-armo depending on whether we were building for 32-bit or 26-bit
ARMs.