> On 6 Nov 2018, at 21:31, Takashi Iwai wrote:
>
> On Tue, 06 Nov 2018 22:05:11 +0100,
> Mike Brady wrote:
>>
>>
>>> On 5 Nov 2018, at 16:11, Takashi Iwai wrote:
>>>
>>> On Mon, 05 Nov 2018 16:57:07 +0100,
>>> Mike Brady wrote:
> One another thing I'd like to point out is that
> On 6 Nov 2018, at 21:31, Takashi Iwai wrote:
>
> On Tue, 06 Nov 2018 22:05:11 +0100,
> Mike Brady wrote:
>>
>>
>>> On 5 Nov 2018, at 16:11, Takashi Iwai wrote:
>>>
>>> On Mon, 05 Nov 2018 16:57:07 +0100,
>>> Mike Brady wrote:
> One another thing I'd like to point out is that
On Tue, 06 Nov 2018 22:05:11 +0100,
Mike Brady wrote:
>
>
> > On 5 Nov 2018, at 16:11, Takashi Iwai wrote:
> >
> > On Mon, 05 Nov 2018 16:57:07 +0100,
> > Mike Brady wrote:
> >>
> >>> One another thing I'd like to point out is that the value given in the
> >>> patch is nothing but an
On Tue, 06 Nov 2018 22:05:11 +0100,
Mike Brady wrote:
>
>
> > On 5 Nov 2018, at 16:11, Takashi Iwai wrote:
> >
> > On Mon, 05 Nov 2018 16:57:07 +0100,
> > Mike Brady wrote:
> >>
> >>> One another thing I'd like to point out is that the value given in the
> >>> patch is nothing but an
> On 5 Nov 2018, at 16:11, Takashi Iwai wrote:
>
> On Mon, 05 Nov 2018 16:57:07 +0100,
> Mike Brady wrote:
>>
>>> One another thing I'd like to point out is that the value given in the
>>> patch is nothing but an estimated position, optimistically calculated
>>> via the system timer. Mike
> On 5 Nov 2018, at 16:11, Takashi Iwai wrote:
>
> On Mon, 05 Nov 2018 16:57:07 +0100,
> Mike Brady wrote:
>>
>>> One another thing I'd like to point out is that the value given in the
>>> patch is nothing but an estimated position, optimistically calculated
>>> via the system timer. Mike
On Mon, 05 Nov 2018 16:57:07 +0100,
Mike Brady wrote:
>
> > One another thing I'd like to point out is that the value given in the
> > patch is nothing but an estimated position, optimistically calculated
> > via the system timer. Mike and I had already discussion in another
> > thread, and
On Mon, 05 Nov 2018 16:57:07 +0100,
Mike Brady wrote:
>
> > One another thing I'd like to point out is that the value given in the
> > patch is nothing but an estimated position, optimistically calculated
> > via the system timer. Mike and I had already discussion in another
> > thread, and
> On 25 Oct 2018, at 08:37, Takashi Iwai wrote:
>
> On Thu, 25 Oct 2018 00:02:34 +0200,
> Kirill Marinushkin wrote:
>>
When you play sound - the pointer increments.
>>>
>>> Unfortunately, when you play sound, the pointer does not actually
>>> increment, for up to about 10
> On 25 Oct 2018, at 08:37, Takashi Iwai wrote:
>
> On Thu, 25 Oct 2018 00:02:34 +0200,
> Kirill Marinushkin wrote:
>>
When you play sound - the pointer increments.
>>>
>>> Unfortunately, when you play sound, the pointer does not actually
>>> increment, for up to about 10
Hi Kirill. Thanks for the post.
Mike
> On 25 Oct 2018, at 18:20, Kirill Marinushkin wrote:
>
> Hello Takashi, Mike,
>
> @Takashi
>
> On 10/25/18 09:37, Takashi Iwai wrote:
>> Well, in the API POV, it's nothing wrong to keep hwptr sticking while
>> updating only delay value. It implies that
Hi Kirill. Thanks for the post.
Mike
> On 25 Oct 2018, at 18:20, Kirill Marinushkin wrote:
>
> Hello Takashi, Mike,
>
> @Takashi
>
> On 10/25/18 09:37, Takashi Iwai wrote:
>> Well, in the API POV, it's nothing wrong to keep hwptr sticking while
>> updating only delay value. It implies that
Hello Takashi, Mike,
@Takashi
On 10/25/18 09:37, Takashi Iwai wrote:
> Well, in the API POV, it's nothing wrong to keep hwptr sticking while
> updating only delay value. It implies that the hardware chip doesn't
> provide the hwptr update.
Thank you for the clarification. Modifying
Hello Takashi, Mike,
@Takashi
On 10/25/18 09:37, Takashi Iwai wrote:
> Well, in the API POV, it's nothing wrong to keep hwptr sticking while
> updating only delay value. It implies that the hardware chip doesn't
> provide the hwptr update.
Thank you for the clarification. Modifying
On Thu, 25 Oct 2018 00:02:34 +0200,
Kirill Marinushkin wrote:
>
> >> When you play sound - the pointer increments.
> >
> > Unfortunately, when you play sound, the pointer does not actually
> > increment, for up to about 10 milliseconds. I know of no way to actually
> > access the true “live”
On Thu, 25 Oct 2018 00:02:34 +0200,
Kirill Marinushkin wrote:
>
> >> When you play sound - the pointer increments.
> >
> > Unfortunately, when you play sound, the pointer does not actually
> > increment, for up to about 10 milliseconds. I know of no way to actually
> > access the true “live”
Hello Mike,
We are not on the same page. What you hear is not what I tell you.
Either you don't understand what happens in your commit, or I don't understand
what happens in the driver.
Hopefully somebody in the community can comment here.
On 10/24/18 21:54, Mike Brady wrote:
You modify
Hello Mike,
We are not on the same page. What you hear is not what I tell you.
Either you don't understand what happens in your commit, or I don't understand
what happens in the driver.
Hopefully somebody in the community can comment here.
On 10/24/18 21:54, Mike Brady wrote:
You modify
Hi Kirill. Thanks again for your comments.
> On 24 Oct 2018, at 19:06, Kirill Marinushkin wrote:
>
> Hello Mike,
>
> On 10/24/18 10:20, Mike Brady wrote:
>> Hi Kirill. Thanks for your comments.
>>
>>> On 22 Oct 2018, at 23:25, Kirill Marinushkin
>>> wrote:
>>>
>>> AFAIU, this patch is
Hi Kirill. Thanks again for your comments.
> On 24 Oct 2018, at 19:06, Kirill Marinushkin wrote:
>
> Hello Mike,
>
> On 10/24/18 10:20, Mike Brady wrote:
>> Hi Kirill. Thanks for your comments.
>>
>>> On 22 Oct 2018, at 23:25, Kirill Marinushkin
>>> wrote:
>>>
>>> AFAIU, this patch is
Hello Mike,
On 10/24/18 10:20, Mike Brady wrote:
> Hi Kirill. Thanks for your comments.
>
>> On 22 Oct 2018, at 23:25, Kirill Marinushkin wrote:
>>
>> AFAIU, this patch is wrong. Please correct me, maybe I misunderstand
>> something.
>>
>>> The problem that this patch seeks to resolve is that
Hello Mike,
On 10/24/18 10:20, Mike Brady wrote:
> Hi Kirill. Thanks for your comments.
>
>> On 22 Oct 2018, at 23:25, Kirill Marinushkin wrote:
>>
>> AFAIU, this patch is wrong. Please correct me, maybe I misunderstand
>> something.
>>
>>> The problem that this patch seeks to resolve is that
Hi Kirill. Thanks for your comments.
> On 22 Oct 2018, at 23:25, Kirill Marinushkin wrote:
>
> AFAIU, this patch is wrong. Please correct me, maybe I misunderstand
> something.
>
>> The problem that this patch seeks to resolve is that when userland asks for
>> the delay
>
> The userspace
Hi Kirill. Thanks for your comments.
> On 22 Oct 2018, at 23:25, Kirill Marinushkin wrote:
>
> AFAIU, this patch is wrong. Please correct me, maybe I misunderstand
> something.
>
>> The problem that this patch seeks to resolve is that when userland asks for
>> the delay
>
> The userspace
24 matches
Mail list logo
