Hi
I see that by and large, the contents of SoC and Board Packages (ARM based) in
EDK2, are like this:
- Most drivers like mmc, sd, flash, timer, etc and certain Libraries
like Serial port, RTC, etc, in SoC packages (E.g. Omap35xxPkg, Omap44xxPkg,
ExynosPkg)
- For Board packages there is essentially one library that identifies
itself as ArmPlatformLib in the inf file. There are few others too, but this
one is common to all Board Packages. (E.g. BeagleBoardPkg, ArndaleBoardPkg,
PandaBoardPkg etc.)
My concerns/queries regarding such structuring are -->
1. Why is slave dependent code for storage devices like mmc, sd, etc
present in SoC packages, when it should really vary with the board/platform?
2. Having multiple driver sources for similar devices (e.g. storage
drivers in Omap35xxPkg, Omap44xxPkg) causes code duplication, as there is a lot
of common code in these drivers. Is this intentional? What is the rationale
behind it?
3. Is there any discussion going around in the EDK2 community to
streamline these driver sources, to ensure better code reusability?
Thanks
Sakar Arora
------------------------------------------------------------------------------
Dive into the World of Parallel Programming The Go Parallel Website, sponsored
by Intel and developed in partnership with Slashdot Media, is your hub for all
things parallel software development, from weekly thought leadership blogs to
news, videos, case studies, tutorials and more. Take a look and join the
conversation now. http://goparallel.sourceforge.net/
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
