Working device tree for the HifiveU
What is the correct device tree for the HifiveU that works both with 5.2+ and U-Boot?
Andreas.
Signature · 8 lines
Andreas Schwab, SUSE Labs, [email protected] GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." _______________________________________________ linux-riscv mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-riscv
Quoted 2 lines · Andreas Schwab
What is the correct device tree for the HifiveU that works both with 5.2+ and U-Boot?
U-Boot should follow the kernel's DT data:
Thus the upstream-bound data is currently here:
https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/log/?h=fixes
However, since some FU540 U-Boot drivers were upstreamed before the kernel DT data was posted and reviewed, it's necessary to patch upstream U-Boot to use the upstream-bound DT data format. One of the patches required can be found here:
https://lists.denx.de/pipermail/u-boot/2019-May/370814.html
- Paul
_______________________________________________
linux-riscv mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-riscv
Quoted 11 lines · Paul Walmsley
Quoted 2 lines · Andreas Schwab
What is the correct device tree for the HifiveU that works both with 5.2+ and U-Boot?
U-Boot should follow the kernel's DT data:
Thus the upstream-bound data is currently here:
Quoted 8 lines
https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/log/?h=fixes
However, since some FU540 U-Boot drivers were upstreamed before the kernel DT data was posted and reviewed, it's necessary to patch upstream U-Boot to use the upstream-bound DT data format. One of the patches required can be found here:
Any patch to make serial work again?
Andreas.
Signature · 8 lines
Andreas Schwab, SUSE Labs, [email protected] GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." _______________________________________________ linux-riscv mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-riscv
Quoted 5 lines · Paul Walmsley
Quoted 2 lines · Andreas Schwab
What is the correct device tree for the HifiveU that works both with 5.2+ and U-Boot?
Quoted 7 lines
U-Boot should follow the kernel's DT data:
Thus the upstream-bound data is currently here:
https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/log/?h=fixes
That is completely useless.
Andreas.
Signature · 8 lines
Andreas Schwab, SUSE Labs, [email protected] GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." _______________________________________________ linux-riscv mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-riscv
Quoted 9 lines · Andreas Schwab
Quoted 7 lines · Paul Walmsley
Quoted 2 lines · Andreas Schwab
What is the correct device tree for the HifiveU that works both with 5.2+ and U-Boot?
U-Boot should follow the kernel's DT data:
Quoted 7 lines
Quoted 5 lines
Thus the upstream-bound data is currently here:
https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/log/?h=fixes
That is completely useless.
If you have specific questions or comments, I or someone else would be happy to try to help you out. Otherwise, there's not much that we can do.
- Paul
_______________________________________________
linux-riscv mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-riscv
Quoted 13 lines · Paul Walmsley
Quoted 11 lines · Andreas Schwab
Quoted 9 lines · Paul Walmsley
Quoted 2 lines · Andreas Schwab
What is the correct device tree for the HifiveU that works both with 5.2+ and U-Boot?
U-Boot should follow the kernel's DT data:
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines
Thus the upstream-bound data is currently here:
https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/log/?h=fixes
That is completely useless.
If you have specific questions or comments, I or someone else would be happy to try to help you out. Otherwise, there's not much that we can do.
It doesn't even have ethernet, so how can it be of any use?
Andreas.
Signature · 8 lines
Andreas Schwab, SUSE Labs, [email protected] GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." _______________________________________________ linux-riscv mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-riscv
Quoted 23 lines · Andreas Schwab
Quoted 17 lines · Paul Walmsley
Quoted 15 lines · Andreas Schwab
Quoted 12 lines · Paul Walmsley
Quoted 2 lines · Andreas Schwab
What is the correct device tree for the HifiveU that works both with 5.2+ and U-Boot?
U-Boot should follow the kernel's DT data:
Thus the upstream-bound data is currently here:
https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/log/?h=fixes
Quoted 9 lines
Quoted 4 lines
Quoted 1 line
That is completely useless.
If you have specific questions or comments, I or someone else would be happy to try to help you out. Otherwise, there's not much that we can do.
It doesn't even have ethernet, so how can it be of any use?
Andreas.
Could we please include Yash’s macb patches (and associated device tree changes) in the ‘fixes’ branch on
https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git
_______________________________________________
linux-riscv mailing list [email protected]
http://lists.infradead.org/mailman/listinfo/linux-riscv
Quoted 17 lines · Andreas Schwab
Quoted 15 lines · Paul Walmsley
Quoted 13 lines · Andreas Schwab
Quoted 11 lines · Paul Walmsley
Quoted 2 lines · Andreas Schwab
What is the correct device tree for the HifiveU that works both with 5.2+ and U-Boot?
U-Boot should follow the kernel's DT data:
Thus the upstream-bound data is currently here:
Quoted 8 lines
Quoted 6 lines
Quoted 3 lines
That is completely useless.
If you have specific questions or comments, I or someone else would be happy to try to help you out. Otherwise, there's not much that we can do.
It doesn't even have ethernet, so how can it be of any use?
We can't add the Ethernet data yet, since it hasn't been approved by the DT maintainers. But of course you can always add it yourself to your own kernel branch, along with the driver.
- Paul
_______________________________________________
linux-riscv mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-riscv
Quoted 3 lines · Paul Walmsley
We can't add the Ethernet data yet, since it hasn't been approved by the DT maintainers. But of course you can always add it yourself to your own kernel branch, along with the driver.
Which driver?
Andreas.
Signature · 8 lines
Andreas Schwab, SUSE Labs, [email protected] GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." _______________________________________________ linux-riscv mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-riscv
Quoted 26 lines · Troy Benjegerdes
Quoted 26 lines · Andreas Schwab
Quoted 21 lines · Paul Walmsley
Quoted 9 lines · Andreas Schwab
Quoted 7 lines · Paul Walmsley
Quoted 2 lines · Andreas Schwab
What is the correct device tree for the HifiveU that works both with 5.2+ and U-Boot?
U-Boot should follow the kernel's DT data:
Quoted 7 lines
Quoted 5 lines
Thus the upstream-bound data is currently here:
https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/log/?h=fixes
That is completely useless.
If you have specific questions or comments, I or someone else would be happy to try to help you out. Otherwise, there's not much that we can do.
Quoted 8 lines
Quoted 4 lines
It doesn't even have ethernet, so how can it be of any use?
Andreas.
Could we please include Yash’s macb patches (and associated device tree changes) in the ‘fixes’ branch on
https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git
Yash's DT binding need to be approved by the DT maintainers first. And ideally, his MACB driver change needs to be merged first by the networking maintainers.
Once that happens, we'll be able to add Ethernet support to the upstream FU540 and HiFive Unleashed device tree data files.
- Paul
_______________________________________________
linux-riscv mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-riscv
Quoted 7 lines · Andreas Schwab
Quoted 3 lines · Paul Walmsley
We can't add the Ethernet data yet, since it hasn't been approved by the DT maintainers. But of course you can always add it yourself to your own kernel branch, along with the driver.
Which driver?
This one:
https://lore.kernel.org/linux-riscv/[email protected]/T/#u
Note that Yash is planning to post a v3 with the CONFIG_MACB_SIFIVE_FU540 conditional removed.
- Paul
_______________________________________________
linux-riscv mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-riscv
Quoted 45 lines · Paul Walmsley
Quoted 26 lines · Troy Benjegerdes
Quoted 26 lines · Andreas Schwab
Quoted 21 lines · Paul Walmsley
Quoted 9 lines · Andreas Schwab
Quoted 7 lines · Paul Walmsley
Quoted 2 lines · Andreas Schwab
What is the correct device tree for the HifiveU that works both with 5.2+ and U-Boot?
U-Boot should follow the kernel's DT data:
Quoted 7 lines
Quoted 5 lines
Thus the upstream-bound data is currently here:
https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.git/log/?h=fixes
That is completely useless.
If you have specific questions or comments, I or someone else would be happy to try to help you out. Otherwise, there's not much that we can do.
Quoted 8 lines
Quoted 4 lines
It doesn't even have ethernet, so how can it be of any use?
Andreas.
Could we please include Yash’s macb patches (and associated device tree changes) in the ‘fixes’ branch on
https://git.kernel.org/pub/scm/linux/kernel/git/riscv/linux.gitYash's DT binding need to be approved by the DT maintainers first. And ideally, his MACB driver change needs to be merged first by the networking maintainers.
Quoted 5 lines
Once that happens, we'll be able to add Ethernet support to the upstream FU540 and HiFive Unleashed device tree data files.
- Paul
Can we at least put it in some kind of ‘under review’ branch on the shared git tree so everything we need (including other stuff like GPIO drivers) is all in one place?
We used to do this with some of the github riscv-linux trees.
_______________________________________________
linux-riscv mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-riscv
Quoted 5 lines · Troy Benjegerdes
Can we at least put it in some kind of ‘under review’ branch on the shared git tree so everything we need (including other stuff like GPIO drivers) is all in one place?
We used to do this with some of the github riscv-linux trees.
Yash has already been kind enough to post his own test branch for these patches, along with dependencies:
https://github.com/yashshah7/riscv-linux/commits/dev/yashs/ethernet_v2
If you want something more, you're of course welcome to maintain such an unofficial branch on one of your personal git trees, or in a personal branch of one of SiFive's git trees, if you wish.
- Paul
_______________________________________________
linux-riscv mailing list
[email protected]
http://lists.infradead.org/mailman/listinfo/linux-riscv
Quoted 4 lines · Paul Walmsley
Yash has already been kind enough to post his own test branch for these patches, along with dependencies:
https://github.com/yashshah7/riscv-linux/commits/dev/yashs/ethernet_v2
That doesn't work with U-Boot.
Andreas.
Signature · 8 lines
Andreas Schwab, SUSE Labs, [email protected] GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7 "And now for something completely different." _______________________________________________ linux-riscv mailing list [email protected] http://lists.infradead.org/mailman/listinfo/linux-riscv