[meta-intel] Urgent: my network interface name is changed to sit0 instead of eth0

Hi, I'm building meta-intel & poky (based on jethro release) for my custom hardware (based on intel atom e3845) and I see that my network interface name has changed from "eth0" to "sit0" and I do not get any network connection on my device. How can I revert back to eth0? I have tried adding

Re: [meta-intel] [PATCH 5/6] rmc: add recipe and bbclass for feature "rmc distro"

> On Jul 12, 2016, at 5:21 PM, Saul Wold wrote: > > On Tue, 2016-07-12 at 16:53 -0700, Jianxun Zhang wrote: >>> >>> On Jul 12, 2016, at 4:29 PM, Saul Wold wrote: >>> >>> On Tue, 2016-07-12 at 10:59 -0700, Jianxun Zhang wrote: The new added

Re: [meta-intel] [PATCH 5/6] rmc: add recipe and bbclass for feature "rmc distro"

On Tue, 2016-07-12 at 16:53 -0700, Jianxun Zhang wrote: > > > > On Jul 12, 2016, at 4:29 PM, Saul Wold wrote: > > > > On Tue, 2016-07-12 at 10:59 -0700, Jianxun Zhang wrote: > > > > > > The new added recipe and bbclass put modified systemd-boot, > > > EFI installer and rmc

Re: [meta-intel] [PATCH 0/6] Runtime Machine Configuration and Distro

| >> Time: 0:00:00 >> Parsing of 884 .bb files complete (883 cached, 1 parsed). 1324 targets, >> 51 skipped, 0 masked, 0 errors. >> NOTE: Resolving any missing task queue dependencies >> >> Build Configuration: >> BB_VERSION

Re: [meta-intel] [PATCH 5/6] rmc: add recipe and bbclass for feature "rmc distro"

> On Jul 12, 2016, at 4:29 PM, Saul Wold wrote: > > On Tue, 2016-07-12 at 10:59 -0700, Jianxun Zhang wrote: >> The new added recipe and bbclass put modified systemd-boot, >> EFI installer and rmc work together to enable a single >> generic image, built for multiple

Re: [meta-intel] [PATCH 5/6] rmc: add recipe and bbclass for feature "rmc distro"

On Tue, 2016-07-12 at 10:59 -0700, Jianxun Zhang wrote: > The new added recipe and bbclass put modified systemd-boot, > EFI installer and rmc work together to enable a single > generic image, built for multiple platforms, automatically > applies customization specific to the type of a running

Re: [meta-intel] [PATCH 0/6] Runtime Machine Configuration and Distro

lete (883 cached, 1 parsed). 1324 >> targets, >> 51 skipped, 0 masked, 0 errors. >> NOTE: Resolving any missing task queue dependencies >> >> Build Configuration: >> BB_VERSION= "1.31.0" >> BUILD_SYS = "x86_64-linux" >>

Re: [meta-intel] [PATCH 0/6] Runtime Machine Configuration and Distro

ation: > BB_VERSION= "1.31.0" > BUILD_SYS = "x86_64-linux" > NATIVELSBSTRING = "Ubuntu-15.10" > TARGET_SYS= "x86_64-poky-linux" > MACHINE = "intel-corei7-64" > DISTRO= "poky" > DIS

Re: [meta-intel] [PATCH 0/6] Runtime Machine Configuration and Distro

On Tue, 2016-07-12 at 10:59 -0700, Jianxun Zhang wrote: > This patch seriese introduces new RMC project and RMC distro that's > developped based on RMC. > > The test is done on several boards, including boards checked in > examples. (poky:6bb3069; meta-intel: 9bb4622) > > Some people may have

Re: [meta-intel] [PATCH 1/6] rmc: Add Runtime Machine Configuration (RMC) project

On Tue, 2016-07-12 at 10:59 -0700, Jianxun Zhang wrote: > RMC recipes fetch RMC project and build it more than once in > build time: > > RMC tool is built for host architecture (native). The tool for > host is used to generate RMC database in build time. > > RMC tool is also built for target

Re: [meta-intel] [PATCH 0/6] Runtime Machine Configuration and Distro

t; Build Configuration: > BB_VERSION= "1.31.0" > BUILD_SYS = "x86_64-linux" > NATIVELSBSTRING   = "Ubuntu-15.10" > TARGET_SYS    = "x86_64-poky-linux" > MACHINE   = "intel-corei7-64" > DISTRO= "

Re: [meta-intel] [PATCH 0/6] Runtime Machine Configuration and Distro

dependencies Build Configuration: BB_VERSION= "1.31.0" BUILD_SYS = "x86_64-linux" NATIVELSBSTRING = "Ubuntu-15.10" TARGET_SYS= "x86_64-poky-linux" MACHINE = "intel-corei7-64" DISTRO = "poky" DISTRO_V

[meta-intel] [PATCH 4/6] EFI installer: deploy board-specific data and kernel cmdline

Extend the existing init-install-efi.sh in OE to call RMC tool so that it can deploy file blobs and a global kernel cmdline fragment associated to the type of current running board. At first, it tries to retrieve a special configuration file INSTALLER.CONFIG associated to the board from RMC

[meta-intel] [PATCH 6/6] rmc: document and examples for rmc distro feature

Provide a README.rmc.distro for rmc-distro. Also check in fingerprints and configuration data for several boards as examples for users. They can be used for validation too. Signed-off-by: Jianxun Zhang --- README.rmc.distro | 261

[meta-intel] [PATCH 0/6] Runtime Machine Configuration and Distro

This patch seriese introduces new RMC project and RMC distro that's developped based on RMC. The test is done on several boards, including boards checked in examples. (poky:6bb3069; meta-intel: 9bb4622) Some people may have checked implementation before, but I have done a lot refactoring since

[meta-intel] [PATCH 3/6] systemd-boot: load board-specific entry and kernel cmdline

Invoke RMC APIs in this bootloader to query board-specific data from RMC database(DB) file on ESP. Data can be boot entries or a global kernel boot command line fragment specific to a type of board supported in RMC DB. Bootloader queries a file blob named BOOTENTRY.CONFIG from RMC DB first. In

[meta-intel] [PATCH 5/6] rmc: add recipe and bbclass for feature "rmc distro"

The new added recipe and bbclass put modified systemd-boot, EFI installer and rmc work together to enable a single generic image, built for multiple platforms, automatically applies customization specific to the type of a running board. In another word, you will see a single image behaves

[meta-intel] [PATCH 1/6] rmc: Add Runtime Machine Configuration (RMC) project

RMC recipes fetch RMC project and build it more than once in build time: RMC tool is built for host architecture (native). The tool for host is used to generate RMC database in build time. RMC tool is also built for target architecture, so that scripts in user space can call RMC tool on a

[meta-intel] [PATCH 2/6] gnu-efi: Add GUID for SMBIOS 3 entry point structure

UEFI spec has different GUIDs for 32 and 64 bit SMBIOS entry point structure. This change adds definition for 64 bit GUID, so that software linked with gnu-efi can have it for x86_64 architecture. Upstream-Status: Pending Signed-off-by: Jianxun Zhang ---