All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@ossystems.com.br>
To: Alexander Shashkevych <alex@stunpix.com>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: pulseaudio makes system unstable
Date: Sat, 29 Nov 2014 11:02:12 -0200	[thread overview]
Message-ID: <CAP9ODKpFY6LUoeGqVF9FMoH7_66Yfj7K9TcJ9vX6e6a4cxKr0Q@mail.gmail.com> (raw)
In-Reply-To: <CAE6DSAE9ozNn_+X5MT5iz5kkudNeApGqz7NdwgmKnjN5wgRHVw@mail.gmail.com>

On Sat, Nov 29, 2014 at 8:46 AM, Alexander Shashkevych <alex@stunpix.com> wrote:
>>>>>>> May [1] be related with your problems?
>>>>>>>
>>>>>>> [1] http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/tree/sound/soc/fsl/imx-hdmi-dma.c?h=imx_3.10.31_1.1.0_beta2#n289
>>>>>>
>>>>>> Interesting. I've found same #ifdefs in yocto branch I'm using with
>>>>>> kernel 3.10.17, but there is no #define that disables  neon's dma for
>>>>>> hdmi, so I'll define it and recompile.
>>>>>
>>>>> Yeah! That's it! No more crashes, no more unexpected exits from apps
>>>>> and even more, earlier sound was always choppy and now it is not.
>>>>> Through hdmi.
>>>>>
>>>>> I also added --disallow-exit and --exit-idle-time to pulse server and
>>>>> now it doesn't exit unexpectedly.
>>>>>
>>>>> Thank you guys! You really helped me.
>>>>
>>>> Not so fast! Now as a demonstration of gratitude you could prepare a
>>>> nice patch which do the define and apply it on our linux-imx recipe?
>>>> That would be awesome!
>>>
>>> I would be glad to do so, but to be honest, I'm not sure has it any
>>> sense, because instability was detected on imx-linux-3.10.17,
>>> meanwhile imx_3.10.31_1.1.0_beta already has this issue fixed and soon
>>> it will be integrated to yocto.
>>
>> It does as 3.10.31 is 1.8 material and 1.7 (Dizzy) will stay on
>> 3.10.17 releases.
>
> Good.
> Last question: as I can see there is no way to create generic patch
> that will cover all kernels, because each kernel from arm-extra layer
> overrides SRC_URI with its own entries. I'm not sure how to handle
> that.

I am more concerned about the base BSP; the board specific kernels are
maintainers responsibility.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9981-7854            Mobile: +1 (347) 903-9750


  reply	other threads:[~2014-11-29 13:02 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 12:12 pulseaudio makes system unstable Alexander Shashkevych
2014-11-24 13:29 ` Marco Trillo
2014-11-25 16:05   ` Alexander Shashkevych
2014-11-25 16:21     ` Daiane Angolini
2014-11-25 16:52       ` Alexander Shashkevych
2014-11-25 18:42         ` Alexander Shashkevych
2014-11-28 15:23           ` Otavio Salvador
2014-11-28 17:34             ` Alexander Shashkevych
2014-11-28 18:22               ` Otavio Salvador
2014-11-29 10:46                 ` Alexander Shashkevych
2014-11-29 13:02                   ` Otavio Salvador [this message]
2014-11-25 16:25     ` Marco Trillo
2014-11-25 17:06       ` Alexander Shashkevych
2014-11-24 20:03 ` Status of imx28evk recipes/images Simone
2014-11-25 10:58   ` Daiane Angolini
2014-11-25 11:02     ` Otavio Salvador
2014-11-25 13:24     ` Simone
2014-11-25 14:44       ` Daiane Angolini
2014-11-25 19:47         ` Simone
2014-11-27 11:55           ` Daiane Angolini
2014-11-27 12:31             ` Simone

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAP9ODKpFY6LUoeGqVF9FMoH7_66Yfj7K9TcJ9vX6e6a4cxKr0Q@mail.gmail.com \
    --to=otavio@ossystems.com.br \
    --cc=alex@stunpix.com \
    --cc=meta-freescale@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.