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

"Hardware: BCM2835" from /proc/cpuinfo breaks wiringPi with >= rpi-4.8.y kernel #1725

Closed
clivem opened this issue Nov 18, 2016 · 4 comments
Closed

Comments

@clivem
Copy link

clivem commented Nov 18, 2016

Just noticed on Pi2B with 4.8 kernel, that /proc/cpuinfo "Hardware: BCM2835" breaks wiringPi. Suspect this is to do with recent changes to rpi-4.8.y..... ISTR, Arch used to be either BCM2708 or BCM2709, not BCM2835.

@pelwell
Copy link
Contributor

pelwell commented Nov 18, 2016

You'd be better off telling Gordon - he's got a while to make the necessary changes.

@clivem
Copy link
Author

clivem commented Nov 18, 2016

Yeah, probably would. Just sticking it here for the moment so I don't forget it. Obviously something has changed on the kernel side of things...... I also wonder if this will affect other software that for years has depended on "Hardware" from /proc/cpuinfo to determine whether dealing with original ARMv6 hardware or ARMv7. I've not checked what is in the "Hardware" field on a BCM2708 build, but I wonder if that will now use BCM2835 as well. Which if people are using that field to differentiate hardware.......

NB. Just sent Gordon a heads-up email.

@clivem clivem changed the title "Hardware: BCM2835" for kernel breaks wiringPi with rpi-4.8.y kernel "Hardware: BCM2835" from /proc/cpuinfo breaks wiringPi with >= rpi-4.8.y kernel Nov 20, 2016
@Ruffio
Copy link

Ruffio commented Dec 30, 2016

@clivem has this been resolved (by email) or what is the status of this issue?

@clivem
Copy link
Author

clivem commented Dec 30, 2016

I made Gordon aware of the issue via email. Whether he has a workaround in a new version of wiringPi, to differentiate the actual hardware in use some other way, I do not know. Anyway, I'll close the issue, based on the fact that @pelwell thought it was down to user-space to accommodate the change.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants