On 9 May 2014 23:07, Leif Lindholm <leif.lindholm@linaro.org> wrote:

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.

As previously mentioned, I don't want to take ownership of the ethernet driver. So here's my idea:

"Someone" adds the networking INFs to ArmVExpressPkg/ArmVExpress.dsc.inc or ArmPlatformPkg/ArmPlatformPkg.dec, or whichever is most appropriate. They would be guarded with a "!ifdef USE_LAN91X".

Optionally, I add "USE_LAN91X" to the DSC files for the models.

Then, my topic will still build standalone, and when combined with the -lan91x topic, it will also build with networking enabled.

If we don't add the "USE_LAN91X" to the DSC files, it can be added to uefi-build.sh instead; which might be a better option anyway.

And in fact, most of the INFs we add are for generic networking, so perhaps there should be one define for networking includes and one for each driver? That would mean that A9 and TC2 don't need to manually include the networking stuff - and it would simplify the DSC files for each platform.

Would that work?

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

_______________________________________________
Linaro-uefi mailing list
Linaro-uefi@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-uefi