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
Loongson Technology wants to participate in the Adoptium community. Currently, we are submitting a PR for the Loongson platform JDK (Here is our open-sourced repo on github: https://github.com/loongson/jdk8u/tree/master-ls, including LoongArch and MIPS support), see: adoptium/temurin-build#3134. Although the LoongArch platform JDK can be built by cross-compiling, but in the Adoptium community (such as Jenkins), it is definitely more convenient to have LoongArch's real machine/physical machine for testing and other activities. Loongson Technology is willing to provide LoongArch real machine/physical machine to Adoptium. How should I do it? Do you have any suggestions and any documents for reference?
The text was updated successfully, but these errors were encountered:
Based on an earlier discussion with @tellison it sounds like we are not in a position to support this in our CI until such time as the loongarch port is merged into the upstream openjdk codebase. Once this is in place we can consider adding it.
Loongson Technology wants to participate in the Adoptium community. Currently, we are submitting a PR for the Loongson platform JDK (Here is our open-sourced repo on github: https://github.com/loongson/jdk8u/tree/master-ls, including LoongArch and MIPS support), see: adoptium/temurin-build#3134. Although the LoongArch platform JDK can be built by cross-compiling, but in the Adoptium community (such as Jenkins), it is definitely more convenient to have LoongArch's real machine/physical machine for testing and other activities. Loongson Technology is willing to provide LoongArch real machine/physical machine to Adoptium. How should I do it? Do you have any suggestions and any documents for reference?
The text was updated successfully, but these errors were encountered: