blacklist evbug or remove it from the kernel config

blacklist evbug or remove it from the kernel config

[Carlos Rafael Giani]

Hello,

evbug is enabled by default with newer kernels. This is highly annoying. 
It prints a debug message for every single HID activity. Mouse movement, 
key presses etc.
It can slow down the system.

evbug is blacklisted in Ubuntu's modprobe config. I think it is wise to 
do the same in meta-fsl-arm . Blacklisting is probably more effective, 
since otherwise, the configurations of all kernels in meta-fsl-arm and 
meta-fsl-arm-extra have to be modified.

cheers

Re: blacklist evbug or remove it from the kernel config

[Daiane Angolini]

On Mon, Jun 23, 2014 at 12:57 PM, Carlos Rafael Giani
<dv@pseudoterminal.org> wrote:
> Hello,
>
> evbug is enabled by default with newer kernels. This is highly annoying. It
> prints a debug message for every single HID activity. Mouse movement, key
> presses etc.
> It can slow down the system.
>
> evbug is blacklisted in Ubuntu's modprobe config. I think it is wise to do
> the same in meta-fsl-arm . Blacklisting is probably more effective, since
> otherwise, the configurations of all kernels in meta-fsl-arm and
> meta-fsl-arm-extra have to be modified.

I agree.

Could you, please, make a patch to fix it?

Daiane
>
> cheers
> --
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale

Re: blacklist evbug or remove it from the kernel config

[Carlos Rafael Giani]

On 2014-06-23 18:03, Daiane Angolini wrote:
> On Mon, Jun 23, 2014 at 12:57 PM, Carlos Rafael Giani
> <dv@pseudoterminal.org> wrote:
>> Hello,
>>
>> evbug is enabled by default with newer kernels. This is highly annoying. It
>> prints a debug message for every single HID activity. Mouse movement, key
>> presses etc.
>> It can slow down the system.
>>
>> evbug is blacklisted in Ubuntu's modprobe config. I think it is wise to do
>> the same in meta-fsl-arm . Blacklisting is probably more effective, since
>> otherwise, the configurations of all kernels in meta-fsl-arm and
>> meta-fsl-arm-extra have to be modified.
> I agree.
>
> Could you, please, make a patch to fix it?
>
> Daiane
>> cheers
>> --
>> _______________________________________________
>> meta-freescale mailing list
>> meta-freescale@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/meta-freescale

Well, how would it ideally be fixed? By blacklisting?

Re: blacklist evbug or remove it from the kernel config

[Daiane Angolini]

On Mon, Jun 23, 2014 at 1:05 PM, Carlos Rafael Giani
<dv@pseudoterminal.org> wrote:
> On 2014-06-23 18:03, Daiane Angolini wrote:
>>
>> On Mon, Jun 23, 2014 at 12:57 PM, Carlos Rafael Giani
>> <dv@pseudoterminal.org> wrote:
>>>
>>> Hello,
>>>
>>> evbug is enabled by default with newer kernels. This is highly annoying.
>>> It
>>> prints a debug message for every single HID activity. Mouse movement, key
>>> presses etc.
>>> It can slow down the system.
>>>
>>> evbug is blacklisted in Ubuntu's modprobe config. I think it is wise to
>>> do
>>> the same in meta-fsl-arm . Blacklisting is probably more effective, since
>>> otherwise, the configurations of all kernels in meta-fsl-arm and
>>> meta-fsl-arm-extra have to be modified.
>>
>> I agree.
>>
>> Could you, please, make a patch to fix it?
>>
>> Daiane
>
> Well, how would it ideally be fixed? By blacklisting?

I think we can start by using it.

Or, wait more 1 or 2 days for more replies


Daiane

Re: blacklist evbug or remove it from the kernel config

[Eric Nelson]

Hi Carlos,

On 06/23/2014 08:57 AM, Carlos Rafael Giani wrote:
> Hello,
> 
> evbug is enabled by default with newer kernels. This is highly annoying.
> It prints a debug message for every single HID activity. Mouse movement,
> key presses etc.
> It can slow down the system.
> 
> evbug is blacklisted in Ubuntu's modprobe config. I think it is wise to
> do the same in meta-fsl-arm . Blacklisting is probably more effective,
> since otherwise, the configurations of all kernels in meta-fsl-arm and
> meta-fsl-arm-extra have to be modified.
> 
> cheers

