On Tue, May 24, 2011 at 2:04 AM, Eric Miao wrote:
> On Mon, May 23, 2011 at 11:24 AM, Eric Miao wrote:
>> On Sat, May 21, 2011 at 12:39 AM, Kurt Taylor
>> wrote:
>>> On Fri, May 20, 2011 at 1:44 AM, Eric Miao wrote:
Hi all,
When debugging video playback performance issue, we fou
On Mon, May 23, 2011 at 11:24 AM, Eric Miao wrote:
> On Sat, May 21, 2011 at 12:39 AM, Kurt Taylor wrote:
>> On Fri, May 20, 2011 at 1:44 AM, Eric Miao wrote:
>>> Hi all,
>>>
>>> When debugging video playback performance issue, we found that pulseaudio is
>>> eating up 100% cpu time. Just in cas
On Thu, 19 May 2011 17:05:09 +1200, Michael Hudson-Doyle
wrote:
> Hi there,
>
> Some of you know about this already as it was discussed a bit at LDS,
> but probably not very inclusively.
>
> We have a slightly strange arrangement of projects on Launchpad, with
> the main ones being "launch-cont
On Tue, May 24, 2011 at 10:33 AM, Michael Casadevall
wrote:
> On 05/19/2011 10:56 AM, David Gilbert wrote:
>> On 19 May 2011 16:49, Ken Werner wrote:
>>> On 05/19/2011 12:40 PM, David Rusling wrote:
Is this going to end up in a blueprint? This is the last loose end of
SMP / atomi
On 05/19/2011 10:56 AM, David Gilbert wrote:
> On 19 May 2011 16:49, Ken Werner wrote:
>> On 05/19/2011 12:40 PM, David Rusling wrote:
>>>
>>> Is this going to end up in a blueprint? This is the last loose end of
>>> SMP / atomic memory operations work and I'd like to see it happen
>>
>> Hi,
>>
On Mon, May 23, 2011 at 5:00 PM, Jaswinder Singh
wrote:
> On 24 May 2011 00:53, Ricardo Salveti wrote:
Can you boot with omapdss.debug=1 drm.debug=7 and give me your kernel log?
>>>
>>> Please find the log attached.
>>
>> Interesting, the driver didn't find your monitor at all!
>> [ 5.738
I just noticed today an online code cycle analyzer that targets the
Cortex-A8:
http://pulsar.webshaker.net/ccc/index.php?lng=us
Does anyone know who the author of that is, and whether he'd be
interested in doing an A9 update?
--
Christian Robottom Reis | [+55 16] 3376 0125 | http://launchp
On 24 May 2011 00:53, Ricardo Salveti wrote:
>>> Can you boot with omapdss.debug=1 drm.debug=7 and give me your kernel log?
>>
>> Please find the log attached.
>
> Interesting, the driver didn't find your monitor at all!
> [ 5.738037] omapdss HDMI: Fail to detect the connector and force is
> en
On Mon, May 23, 2011 at 3:27 PM, Jaswinder Singh
wrote:
> On 23 May 2011 05:44, Ricardo Salveti wrote:
>> On Sun, May 22, 2011 at 4:44 AM, Jaswinder Singh
>> wrote:
>>> On 22 May 2011 04:38, John Rigby wrote:
This is the same problem that marcin and I have seen. See
https://bugs.laun
Hi John,
echo blacklist wl12xx_sdio > /etc/modprobe.d/blacklist-wireless.conf
reboot
Doesn't change the behavior on my Xm.
Anything else you want me to try just hollar.
Regards,
Tom
On Mon, May 23, 2011 at 10:52 AM, John Rigby wrote:
> On Mon, May 23, 2011 at 9:50 AM, Tom Gall wrote:
>> I've
On Fri, 2011-05-20 at 12:49 -0400, James Westby wrote:
> On Fri, 20 May 2011 17:32:27 +0100, David Gilbert
> wrote:
> > On 20 May 2011 17:12, James Westby wrote:
> > > On Fri, 20 May 2011 16:03:16 +0100, Peter Maydell
> > > wrote:
> > >> We're only doing this once a month, we should just produ
On Mon, May 23, 2011 at 9:50 AM, Tom Gall wrote:
> I've also seen it on my beagle Xm from time to time. Agree, be nice to
> figure out who is
> blocked and why.
>
ok, its not the wireless driver mishaving then
___
linaro-dev mailing list
linaro-dev@list
I have only seen this with the wireless problem already noted. Can
you see if blacklisting the wireless driver fixes the problem?
echo blacklist wl12xx_sdio > /etc/modeprobe.d/blacklist-wireless.conf
reboot
On Mon, May 23, 2011 at 7:10 AM, Christian Robottom Reis
wrote:
> Hi there,
>
> I'm
I've also seen it on my beagle Xm from time to time. Agree, be nice to
figure out who is
blocked and why.
On Mon, May 23, 2011 at 8:10 AM, Christian Robottom Reis
wrote:
> Hi there,
>
> I'm playing around with the latest snapshots on my IGEPv2 and I'm
> seeing a recurring message posted to the
Dnia 2011-05-23, pon o godzinie 10:10 -0300, Christian Robottom Reis
pisze:
> Hi there,
>
> I'm playing around with the latest snapshots on my IGEPv2 and I'm
> seeing a recurring message posted to the console while using it:
>
> [ 1561.340942] INFO: task kworker/0:0:1030 blocked for more
Hi there,
I'm playing around with the latest snapshots on my IGEPv2 and I'm
seeing a recurring message posted to the console while using it:
[ 1561.340942] INFO: task kworker/0:0:1030 blocked for more than 120
seconds.
[ 1561.350860] "echo 0 > /proc/sys/kernel/hung_task_timeou
On 23 May 2011 16:54, Patrik Ryd wrote:
> The file init.ompa4.sh only contained one line for setting
> ro.runtime.device. This property is not used so the file
> can be removed.
hi Patrik,
Thanks for cleaning up. It looks great to me.
So, we are going to be more consistent in device/linaro/com
The file init.ompa4.sh only contained one line for setting
ro.runtime.device. This property is not used so the file
can be removed.
Bug #747911
---
AndroidBoard.mk |5 -
init.omap4.rc |3 ---
init.omap4.sh |3 ---
3 files changed, 0 insertions(+), 11 deletions(-)
delete mode
18 matches
Mail list logo
