Navigation Menu

Skip to content
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

Jump to bottom

runtime: support for HiSillicon Hi3519 V100 Architecture #33052

Closed
mms- opened this issue Jul 11, 2019 · 3 comments
Closed

runtime: support for HiSillicon Hi3519 V100 Architecture #33052

mms- opened this issue Jul 11, 2019 · 3 comments
Labels
FrozenDueToAge WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.

Comments

@mms-
Copy link

mms- commented Jul 11, 2019

The HiSillicon Hi3519 V100 is based on ARM but not standard arm, it does use the Cortex-A53 CPU. Possible / hard to add suport for this arch?

It does seem to have fairly wide use.

More info : http://www.hisilicon.com/-/media/Hisilicon/pdf/Surveillance_mobilecam/Hi3519AV100.pdf
@ianlancetaylor ianlancetaylor changed the title Support for HiSillicon Hi3519 V100 Architecture runtime: support for HiSillicon Hi3519 V100 Architecture Jul 11, 2019
@ianlancetaylor
Copy link
Contributor

What would have to change in Go in order to add support for this?

Go generally doesn't care about anything other than the CPU, so if it uses a standard ARM CPU what is there to do?

@ianlancetaylor ianlancetaylor added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Jul 11, 2019
@mms-
Copy link
Author

mms- commented Jul 12, 2019

That is what I thought. Hisilicon has their own modifications to Standar Library, Linux Kernel, cross compile toolchain, not sure what else, this matters not for GO?

@ianlancetaylor
Copy link
Contributor

Changes to the standard library and cross-compiler toolchain are almost certainly irrelevant to Go. Changes to the kernel could possibly matter, but only if they changed the system call interface which is extremely unlikely. So I doubt we need to do anything. Of course please let us know if you find out otherwise.

@golang golang locked and limited conversation to collaborators Jul 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@ianlancetaylor @mms- @gopherbot