Hi all,
I have now pushed a second alpha of 2014.05, but it will not be a
release candidate, since all of the software models are currently
lacking networking support.
All 15 platforms do build for both DEBUG and RELEASE targets, though -
at least on my local pc.
Expect -a3 and -rc1 next week.
/
Leif
Hi all,
I have set a new baseline at upstream commit
7447345a364e6aa5f5bd5219d25d28a2d6147bce.
Due to upstream changes, linaro-platform-tc2 and linaro-platform-a9
failed to rebase cleanly - Ryan is looking into that.
Since we now have all of the required support in the upstream Bds to
boot properly, we are leaving out the linaro-topic-bds patched for
this round. This will have an impact on validation.
Also, linaro-topic-pxeboot is being put out to pasture since Olivier
pushed the Ethernet driver last week. We may need to carry side
patches for model platforms that use a different driver.
I have pushed linaro-edk2-2014.05-a1, but we will be waiting for at
least another alpha including the two mentioned platform topics.
/
Leif
Hi Leif,
I have make a multiboot support patch V3 following all your suggestion
The main change are :
(1)separate all the xen specific code to multiboot_xen.c and multiboot_xen.h
(2)support for ramdisk and xsm
(3)fully support http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/Multiboot
and xen/docs/misc/arm/device-tree/booting.txt in Xen source code.
(4)there is not limit in the module's number
For the test log, please check :
https://staging.validation.linaro.org/scheduler/job/46542/log_file
I have tested it locally, it works fine for me.
Please check the patch, and provide some suggestions.
Thank you very much!
--
Best regards,
Fu Wei
Enterprise Server Engineer From Red Hat
LEG Team
Linaro.org | Open source software for ARM SoCs
Ph: +86 186 2020 4684 (mobile)
IRC: fuwei
Skype: tekkamanninja
Room 1512, Regus One Corporate Avenue,Level 15,
One Corporate Avenue,222 Hubin Road,Huangpu District,
Shanghai,China 200021
Hi Olivier,
thanks for the inputs.
Yes agreed, it is specific to chipset/SoC not Architecture specific.
thanks
Ganapat
On Thu, May 1, 2014 at 3:25 PM, Olivier Martin <olivier.martin(a)arm.com>wrote:
> Hi Ganapat,
>
>
>
> You will need to implement the UEFI protocols:
>
> - EFI_PCI_HOST_BRIDGE_RESOURCE_ALLOCATION_PROTOCOL
>
> - EFI_PCI_ROOT_BRIDGE_IO_PROTOCOL
>
>
>
> Your driver will be more tied to your PCI Root Complex than the Aarch64
> architecture itself.
>
>
>
> PcAtChipsetPkg/PciHostBridgeDxe might be a good candidate to start with.
> But again, your driver will be chipset specific, not architecture specific.
>
>
>
> Olivier
>
>
>
> *From:* Ganapatrao Kulkarni [mailto:gpkulkarni@gmail.com]
> *Sent:* 01 May 2014 10:28
> *To:* linaro-uefi(a)lists.linaro.org; Olivier Martin
> *Subject:* PCI driver support on ARM64 platforms.
>
>
>
> Hi All,
>
> We want to understand how to enable/add PCI support for ARM64 based
> platforms in UEFI.
>
> Any suggestion on where to start from? which driver needs to be referred?
>
> Can we use PcAtChipsetPkg/PciHostBridgeDxe to start with?
>
> what are the changes required to port PcAtChipsetPkg/PciHostBridgeDxe to
> support ARM64 platforms?
>
> I appreciate your advise on this!
>
> thanks in advance
>
> Ganapat
>
>
>
Hi All,
We want to understand how to enable/add PCI support for ARM64 based
platforms in UEFI.
Any suggestion on where to start from? which driver needs to be referred?
Can we use PcAtChipsetPkg/PciHostBridgeDxe to start with?
what are the changes required to port PcAtChipsetPkg/PciHostBridgeDxe to
support ARM64 platforms?
I appreciate your advise on this!
thanks in advance
Ganapat