Strange timing...

https://github.com/boundarydevices/linux-imx6/commit/f6b5aef511f490f79fc3622c1a51672d13cb664e

+1 if it can be black-listed.

Regards,


Eric

gpu-viv-bin-mx6q from 3.10.17 -> 3.5.7?

[Ra37740@freescale.comndy]

I want to update the 3.5.7 gpu-viv-bin-mx6q from 3.10.17...

I've started editing the layer.conf file and moving some .bb files 
around and etc. But this seems like too much effort to be correct.

Can someone at least point me in the right direction to do something 
like this?

Thanks,
Randy Krakora

Re: gpu-viv-bin-mx6q from 3.10.17 -> 3.5.7?

[Daiane.Angolini]

> 
> I want to update the 3.5.7 gpu-viv-bin-mx6q from 3.10.17...
> 
> I've started editing the layer.conf file and moving some .bb files around
> and etc. But this seems like too much effort to be correct.
> 
> Can someone at least point me in the right direction to do something like
> this?

The trick is not on recipe side.

The trick is to find the right patchset to upgrade the GPU driver in kernel

The recipes you solve with a simple diff.


Daiane

Re: gpu-viv-bin-mx6q from 3.10.17 -> 3.5.7?

[Otavio Salvador]

Randy,

On Mon, Jun 23, 2014 at 10:25 PM, Daiane.Angolini@freescale.com
<Daiane.Angolini@freescale.com> wrote:
>>
>> I want to update the 3.5.7 gpu-viv-bin-mx6q from 3.10.17...
>>
>> I've started editing the layer.conf file and moving some .bb files around
>> and etc. But this seems like too much effort to be correct.
>>
>> Can someone at least point me in the right direction to do something like
>> this?
>
> The trick is not on recipe side.
>
> The trick is to find the right patchset to upgrade the GPU driver in kernel
>
> The recipes you solve with a simple diff.

Check:

https://github.com/Freescale/meta-fsl-arm-extra/blob/master/recipes-kernel/linux/linux-boundary-3.0.35/ENGR00278350-gpu-viante-4.6.9p13-kernel-part-integra.patch

This should apply fine (I hope).

-- 
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

Re: gpu-viv-bin-mx6q from 3.10.17 -> 3.5.7?

[Eric Nelson]

Hi Otavio,

On 06/24/2014 02:06 PM, Otavio Salvador wrote:
> Randy,
> 
> On Mon, Jun 23, 2014 at 10:25 PM, Daiane.Angolini@freescale.com
> <Daiane.Angolini@freescale.com> wrote:
>>>
>>> I want to update the 3.5.7 gpu-viv-bin-mx6q from 3.10.17...
>>>
>>> I've started editing the layer.conf file and moving some .bb files around
>>> and etc. But this seems like too much effort to be correct.
>>>
>>> Can someone at least point me in the right direction to do something like
>>> this?
>>
>> The trick is not on recipe side.
>>
>> The trick is to find the right patchset to upgrade the GPU driver in kernel
>>
>> The recipes you solve with a simple diff.
> 
> Check:
> 
> https://github.com/Freescale/meta-fsl-arm-extra/blob/master/recipes-kernel/linux/linux-boundary-3.0.35/ENGR00278350-gpu-viante-4.6.9p13-kernel-part-integra.patch
> 
> This should apply fine (I hope).
> 

I think you missed something. Randy was asking about migrating
(down-grading) from 3.10.17 to 3.5.7...

This patch goes the other direction (3.0.35->3.5.7).

Regards,


Eric

Re: gpu-viv-bin-mx6q from 3.10.17 -> 3.5.7?

[Otavio Salvador]

