-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upstreaming A3700 #14
Comments
I was planning to push A3700 support this August, but my work gets delayed since we want to migrate the SERDES initialization to lower EL levels, while TF-A executes it through SMCC calls. The same mechanism already implemented in A8K family. So I believe the final A3700 pull request will be created in September-October this year. |
@kostapr Thanks, good that there is progress in sight! I was recently discussing with Debian how to improve the user experience of ESPRESSObin by packaging a recent upstream bootloader (https://lists.debian.org/debian-arm/2018/08/msg00001.html) where ATF would be a building block. I have some further issues around u-boot, though. Will put you on CC when reporting. |
@kostapr From a quick glance, it looks like a3700 support landed upstream. Is that "done", so I can just use that for my espressobin, or are there any missing bits which still need to be upstreamed? |
@dhewg I am not aware of any missing parts there. Everything should be aligned with upstream sources. |
What are the plans to get the A3700 support into upstream? https://github.com/ARM-software/arm-trusted-firmware/blob/master/docs/marvell/build.txt talks about that platform already, but the bits aren't there yet. Please clarify.
Alternatively, I can open a ticket on upstream to remove those bits from the docs so that users like me don't get confused when trying to build non-existing code.
The text was updated successfully, but these errors were encountered: