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

Update linux-sun7i to 3.4.79 and add support for cubietruck #757

Merged
merged 4 commits into from
Mar 14, 2014

Conversation

mikkeloscar
Copy link
Contributor

This is a reworked version of a previous PR to update linux-sun7i to add cubietruck support.

This PR is based on the PKGBUILD and config from the current version of linux-sun7i.
I have been running this version on my cubietruck for the past week and it has been very stable for me. I also asked users in the forum to test it out on other sun7i devices: http://archlinuxarm.org/forum/viewtopic.php?f=33&t=6413&start=60

So far one other user, fcarolo, has tested it on the cubieboard2 and cubietruck and confirmed that it works on both.

Note that this kernel also includes a patched bcmdhd driver which makes the onboard wifi work on the cubietruck.

kmihelich added a commit that referenced this pull request Mar 14, 2014
Update linux-sun7i to 3.4.79 and add support for cubietruck
@kmihelich kmihelich merged commit af13e38 into archlinuxarm:master Mar 14, 2014
@mikkeloscar mikkeloscar deleted the linux-sun7i branch March 14, 2014 14:41
@TheDZhon
Copy link
Contributor

My cubieboard2 is no longer bootable after this new 3.4.79 kernel.

@fernandocarolo
Copy link

TheDZhon, this kernel requires that you set machid=0x10bb on /boot/uEnv.txt or simply omit it and let the kernel find out, instead of using machid=0xf35 as the previous kernel did. There is an updated uboot-cubieboard2 package that fixes this, but you can simply remove the old machid from /boot/uEnv.txt and your cubieboard2 will boot fine.

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

Successfully merging this pull request may close these issues.

4 participants