Resetting the luv-yocto master branch
by Matt Fleming
Folks,
Based on the recent discussions we've had on this mailing list,
https://lists.01.org/pipermail/luv/2015-January/000265.html
and the pain points experienced in moving from Dora to Dizzy, I think
it's best if we move to a release process that more closely matches
upstream Yocto Project and OE-core, where we fork a branch every time
a new release is created in upstream Yocto Project.
So, once v1.2 drops (week of 23rd March) I plan on moving the 'master'
branch of the luv-yocto repository to point at the 'master' branch of
Poky. The benefits are discussed in the thread referenced above but
mainly it allows us to pull new changes from upstream much sooner.
What this will mean is that after the v1.2 tag is created you'll see
something like the following when fetching updates,
$ git fetch
remote: Counting objects: 12698, done.
remote: Compressing objects: 100% (2537/2537), done.
remote: Total 10416 (delta 7720), reused 10409 (delta 7713)
Receiving objects: 100% (10416/10416), 2.60 MiB | 0 bytes/s, done.
Resolving deltas: 100% (7720/7720), completed with 879 local objects.
From /home/foobar/luv-yocto
+ fd8d0b4...dda70ca master -> origin/master (forced update)
and a git pull will fail with a whole bunch of conflicts, because git
can't do a simple merge.
If you don't have any changes on your master branch the easiest way to
get upto date is to do,
$ git reset --hard origin/master
However, if you do have updates, before you do the reset you must save
them either by creating patches or stashing your changes.
Do not merge your old branches into the new master branch, the resulting
history will be an abomination, and explicitly contradicts what I'm
trying to do here - make it possible to merge upstream without causing
huge amounts of conflicts.
The old tip of the master branch will always be accessible with the
'v1.2' tag, so it's not like the history is going to be lost in any way.
Let me know if you have any questions.
--
Matt Fleming, Intel Open Source Technology Center
7 years
[PATCH v2 0/8] luvOS support for ARM64
by Naresh Bhat
A set of patches which will help to build and run luvOS distribution for aarch64 architecture.
With this set you can build and run the luvOS distribution for genericarmv8 machine.
I have verified the luvOS distribution on ARM64 FVP base model.
The flow of luvOS distribution on arm64 architecture
<boot> -> <upstream GRUB> -> leg-kernel with ACPI support -> efivarfs -> fwts -> kernel-efi-warnings -> <DONE>
Instructions and logs visit
Linaro wiki - https://wiki.linaro.org/LEG/Engineering/luvOS
Git repository - https://git.linaro.org/people/naresh.bhat/luvOS/luv-yocto.git
Changes since V0:[RFC series]
- Add all the comments from Matt Fleming on RFC series
- Rebase all patches on top of v1.2-rc3-dizzy
- cherry pick few patches from upstream
- Drop all the unnecessary aarch64 patches
Changes since V1:[series]
- Rebase all patches on top of v1.2-rc4
- Modify grub_git.bb recipe so that it can be built for both native and non-native architecture
- Update leg-kernel defconfig file
- Skip syslinux package for aarch64 build
- Skip ISO image build for aarch64
- Address Matt Fleming comments on bootimg bbclass. Modify the class to support aarch64/x86_64/i386 architecture
- Update FWTS version to 15.01.00
- Define bootimg dependency in luv-efi bbclass for aarch64 (i.e. grub)
Naresh Bhat (8):
aarch64: Add genericarmv8 machine configuration file
bootimg: Add support to install Image
luv-efi: Define bootimg dependency
fwts : Upgrade to version 15.01.00
syslinux: Skip syslinux dependency for aarch64
bootimg: Skip build iso image for aarch64
grub: Update grub git recipe
leg-kernel: Update leg kernel config
meta-luv/classes/luv-efi.bbclass | 11 +-
...01-efi_runtime-Set-default-value-for-KVER.patch | 27 -
...-Refactor-ioctl-code-into-helper-function.patch | 506 -------
...-Group-kernel-version-dependent-functions.patch | 99 --
...me-Do-not-pass-user-addresses-to-firmware.patch | 374 -----
...fi_runtime-donot-dereference-user-address.patch | 444 ------
...de-remove-failures-when-kernel-does-not-h.patch | 40 -
...ert-report-info-instead-of-failure-for-mi.patch | 68 -
...runtime-Don-t-use-get_user-on-non-pointer.patch | 34 -
...-limit-the-amount-of-data-copied-to-users.patch | 95 --
...-get_nextvariable-copy-only-the-needed-na.patch | 41 -
...able-allow-large-sizes-for-variable-names.patch | 245 ----
meta-luv/recipes-core/fwts/fwts_git.bb | 19 +-
meta-luv/recipes-kernel/linux/leg-kernel/defconfig | 1510 ++++++++++++++------
meta/classes/bootimg.bbclass | 16 +-
meta/classes/syslinux.bbclass | 11 +-
meta/conf/machine/genericarmv8.conf | 16 +
meta/conf/machine/genericarmv8b.conf | 6 +
meta/conf/machine/include/arm64/arch-armv8.inc | 20 +
meta/recipes-bsp/grub/grub_git.bb | 60 +-
20 files changed, 1233 insertions(+), 2409 deletions(-)
delete mode 100644 meta-luv/recipes-core/fwts/fwts/0001-efi_runtime-Set-default-value-for-KVER.patch
delete mode 100644 meta-luv/recipes-core/fwts/fwts/0002-efi_runtime-Refactor-ioctl-code-into-helper-function.patch
delete mode 100644 meta-luv/recipes-core/fwts/fwts/0003-efi_runtime-Group-kernel-version-dependent-functions.patch
delete mode 100644 meta-luv/recipes-core/fwts/fwts/0004-efi_runtime-Do-not-pass-user-addresses-to-firmware.patch
delete mode 100644 meta-luv/recipes-core/fwts/fwts/0005-efi_runtime-donot-dereference-user-address.patch
delete mode 100644 meta-luv/recipes-core/fwts/fwts/0006-cpu-microcode-remove-failures-when-kernel-does-not-h.patch
delete mode 100644 meta-luv/recipes-core/fwts/fwts/0007-securebootcert-report-info-instead-of-failure-for-mi.patch
delete mode 100644 meta-luv/recipes-core/fwts/fwts/0008-efi_runtime-Don-t-use-get_user-on-non-pointer.patch
delete mode 100644 meta-luv/recipes-core/fwts/fwts/0009-efi_runtime-limit-the-amount-of-data-copied-to-users.patch
delete mode 100644 meta-luv/recipes-core/fwts/fwts/0010-efi_runtime-get_nextvariable-copy-only-the-needed-na.patch
delete mode 100644 meta-luv/recipes-core/fwts/fwts/0011-uefirtvariable-allow-large-sizes-for-variable-names.patch
create mode 100644 meta/conf/machine/genericarmv8.conf
create mode 100644 meta/conf/machine/genericarmv8b.conf
create mode 100644 meta/conf/machine/include/arm64/arch-armv8.inc
--
1.7.9.5
7 years, 2 months
[PATCH v1 00/15] luvOS support for ARM64 architecture
by Naresh Bhat
After merging luv-dizzy-wip branch many patches are dropped out compared to RFC series.
This is a very minimal set of patches which will help to build and run luvOS distribution
for aarch64 architecture. With this set of patches you can build and run the luvOS distribution
for genericarmv8 machine. I have verified the luvOS distribution on ARM64 FVP base model.
The flow of luvOS distribution on arm64 architecture
<boot> -> <upstream GRUB> -> leg-kernel with ACPI support -> efivarfs -> fwts -> kernel-efi-warnings -> <DONE>
More information and logs visit linaro - https://wiki.linaro.org/LEG/Engineering/luvOS
git repository - http://git.linaro.org/people/naresh.bhat/luvOS/luv-yocto.git/shortlog/ref...
Changes since V0:[RFC series]
- Add all the comments from Matt Fleming on RFC series
- Rebase all patches on top of v1.2-rc3-dizzy
- cherry pick few patches from upstream
- Drop all the unnecessary aarch64 patches
Naresh
Graeme Gregory (1):
fwts : Upgrade to version 14.12.00 with ARM64 support
Mark Hatle (1):
gcc: Disable aarch64 multilib options
Naresh Bhat (13):
aarch64: Add genericarmv8 machine configuration file
Build/Fix: Build fix of syslinux for aarch64
leg-kernel: Add leg-kernel recipe
core-image-efi-initramfs: Skip some packages for aarch64
grub-native: Add grub native recipe
grub: Update grub git recipe
bootimg: Add support to install Image
grub-efi: Add to support to install grubaa64 efi
luv-efi: Update luv efi bbclass aarch64
syslinux: Fix aarch64 build is not able to find isolinux.bin
luv-live-image : correct the aarch64 cmdline
fwts : Use json header files from sysroot
luv-efi: Define bootimg dependency
meta-luv/classes/luv-efi.bbclass | 67 +-
.../fwts/fwts/Use-sysroot-path-for-json.patch | 48 +
meta-luv/recipes-core/fwts/fwts_git.bb | 18 +-
.../images/core-image-efi-initramfs.bb | 7 +-
meta-luv/recipes-core/images/luv-live-image.bb | 1 +
meta-luv/recipes-kernel/linux/leg-kernel/defconfig | 2426 ++++++++++++++++++++
meta-luv/recipes-kernel/linux/leg-kernel_git.bb | 24 +
meta/classes/bootimg.bbclass | 12 +-
meta/classes/grub-efi.bbclass | 3 +
meta/conf/machine/genericarmv8.conf | 16 +
meta/conf/machine/genericarmv8b.conf | 6 +
meta/conf/machine/include/arm64/arch-armv8.inc | 20 +
meta/recipes-bsp/grub/grub-native_git.bb | 61 +
meta/recipes-bsp/grub/grub_git.bb | 29 +-
meta/recipes-devtools/gcc/gcc-4.9.inc | 1 +
.../gcc/gcc-4.9/0057-aarch64-config.patch | 32 +
meta/recipes-devtools/syslinux/syslinux_6.01.bb | 15 +-
17 files changed, 2749 insertions(+), 37 deletions(-)
create mode 100644 meta-luv/recipes-core/fwts/fwts/Use-sysroot-path-for-json.patch
create mode 100644 meta-luv/recipes-kernel/linux/leg-kernel/defconfig
create mode 100644 meta-luv/recipes-kernel/linux/leg-kernel_git.bb
create mode 100644 meta/conf/machine/genericarmv8.conf
create mode 100644 meta/conf/machine/genericarmv8b.conf
create mode 100644 meta/conf/machine/include/arm64/arch-armv8.inc
create mode 100644 meta/recipes-bsp/grub/grub-native_git.bb
create mode 100644 meta/recipes-devtools/gcc/gcc-4.9/0057-aarch64-config.patch
--
1.7.9.5
7 years, 2 months
Linux UEFI Validation Project v1.2-rc4 release
by Matt Fleming
Folks, v1.2-rc4 is available for download now at the usual location,
https://download.01.org/linux-uefi-validation/v1.2/luv-live-v1.2-rc4.tar.bz2
This will be the last release candidate for the v1.2 series, and I'm
planning on releasing v1.2 the week of 23rd March.
The biggest change in this rc is the move from Dora to Dizzy, and the
subsequent recipe fixes that were required. Big thanks to Ricardo for
taking on that mammoth task.
We've also got some preparatory arm64 patches from Naresh, with more
expected to make it in before v1.2 lands.
There's a lot of moving pieces in this release, so now would be a good
time to run it through a round of testing. And please, report your test
results.
I haven't included all the patches that went in between v1.2-rc3 and
v1.2-4 because that includes all the Yocto Project changes too. But the
shortlog for the meta-luv specific changes looks like this,
Matt Fleming (1):
LUV v1.2-rc4
Naresh Bhat (4):
leg-kernel: Add leg-kernel recipe
core-image-efi-initramfs: Skip some packages for aarch64
luv-efi: Update luv efi bbclass aarch64
luv-live-image: Correct the aarch64 cmdline
Ricardo Neri (16):
Merge branch 'dizzy' into ricardo/luv-dizzy
bits: deploy from the source directory
chipsec: utilize a git commit ID rather than a tag
core-image-efi-initramfs: populate /dev with makedevs
fwts: rename build dependency libjson to json-c
fwts: inherit from autotools-brokensep
efivarfs: build from the source directory
grub-efi: append to the non-native recipe
grub-efi: do not override the do_mkimage function
ovmf: add ovmf-native
qemu: update append to qemu 2.1.0
qemu: make qemu depend on ovmf-native
luv-live-image: update checksum for license
luv-efi.bbclass: do not depend on grub-efi-native
linux-yocto-efi-test: update for the latest kernel custom recipe
Merge branch 'master' into ricardo/luv-dizzy
--
Matt Fleming, Intel Open Source Technology Center
7 years, 3 months