On Tue, Jun 24, 2014 at 6:32 PM, Eric Nelson
<eric.nelson@boundarydevices.com> wrote:
> On 06/24/2014 02:06 PM, Otavio Salvador wrote:
>> On Mon, Jun 23, 2014 at 10:25 PM, Daiane.Angolini@freescale.com
>> <Daiane.Angolini@freescale.com> wrote:
>>>> I want to update the 3.5.7 gpu-viv-bin-mx6q from 3.10.17...
>>>>
>>>> I've started editing the layer.conf file and moving some .bb files around
>>>> and etc. But this seems like too much effort to be correct.
>>>>
>>>> Can someone at least point me in the right direction to do something like
>>>> this?
>>>
>>> The trick is not on recipe side.
>>>
>>> The trick is to find the right patchset to upgrade the GPU driver in kernel
>>>
>>> The recipes you solve with a simple diff.
>>
>> Check:
>>
>> https://github.com/Freescale/meta-fsl-arm-extra/blob/master/recipes-kernel/linux/linux-boundary-3.0.35/ENGR00278350-gpu-viante-4.6.9p13-kernel-part-integra.patch
>>
>> This should apply fine (I hope).
>>
>
> I think you missed something. Randy was asking about migrating
> (down-grading) from 3.10.17 to 3.5.7...
>
> This patch goes the other direction (3.0.35->3.5.7).

Humm maybe. Randy, could you clarify it?

-- 
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

Re: gpu-viv-bin-mx6q from 3.10.17 -> 3.5.7?

[randy.krakora]

Yes, unfortunately Eric is right. :)

I need to back port from 3.10.17 to 3.5.7, although I found out 3.0.35 has the patches that 3.10.17 does for this as well, so maybe starting from there would be better.

Regards,
Randy Krakora

> On Jun 25, 2014, at 10:42 AM, "Otavio Salvador" <otavio@ossystems.com.br> wrote:
> 
> On Tue, Jun 24, 2014 at 6:32 PM, Eric Nelson
> <eric.nelson@boundarydevices.com> wrote:
>> On 06/24/2014 02:06 PM, Otavio Salvador wrote:
>>> On Mon, Jun 23, 2014 at 10:25 PM, Daiane.Angolini@freescale.com
>>> <Daiane.Angolini@freescale.com> wrote:
>>>>> I want to update the 3.5.7 gpu-viv-bin-mx6q from 3.10.17...
>>>>> 
>>>>> I've started editing the layer.conf file and moving some .bb files around
>>>>> and etc. But this seems like too much effort to be correct.
>>>>> 
>>>>> Can someone at least point me in the right direction to do something like
>>>>> this?
>>>> 
>>>> The trick is not on recipe side.
>>>> 
>>>> The trick is to find the right patchset to upgrade the GPU driver in kernel
>>>> 
>>>> The recipes you solve with a simple diff.
>>> 
>>> Check:
>>> 
>>> https://github.com/Freescale/meta-fsl-arm-extra/blob/master/recipes-kernel/linux/linux-boundary-3.0.35/ENGR00278350-gpu-viante-4.6.9p13-kernel-part-integra.patch
>>> 
>>> This should apply fine (I hope).
>> 
>> I think you missed something. Randy was asking about migrating
>> (down-grading) from 3.10.17 to 3.5.7...
>> 
>> This patch goes the other direction (3.0.35->3.5.7).
> 
> Humm maybe. Randy, could you clarify it?
> 
> -- 
> 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
> -- 
> _______________________________________________
> meta-freescale mailing list
> meta-freescale@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-freescale

Re: gpu-viv-bin-mx6q from 3.10.17 -> 3.5.7?

[Otavio Salvador]

On Wed, Jun 25, 2014 at 11:44 AM, randy.krakora@freescale.com
<randy.krakora@freescale.com> wrote:
> Yes, unfortunately Eric is right. :)
>
> I need to back port from 3.10.17 to 3.5.7, although I found out 3.0.35 has the patches that 3.10.17 does for this as well, so maybe starting from there would be better.

Oh right. Sorry if I miss understood it :-)

Yes it is a better starting point.

-- 
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

Re: gpu-viv-bin-mx6q from 3.10.17 -> 3.5.7?

[Eric Nelson]

Hi Randy,

On 06/25/2014 07:44 AM, randy.krakora@freescale.com wrote:
> Yes, unfortunately Eric is right. :)
> 
> I need to back port from 3.10.17 to 3.5.7, although I found out
> 3.0.35 has the patches that 3.10.17 does for this as well, so maybe starting
> from there would be better.
> 

I suspect that pushing forward to 3.10.17 will be an easier move. Since
both are based on Device Tree, this should be relatively
straightforward.

Regards,


Eric