You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am an upstream Linux kernel developer who intends on contributing to arch/riscv, mostly in my free time.
I got a Milky-V Pioneer which uses a sg2042 chip with 64 cores, and after some analysis I found out this repo has more work on top of it compared to milkyv repo.
Is there any effort trying to upstream those changes?
If not, which branch is closest to upstream?
Also, I found some performance issues I would like to try fixing, but I can't say if it's already fixed upstream.
Having a branch closer to v6.12 would make much simpler to sort that out.
Thanks!
Leo
The text was updated successfully, but these errors were encountered:
You are very welcome to participate. Some people in the community have already participated in doing some upstream work for SG2042/Pioneerbox. I currently maintain a latest update at https://github.com/sophgo/linux/wiki, you can look at the SG2042 part.
Some of the work has been merged into the mainline (Accepted), some are still in progress (Under Review or Under Dev~), and some are still to be claimed (Not Started).
Looking forward to your participation.
There are some documents on the wiki that you can take a look at first. If you have any questions, you can contact me (Chen Wang [email protected], or send an email directly to the linux-riscv mailing list, other participants should be there.
Hello!
I am an upstream Linux kernel developer who intends on contributing to arch/riscv, mostly in my free time.
I got a Milky-V Pioneer which uses a sg2042 chip with 64 cores, and after some analysis I found out this repo has more work on top of it compared to milkyv repo.
Is there any effort trying to upstream those changes?
If not, which branch is closest to upstream?
Also, I found some performance issues I would like to try fixing, but I can't say if it's already fixed upstream.
Having a branch closer to v6.12 would make much simpler to sort that out.
Thanks!
Leo
The text was updated successfully, but these errors were encountered: