Fixes for board autodetection (Banana Pi legacy) #225
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
My new build host is up and running (6-core i7 with 3.x GHz, fast SSD and plenty of RAM). I chose 16.04 LTS and 5.2 and just created and tested a Jessie desktop image for Banana Pi: http://sprunge.us/HZDM
Crazy shit, everything's working out of the box, I connected an USB disk lying around, clicked on a large .mp4 now the Banana is playing 1080p/H.264 smoothly, then I tried suspend to RAM just to realize that we've to define the correct Pin mapping for the power button to be able to resume ;)
In other words: Switching from 14.04 LTS to 16.04 LTS on the build host shouldn't be a problem and also using Linaro's GCC 5.2 :)