On 09/21/2015 06:51 AM, Prasant J wrote:
Hi,
I'm building yocto distro for my custom hardware based on intel Atom E3845.
Below is my yocto build configuration:
BB_VERSION = "1.24.0"
BUILD_SYS = "i686-linux"
NATIVELSBSTRING = "Ubuntu-12.04"
TARGET_SYS = "i586-poky-linux"
MACHINE = "valleyisland-32"
DISTRO = "poky"
DISTRO_VERSION = "1.7.1"
TUNE_FEATURES = "m32 core2"
TARGET_FPU = ""
meta
meta-yocto
meta-yocto-bsp = "(nobranch):ff482c2522f7092216a4ac7b335393a5294d97d5"
meta-msc-ldk-core = "v0.4.0:ed047edacf285e711c55ed8389111981abc417c7"
meta-valleyisland = "(nobranch):5af06a8b0dd28498e77581f6bcb7fd6f722b755a"
meta = "(nobranch):56c6bebdd19b5b64a2585986299543abf6e6ad48"
I have changed kernel configuration and successfully built it
(arch/x86/boot/bzImage), but when I copy the newly built kernel to my
target hardware I do not see the relevant changes.
I check my kernel config (zcat /proc/config.gz) and my updated
configuration is not there.
Pj:
This is sounding similar to your other issue, where are you copying the
files to exactly, what disk or usb device? Are you using initramfs.
Your using grub, correct? Have you changed the default grub.conf from
the build?
After updating the configuration, I can see the relevant files being built
(that confirms my changes were applied) also I can see my updated
configuration is (kernel_source_code/include/config.gz).
So why can't I see the new configuration on the target hardware?
I also tried building the kernel outside the yocto build system (used the
SDK to build the kernel). Same observations.
Did you rebuild the image or just the kernel?
I have worked for many years on embedded ARM linux systems but I have never
come across such a puzzling observation. Any one get any ideas what I may
have missed or what I may be doing wrong ?
Thanks in advance!
Regards, Pj
--
_______________________________________________
meta-intel mailing list
[email protected]
https://lists.yoctoproject.org/listinfo/meta-intel
