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

What is the state of the x86 port? #7978

Closed
haukepetersen opened this issue Nov 9, 2017 · 5 comments · Fixed by #8042
Closed

What is the state of the x86 port? #7978

haukepetersen opened this issue Nov 9, 2017 · 5 comments · Fixed by #8042
Assignees
Labels
Area: boards Area: Board ports Discussion: RFC The issue/PR is used as a discussion starting point about the item of the issue/PR Type: cleanup The issue proposes a clean-up / The PR cleans-up parts of the codebase / documentation

Comments

@haukepetersen
Copy link
Contributor

Every once in a while I stumble over the x86 port and wonder, what the state and our future ambitions with this are. At least on my local machin, the x86-multiboot-common does not even build ("cpu_conf.h not found), and from a code/structure perspective this port is not really the best state. Also it seems that there is not really any activity around this port for the last 2 years (hope I did not overlook anything).

So just asking: does it makes sense to (at least for now) remove the port?

@haukepetersen haukepetersen added Area: boards Area: Board ports Type: cleanup The issue proposes a clean-up / The PR cleans-up parts of the codebase / documentation Discussion: RFC The issue/PR is used as a discussion starting point about the item of the issue/PR labels Nov 9, 2017
@Kijewski
Copy link
Contributor

What is the state of the x86 port?

Abandoned and nonworking. I tried to remove it from the tree but that caused other problems so I gave it up pretty soon.

@haukepetersen
Copy link
Contributor Author

Thanks for the heads up! So would you be ok if I'll give it another try for removing it?

@haukepetersen
Copy link
Contributor Author

For the sake of documentation, it also seems like all x86 related issues (#1504, #3630, #2300) are not really active...

@emmanuelsearch
Copy link
Member

So, shall we remove aim to remove the support officially, since it is broken and no one champions making it work again?

@haukepetersen
Copy link
Contributor Author

I'd say so. As the existing code is clearly unused and broken for a long time and there was no need for fixing it, it seems that demand for this feature can't be too great... Also as nobody feels like putting in time at the moment, removing the port seems like the valid option. And as the removal is well documented (-> LOSTANDFOUND.md), we can always fix and pull the port back in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: boards Area: Board ports Discussion: RFC The issue/PR is used as a discussion starting point about the item of the issue/PR Type: cleanup The issue proposes a clean-up / The PR cleans-up parts of the codebase / documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants