> On Jul 21, 2016, at 4:39 PM, Tom Zanussi wrote:
>
> On 07/21/2016 06:33 PM, Jianxun Zhang wrote:
>>
>>> On Jul 21, 2016, at 4:14 PM, Tom Zanussi
>>> wrote:
>>>
>>> On 07/21/2016 06:02 PM, Jianxun Zhang wrote:
> On Jul 21,
> On Jul 21, 2016, at 8:13 PM, Tom Zanussi wrote:
>
> On 07/21/2016 08:05 PM, Jianxun Zhang wrote:
>>
>>> On Jul 21, 2016, at 2:50 PM, Tom Zanussi
>>> wrote:
>>>
>>> On 07/21/2016 04:35 PM, Jianxun Zhang wrote:
> On Jul 21,
On 07/21/2016 08:05 PM, Jianxun Zhang wrote:
>
>> On Jul 21, 2016, at 2:50 PM, Tom Zanussi wrote:
>>
>> On 07/21/2016 04:35 PM, Jianxun Zhang wrote:
>>>
On Jul 21, 2016, at 1:07 PM, Tom Zanussi
wrote:
On 07/21/2016
> On Jul 21, 2016, at 2:50 PM, Tom Zanussi wrote:
>
> On 07/21/2016 04:35 PM, Jianxun Zhang wrote:
>>
>>> On Jul 21, 2016, at 1:07 PM, Tom Zanussi
>>> wrote:
>>>
>>> On 07/21/2016 02:22 PM, Jianxun Zhang wrote:
> On Jul 21,
> On Jul 21, 2016, at 4:21 PM, Tom Zanussi wrote:
>
> On 07/21/2016 03:37 AM, Jianxun Zhang wrote:
>> 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
On 07/21/2016 06:33 PM, Jianxun Zhang wrote:
>
>> On Jul 21, 2016, at 4:14 PM, Tom Zanussi wrote:
>>
>> On 07/21/2016 06:02 PM, Jianxun Zhang wrote:
>>>
On Jul 21, 2016, at 3:41 PM, Tom Zanussi
wrote:
On 07/21/2016
> On Jul 21, 2016, at 4:14 PM, Tom Zanussi wrote:
>
> On 07/21/2016 06:02 PM, Jianxun Zhang wrote:
>>
>>> On Jul 21, 2016, at 3:41 PM, Tom Zanussi
>>> wrote:
>>>
>>> On 07/21/2016 03:37 AM, Jianxun Zhang wrote:
Provide a README
> On Jul 21, 2016, at 3:35 PM, Tom Zanussi wrote:
>
> On 07/21/2016 03:37 AM, Jianxun Zhang wrote:
>> RMC recipe 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
On 07/21/2016 03:37 AM, Jianxun Zhang wrote:
> 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
On 07/21/2016 06:02 PM, Jianxun Zhang wrote:
>
>> On Jul 21, 2016, at 3:41 PM, Tom Zanussi wrote:
>>
>> On 07/21/2016 03:37 AM, Jianxun Zhang wrote:
>>> Provide a README for RMC feature. Also check in fingerprints and
>>> configuration data for several boards as
> On Jul 21, 2016, at 3:41 PM, Tom Zanussi wrote:
>
> On 07/21/2016 03:37 AM, Jianxun Zhang wrote:
>> Provide a README for RMC feature. Also check in fingerprints and
>> configuration data for several boards as examples for users.
>> They can be used for validation
On 07/21/2016 03:37 AM, Jianxun Zhang wrote:
> Provide a README for RMC feature. 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
[...]
> +
>
On 07/21/2016 04:35 PM, Jianxun Zhang wrote:
>
>> On Jul 21, 2016, at 1:07 PM, Tom Zanussi wrote:
>>
>> On 07/21/2016 02:22 PM, Jianxun Zhang wrote:
>>>
On Jul 21, 2016, at 11:37 AM, Tom Zanussi
wrote:
Hi Jianxun,
> On Jul 21, 2016, at 1:07 PM, Tom Zanussi wrote:
>
> On 07/21/2016 02:22 PM, Jianxun Zhang wrote:
>>
>>> On Jul 21, 2016, at 11:37 AM, Tom Zanussi
>>> wrote:
>>>
>>> Hi Jianxun,
>>>
>>> On 07/21/2016 03:37 AM, Jianxun Zhang wrote:
On 07/21/2016 02:22 PM, Jianxun Zhang wrote:
>
>> On Jul 21, 2016, at 11:37 AM, Tom Zanussi
>> wrote:
>>
>> Hi Jianxun,
>>
>> On 07/21/2016 03:37 AM, Jianxun Zhang wrote:
>>> V3 addresses feedbacks for V2, also includes other fixes:
>>>
>>> () Explicitly tell user
> On Jul 21, 2016, at 11:37 AM, Tom Zanussi wrote:
>
> Hi Jianxun,
>
> On 07/21/2016 03:37 AM, Jianxun Zhang wrote:
>> V3 addresses feedbacks for V2, also includes other fixes:
>>
>> () Explicitly tell user overriding is a temporary solution in README
>>
>> ()
> On Jul 21, 2016, at 9:08 AM, Tom Zanussi wrote:
>
> On 07/21/2016 03:37 AM, Jianxun Zhang wrote:
>> V3 addresses feedbacks for V2, also includes other fixes:
>>
>> () Explicitly tell user overriding is a temporary solution in README
>>
>> () Move back two
[PATCH] intel-microcode: Update to the 20160714 version
>From the OpenXT Project ( http://openxt.org )
refs: https://openxt.atlassian.net/browse/OXT-668
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
From: Christopher Clark
Dates changed in Licence file required CHKSUM update
>From the OpenXT Project ( http://openxt.org )
refs: OXT-668
Signed-off-by: Christopher Clark
---
.../{intel-microcode_20151106.bb =>
From: Christopher Clark
Dates changed in Licence file required CHKSUM update
>From the OpenXT Project ( http://openxt.org )
refs: OXT-668
Signed-off-by: Christopher Clark
---
.../{intel-microcode_20151106.bb =>
[PATCH] intel-microcode: Update to the 20160714 version
>From the OpenXT Project ( http://openxt.org )
refs: https://openxt.atlassian.net/browse/OXT-668
--
___
meta-intel mailing list
meta-intel@yoctoproject.org
On 07/21/2016 03:37 AM, Jianxun Zhang wrote:
> V3 addresses feedbacks for V2, also includes other fixes:
>
> () Explicitly tell user overriding is a temporary solution in README
>
> () Move back two readme files back to top dir
>
> () Move RMC README to /documentation/rmc/
>
> () Replace
RMC Feature is based on RMC project, systemd-boot, EFI installer
to enable a single generic image, built for multiple platforms,
automatically applies customization and quirks specific to a type
of boards at runtime.
In another word, you will see a single image behaves differently
and
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
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
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.
Signed-off-by: Jianxun Zhang
---
V3 addresses feedbacks for V2, also includes other fixes:
() Explicitly tell user overriding is a temporary solution in README
() Move back two readme files back to top dir
() Move RMC README to /documentation/rmc/
() Replace wrong EFI_PROVIDER info with Distro feature in RMC README
()
RMC recipe 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 running
Hi Rahul,
Will you be able to get me the patch?
Thanks
From: Ashish Dalela (adalela)
Sent: Monday, July 18, 2016 6:01 PM
To: 'Gupta, Rahul KumarXX' ;
meta-intel@yoctoproject.org
Cc: Tan, Raymond ; Pradeep Munakala (pmunakal)
29 matches
Mail list logo