Hey Nicolas,
In working on my 2.6.37 based merge tree of the linaro and android
kernels, I've been seeing a crash or hang at init time on my beagleboard
xm.
I reproduced it with your linaro-2.6.37 tree, and I managed to bisect it
down to the following commit:
ff8ea0c44f666883ef1e5545c33f858557b02043 ARM: 6384/1: Remove the domain
switching on ARMv6k/v7 CPUs
Reverting this patch allows the linaro-2.6.37 kernel to boot on a linaro
disk image, and also allows my dev/linaro.android branch to boot using
an android disk image.
Is anyone else seeing this issue?
thanks
-john
On Thu, 27 Jan 2011, Thomas Abraham wrote:
> On 27 January 2011 19:35, Angus Ainslie <angus.ainslie(a)linaro.org> wrote:
> > Hi Thomas,
> >
> > Thanks for pointing out that mailing list. Can you have a quick look a the
> > included patch and tell me if you've seen these upstream for the v310. I
> > found a similar one for the v210 but not the v310.
> >
> > The patch is untested as I haven't received my hardware yet.
>
> Hi Angus,
>
> pdma patch was submitted. The link to the patch is
> http://www.spinics.net/lists/arm-kernel/msg108006.html
>
> I have not seen any patch to change IRQ_EINT(5) trigger level.
>
> defconfig for s5pv310 was deliberately avoided by the maintainer
> because of linus being unhappy with too many defconfigs. So for
> s5pv310, the s5pv210_defconfig is used.
As I'd prefer to use patches in the Linaro kernel tree which are as
close as possible to upstream including proper authorship attributions,
could you direct me to a git repo where I could find them?
Alternatively, can you resend them to me? Extracting patches from
mailing list archives is not practical.
Nicolas
(repost from debian-arm list)
Hi everyone,
As a follow-up event to http://wiki.debian.org/Sprints/2011/EmdebianSprint
Genesi is also organizing an event in San Antonio. Details about the event
can be found here:
http://wiki.debian.org/Sprints/2011/GenesiSprintSanAntonio
We would like all interested parties to add their names on the wiki page. As
this is a sprint, budget is limited so we can't bring too many people
overseas, though we do have allocated accommodation space for more than the
usual Sprint (~20). For that reason we will give priority to developers from
the US or Latin America.
This one will be a slightly broader-than-Debian event, as we will most-likely
have Freescale engineers from Austin as well, and things like closed-drivers
issues will be available for discussion. We would be especially happy if
Linaro guys eg. from the Kernel and/or Graphics Working Group would be able to
attend :)
For any questions, please email any of the contacts listed in the wiki page.
Regards
Konstantinos
Hi,
In addition to our in-house validation and testing this is a call for
help in testing the images Linaro produces. If you have supported
hardware, as found on:
http://snapshots.linaro.org/10.11-daily/linaro-hwpacks/
and are willing to test, please make your way to:
http://wiki.linaro.org/Releases/DailyBuilds
for an explanation on how to test and submit your results to the QA
tracker at:
http://qatracker.linaro.org
For an explanation of how to use the qatracker please see:
https://wiki.linaro.org/QA/QATracker
Community testing is essential if we are to produce well integrated and
robust Linux on ARM images, with your help we can get there.
Regards,
Jamie.
--
Linaro Release Manager
* Period: (20110120-20110126)
* PM: Ian Smith <ian.smith(a)linaro.org>
* Past reports : https://wiki.linaro.org/Platform/Validation
* Burndown information : http://status.linaro.org
== Key Points for wider discussion ==
* A demonstration of components.linaro.org was delivered.
* Work on a hudson instance to build QEMU images for different board types.
* Got the Panda board master image working and documented
* Investigations into messaging processes to enhance the validation
test farm.
== Team Highlights ==
* A demonstration of components.linaro.org (to show the different
elements that make up the full images - therefore the components may be
updated more regularly) was produced which stimulated additional discussion.
* Discussions with the Power Management group are ongoing to determine
how best to integrate the PM tests into the testing framework.
* Additional work on authorisation systems in Launch Control.
* Working on a hudson instance with additional scripts to use
LinaroMediaCreate to produce QEMU images for different board types.
* The Panda board master image (mentioned above) was used on 2 boards
for the validation farm in Cambridge.
* Investigations into messaging processes looked at RabbitMQ and Celery
to look to improve the validation test farm.
== Upcoming Deliverables ==
* No immediate milestones due.
=== Blueprint Milestones ===
* No immediate milestones due
== Risks / Issues ==
* None to be highlighted.
== Miscellaneous ==
* Spring Zhang leave February 1st - 11th.
* Period: (20110120-20110126)
* PM: Ian Smith <ian.smith(a)linaro.org>
* Past reports : https://wiki.linaro.org/Platform/Infrastructure
* Burndown information : http://status.linaro.org
== Key Points for wider discussion ==
* status.linaro.org has now been deployed, and is being refined. This
site allows progress and reporting information to be observed.
* RT tickets are being monitored by the Infrastructure team. If there
is an IS issue, the Infrastructure team may be able to assist.
* The Infrastructure Stakeholder review meeting is taking place on 3rd
February.
* A private instance of hudson building Android on EC2 has been produced.
== Team Highlights ==
* status.linaro.org being deployed (see above).
* The RT ticket queue is increasing following the involvement of the
Infrastructure team, which ensure the correct visibility of IS issues
affecting Linaro.
* Preparations are under way for the next Infrastructure Stakeholder
meeting w/b 31st January.
* The hudson instance building Android will be migrated to the Linaro
account when it is ready.
== Upcoming Deliverables ==
* No immediate milestones due.
=== Stakeholder Process ===
* OverallStatusReporting - scheduled for end of January, and this is
currently in use, and some enhancements are being added.
* As noted above, the next meeting will be on 3rd February.
=== Blueprint Milestones ===
* No immediate milestones due
== Risks / Issues ==
* None to be highlighted.
== Miscellaneous ==
* Mattias Backman joined the team on 24th January.