From: Manuel Reimer <Manuel.Spam@nurfuerspam.de>
To: linux-embedded@vger.kernel.org
Subject: Re: "make oldconfig" kills config options when cross compiling
Date: Sat, 24 May 2014 21:13:53 +0200 [thread overview]
Message-ID: <llqr1h$sgm$1@ger.gmane.org> (raw)
In-Reply-To: <53754D22.2060108@infradead.org>
On 05/16/2014 01:26 AM, Randy Dunlap wrote:
> In 3.7 (where that original config file came from), ARCH_MXS did NOT depend on
> ARCH_MULTI_V5. Somewhere between 3.7 and 3.14, someone decided that ARCH_MXS should
> depend on ARCH_MULTI_V5. You can probably enable that kconfig option and then
> enable ARCH_MXS.
I had to add the following to my config:
CONFIG_ARCH_MULTI_V5=y
CONFIG_ARCH_MULTI_V6_V7=n
CONFIG_ARCH_MULTI_V7=n
With these three lines "make oldconfig" seemed to no longer kill
important config entries.
"make uImage" failed. I got asked to specify a "LOADADDR" so I created
my image like this:
LOADADDR=0x40008000 make uImage
But the resulting kernel fails to boot. The error message makes sense.
Maybe a bug in imx23.dtsi? In fact the serial port "duart:
serial@80070000" does not have a "dma-names" property:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/boot/dts/imx23.dtsi#n496
But is this a blocker and can cause the kernel boot to stop?
Boot log follows:
U-Boot 2013.10 (Jan 08 2014 - 14:49:21) Arch Linux ARM
CPU: Freescale i.MX23 rev1.4 at 454 MHz
BOOT: SSP SD/MMC #0
DRAM: 64 MiB
MMC: MXS MMC: 0
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Net: Net Initialization Skipped
No ethernet found.
Hit any key to stop autoboot: 0
mmc0 is current device
SD/MMC found on device 0
170 bytes read in 101 ms (1000 Bytes/s)
Importing environment from mmc (uEnv.txt)...
Checking if uenvcmd is set ...
Running loaduimage ...
2542832 bytes read in 848 ms (2.9 MiB/s)
9888 bytes read in 124 ms (77.1 KiB/s)
Booting from mmc ...
## Booting kernel from Legacy Image at 42000000 ...
Image Name: Linux-3.14.4-9-ARCH
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2542768 Bytes = 2.4 MiB
Load Address: 40008000
Entry Point: 40008000
Verifying Checksum ... OK
## Flattened Device Tree blob at 41000000
Booting using the fdt blob at 0x41000000
Loading Kernel Image ... OK
Loading Device Tree to 43b63000, end 43b6869f ... OK
Starting kernel ...
[ 0.000000] of_irq_init: children remain, but no parents
[ 1.970000] of_dma_request_slave_channel: dma-names property of node
'/apb@80000000/apbx@80040000/serial@80070000' missing or empty
prev parent reply other threads:[~2014-05-24 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-15 15:02 "make oldconfig" kills config options when cross compiling Manuel Reimer
2014-05-15 23:26 ` Randy Dunlap
2014-05-24 19:13 ` Manuel Reimer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='llqr1h$sgm$1@ger.gmane.org' \
--to=manuel.spam@nurfuerspam.de \
--cc=linux-embedded@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.