On Thu, April 16, 2020 10:19 am, Peter Robinson wrote: > The proper question is why is Wandboard hostile to upstream by not > sending their device support upstream. The original commit was by a > NXP maintainer, but there's been little on the Wandboard stuff at all > since the addition of the D1 support. Another good question. But even looking at the wandboard github stuff, there doesn't appear to have been any changes since 2015 to the uboot-imx tree or the u-boot-fslc tree. C.f. https://github.com/wandboard-org I feel like they used to be so much better about pushing upstream. Or maybe the hardware manufacturer made a change without telling the wandboard crew? I find it odd that github is showing 2015 when there were clearly changed in 2017? I'm confused. Okay, I was looking at an old branch. There is a 2017 branch which has a commit to add D1 to u-boot: https://github.com/wandboard-org/uboot-imx/commit/978c09eb0d49dba37b86c23e61bc50fb1b72dc00 Of course I don't know if this commit ever made it upstream? -derek -- Derek Atkins 617-623-3745 derek@xxxxxxxxx www.ihtfp.com Computer and Internet Security Consultant _______________________________________________ arm mailing list -- arm@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to arm-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/arm@xxxxxxxxxxxxxxxxxxxxxxx
