Comment 311 for bug 1958019

Revision history for this message
In , mysubstmp (mysubstmp-linux-kernel-bugs) wrote :

(In reply to sycxyc from comment #295)
> (In reply to Cameron Berkenpas from comment #292)
> > Created attachment 297615 [details]
> > verbs-14itl5_14cITL.txt
> >
> > These verbs work for the 14itl5 and most likely the 14cITL as well.
> >
> > Thank you sycxyc for finding all of the compatible verb sequences! How did
> > you do this?! Especially so quickly?
> >
>
> I found that enabling auto-mute mode from alsamixer and then disabling it
> makes the speaker inactive. Using the debug mode of applyverbs.py, I can
> quickly determine the 5 line sequence that activates the left speaker
> without restarting or suspending.
>
> verbs-working.txt has two similar sections. The sequence used to activate
> the left speaker is at the end of the first part. It can be assumed that the
> later part controls the right speaker. After executing the later part, the
> first two lines must be executed to activate the left speaker, and it can be
> determined that the first two lines are used to switch speakers. I tried to
> modify the right speaker section and successfully activated it.
>
> The sequence of 5 lines to activate the speaker is repeated 2 times in
> succession and they are probably safe for the separation point.
>
> I modified applyverbs.py so that it skips comments and empty lines, which
> makes it easier to test and mark up.

Very good work!
That does not look so trivial though. The verbs-working.txt has more than 500 lines and finding those 5 lines looks not so easy. The debug mode makes it easier to find when to stop but not when the sequence starts.
Y