I'm using a only tracking tip approach, which should align with our
new CI push. As the tip's stabilize I'm going to advance the release.
This way people will have a bleeding edge build and a stable build.
Many, many, many thanks to John Stultz and Nicolas Pitre whose
diligent work on 2.6.39 we were able to pick up.
This release differs from 11.06 in:
Linaro 2.6.39
HDMI comes up in the best resolution (no more 640x480 for the upstream
focused build).
I don't like the term generic build so I'm calling these
upstream-focused builds.
I'm happy to announce the first 11.07 build for generic Panda and
Beagle C4. Unfortunately Beagle xM doesn't boot, but Panda and Beagle
C4 look great!
First of all, thanks! Thanks to both you and the entire Linaro team.
Thanks for updating the BeagleBoard community and advancing the state
of software for ARM and enabling BeagleBoard owners to evaluate those
improvements for their own use and to contribute back to advancing the
state of software, especially in this case Android.
I hope that it is not seen as too much of a distraction to ask my
questions below. I know that many answers can be found on the web,
but I'd like to get your specific opinions about the answers and where
to find them, since you are publishing these release notices and
reaching out to the broader user communities.
What is the issue with the BeagleBoard-xM? Where do I find out about
the issues and introduce fixes? How do I find which
x-loader/u-boot/kernel you are using?
I'm using a only tracking tip approach, which should align with our
new CI push. As the tip's stabilize I'm going to advance the release.
This way people will have a bleeding edge build and a stable build.
Are you keeping the x-loader/u-boot/kernel rebased on the mainline
projects? How are the Rowboat project and this project utilizing each
other?
Just got a certificate security message from the links. Is everything OK?
This Connection is Untrusted
You have asked Firefox to connect securely to android-build.linaro.org, but we can’t confirm that your connection is secure. Normally, when you try to connect securely, sites will present trusted identification to prove that you are going to the right place. However, this site’s identity can’t be verified.
What Should I Do?
If you usually connect to this site without problems, this error could mean that someone is trying to impersonate the site, and you shouldn’t continue.
Zach wasn't on the BeagleBoard mailing list until *JUST NOW* when I
approved his membership request, so he never saw your post. For these
cross-mailing list posts, it is best to include everyone in the copy,
unless there is a reason to remove a certain group of people from the
thread.
Just got a certificate security message from the links. Is everything OK?
Based on the "wget --no-check-certificate" portions of Zach's message,
I'd assume that they simply don't have a valid certificate for the
site and are suggesting everyone work-around that issue. I believe
you are fine and should not need to provide any private information to
linaro.org or run scripts from that site that could potentially
compromise your system.
Since Zach only *JUST* joined this mailing list, he probably didn't
see this e-mail since you dropped him off of the copy list.
Does this mean that the build doesn't work with the Beagle C2 and C3?:
The only difference required to support C2/3 vs. C4 is to account for
the EHCI USB supply (it was moved on C4 to provide a better quality
supply). Optionally, you can utilize the additional processor speed
jump from 600MHz to 720MHz.
The related lines in u-boot to account for C2/3 vs. C4 differences are
in the mainline u-boot:
The actual patch applied is at:
I'd guess given that this was the critical change, it is unlikely the
the Linaro u-boot doesn't have something similar to mainline to
support C2/3 and C4.