From: Fu Wei <fu.wei(a)linaro.org>
This patchset add xen_boot support into grup-mkconfig for
generating xen boot entrances automatically
ChangeLog:
v1 :first upstream patchset.
Fu Wei (3):
arm64: add grub_xen_boot env to indicate that we have xen_* commands
* util/grub.d/20_linux_xen.in: Add support of the xen_boot command
i386,xen: Add xen_hypervisor and xen_module aliases for i386
grub-core/loader/arm64/xen_boot.c | 8 ++++++++
grub-core/loader/i386/xen.c | 7 +++++++
util/grub.d/20_linux_xen.in | 18 +++++++++++++++---
3 files changed, 30 insertions(+), 3 deletions(-)
--
2.5.0
From: Fu Wei <fu.wei(a)linaro.org>
This patchset add xen_boot support into grup-mkconfig for
generating xen boot entrances automatically
Also update the docs/grub.texi for new xen_boot commands.
This patchset has been tested on Foudation model with a bug fix:
http://lists.gnu.org/archive/html/grub-devel/2016-02/msg00205.html
ChangeLog:
v2: add "--nounzip" option support in xen_module
use "feature_xen_boot" instead of "grub_xen_boot"
update the introduction of xen boot commands in docs/grub.texi
v1 :first upstream patchset:
http://lists.gnu.org/archive/html/grub-devel/2016-02/msg00264.html
Fu Wei (4):
arm64: add "--nounzip" option support in xen_module command
* util/grub.d/20_linux_xen.in: Add xen_boot command support
i386,xen: Add xen_hypervisor and xen_module aliases for i386
arm64: update the introduction of xen boot commands in
docs/grub.texi
docs/grub.texi | 32 +++++++++-----------------------
grub-core/loader/arm64/xen_boot.c | 17 +++++++++++++++++
grub-core/loader/i386/xen.c | 7 +++++++
grub-core/normal/main.c | 2 +-
util/grub.d/20_linux_xen.in | 13 ++++++++++---
5 files changed, 44 insertions(+), 27 deletions(-)
--
2.5.0
Hi all,
I have just done something horrid, and I apologise, but it's for the
greater good.
Turn out the commit I set as the upstream baseline commit for 2016.02
ended up smack bang in the middle of an "incident" related to the edk2
maintainers getting used to looking after a git tree rather than a
subversion repository.
As a result, I have *moved* the tag in the linaro-edk2 tree, to the
commit just before the breakage.
If anyone has been using the tag linaro-edk2-baseline-2016.02 for
their development, I would recommend that you cherry-pick your work
across to a new branch based on the _current_ version,
8de84d4242215252af9d2afecd45e2419689ee5f.
Apologies for this - in future I'll use gitk before picking a starting point :|
/
Leif
The LAN9118 driver in EDK2 has been updated to include a PCD for
over-riding the default auto-negotiation timeout.
The default setting of 4000us is not long enough for TC2, so set it to
400000.
NOTE: LAN9118 on TC2 is only working in RELEASE builds at the moment.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ryan Harkin <ryan.harkin(a)linaro.org>
---
Platforms/ARM/VExpress/ArmVExpress-CTA15-A7.dsc | 1 +
1 file changed, 1 insertion(+)
diff --git a/Platforms/ARM/VExpress/ArmVExpress-CTA15-A7.dsc b/Platforms/ARM/VExpress/ArmVExpress-CTA15-A7.dsc
index 3cd6bcc..6fee399 100644
--- a/Platforms/ARM/VExpress/ArmVExpress-CTA15-A7.dsc
+++ b/Platforms/ARM/VExpress/ArmVExpress-CTA15-A7.dsc
@@ -167,6 +167,7 @@ [PcdsFixedAtBuild.common]
# Ethernet (SMSC LAN9118)
gEmbeddedTokenSpaceGuid.PcdLan9118DxeBaseAddress|0x1A000000
+ gEmbeddedTokenSpaceGuid.PcdLan9118DefaultNegotiationTimeout|400000
#
# Define the device path to the FDT for the platform
--
2.1.4
Hello all,
I'm having a problem that is platform specific, but perhaps more of a
generic problem.
When ARM's Juno board boots, not all devices are connected. The first
boot creates the boot variables and sets their order, meaning that we
get the following list on the first attempt:
EFI Misc Device
EFI Misc Device 1
EFI Internal Shell
Intel BDS then attempts to boot from one of the devices and ends up in
Shell. After exiting Shell, the Intel BDS console GUI comes up.
Selecting the Boot Manager option shows more devices being connected
and the list becomes longer:
EFI Misc Device
EFI Misc Device 1
EFI Internal Shell
EFI Hard Drive
EFI Network
Subsequent boots will never attempt to boot from Hard Drive or Network
because Shell will always succeed. That is not good.
Leif has a patch in his working tree that solves this problem [1] by
making the platform call BdsLibConnectAll() at init time. So now, the
first time boot order looks sane:
EFI Misc Device
EFI Misc Device 1
EFI Hard Drive
EFI Network
EFI Internal Shell
However, then the board is booting, the "EFI Network" fails to boot
the first time and so the board drops back to Shell again:
Warning: LAN9118 Driver in stopped state
Link timeout in auto-negotiation.
Lan9118: Auto Negociation not supported.
EhcExecTransfer: transfer failed with 2
EhcControlTransfer: error - Device Error, transfer - 2
Buffer: EFI Hard Drive
Booting EFI Misc Device
Booting EFI Misc Device 1
Booting EFI Hard Drive
Booting EFI Network
Warning: LAN9118 Driver not initialized
Link timeout in auto-negotiation.
Lan9118: Auto Negociation not supported.
Booting EFI Internal Shell
Exiting Shell drops the user back to the Intel BDS UI. Selecting
"Continue" then succeeds in booting from the EFI Network:
Booting EFI Misc Device
Booting EFI Misc Device 1
Booting EFI Hard Drive
Booting EFI Network
..MnpFreeTxBuf: Duplicated recycle report from SNP.
MnpFreeTxBuf: Duplicated recycle report from SNP.
[snip repeated SNP errors]
If I duplicate the call to BdsLibConnectAll() [2], then boot works as
expected. On first boot, the boot order is created correctly and EFI
Network pulls down a file and boots it.
I'm assuming that the 2nd call is connecting things that didn't
connect the first time. And from that, I suspect/guess that perhaps
they didn't connect due to either ordering or timing.
Is there a recommended way to set the order things are connected? Is
it even possible to specify dependencies or order? And if so, how do
we work out what the order should be?
Regards,
Ryan.
[1] https://git.linaro.org/uefi/linaro-edk2.git/commitdiff/bfbd0ef1a182e1baa120…
[2] https://git.linaro.org/landing-teams/working/arm/edk2.git/commitdiff/25320b…
This small series removes a fair amount of broken code used to create
default boot entries and install DT blobs depending upon that variant of
the board this the code is running on.
Changes since v1:
- fixed rebase conflict in the 2nd patch where I accidentally left
in a hunk from a different commit not due to be upstreamed.
[PATCH v2 1/2] ArmPlatformPkg/ArmJunoPkg: don't create default boot entries
[PATCH v2 2/2] ArmPlatformPkg/ArmJunoPkg: only have 1 PCD for the FDT
This series can be found here:
https://git.linaro.org/landing-teams/working/arm/edk2.git/shortlog/refs/tag…
Since we've pushed a load of patches to move ARM Ltd platform support
from EDK2 to OpenPlatformPkg, it's time for a cleanup of the configs we
hold.
[PATCH 1/5] platforms.config: build from OpenPlatformPkg
[PATCH 2/5] platforms.config: remove ARM_FOUNDATION_FVP
[PATCH 3/5] platforms.config: add fvp_gicv2_legacy
[PATCH 4/5] platforms.config: fvp_full: enable PL111
[PATCH 5/5] platforms.config: remove obsolete ARM Ltd configs