On Tue, 03 Jan 2023, Alexey Lukyachuk wrote:
> On Tue, 03 Jan 2023 12:14:02 +0200
> Jani Nikula wrote:
>
>> On Mon, 02 Jan 2023, Alexey Lukyachuk wrote:
>> > Regarding to your question about fdo gitlab, I went to do it.
>>
>> What's the URL for the issue?
>>
>> BR,
>> Jani.
>>
>
> I have not
On Tue, Jan 03, 2023 at 07:09:20PM +0300, Alexey Lukyachuk wrote:
> On Tue, 3 Jan 2023 07:46:40 -0500
> Rodrigo Vivi wrote:
>
> > On Mon, Jan 02, 2023 at 04:56:49PM +0300, Alexey Lukyachuk wrote:
> > > On Tue, 27 Dec 2022 20:40:03 +0300
> > > Alexey Lukyachuk wrote:
> > >
> > > > On Tue, 27 Dec
On Tue, 3 Jan 2023 07:46:40 -0500
Rodrigo Vivi wrote:
> On Mon, Jan 02, 2023 at 04:56:49PM +0300, Alexey Lukyachuk wrote:
> > On Tue, 27 Dec 2022 20:40:03 +0300
> > Alexey Lukyachuk wrote:
> >
> > > On Tue, 27 Dec 2022 11:39:25 -0500
> > > Rodrigo Vivi wrote:
> > >
> > > > On Sun, Dec 25, 202
On Tue, 03 Jan 2023, Rodrigo Vivi wrote:
> On Mon, Jan 02, 2023 at 04:56:49PM +0300, Alexey Lukyachuk wrote:
>> On Tue, 27 Dec 2022 20:40:03 +0300
>> Alexey Lukyachuk wrote:
>>
>> > On Tue, 27 Dec 2022 11:39:25 -0500
>> > Rodrigo Vivi wrote:
>> >
>> > > On Sun, Dec 25, 2022 at 09:55:08PM +0300
On Mon, Jan 02, 2023 at 04:56:49PM +0300, Alexey Lukyachuk wrote:
> On Tue, 27 Dec 2022 20:40:03 +0300
> Alexey Lukyachuk wrote:
>
> > On Tue, 27 Dec 2022 11:39:25 -0500
> > Rodrigo Vivi wrote:
> >
> > > On Sun, Dec 25, 2022 at 09:55:08PM +0300, Alexey Lukyanchuk wrote:
> > > > dell wyse 3040 d
On Tue, 03 Jan 2023 12:14:02 +0200
Jani Nikula wrote:
> On Mon, 02 Jan 2023, Alexey Lukyachuk wrote:
> > Regarding to your question about fdo gitlab, I went to do it.
>
> What's the URL for the issue?
>
> BR,
> Jani.
>
I have not submited issue in bug tracker because I found solution in git.
On Mon, 02 Jan 2023, Alexey Lukyachuk wrote:
> Regarding to your question about fdo gitlab, I went to do it.
What's the URL for the issue?
BR,
Jani.
--
Jani Nikula, Intel Open Source Graphics Center
On Tue, 27 Dec 2022 20:40:03 +0300
Alexey Lukyachuk wrote:
> On Tue, 27 Dec 2022 11:39:25 -0500
> Rodrigo Vivi wrote:
>
> > On Sun, Dec 25, 2022 at 09:55:08PM +0300, Alexey Lukyanchuk wrote:
> > > dell wyse 3040 doesn't peform poweroff properly, but instead remains in
> > > turned power on sta
On Tue, 27 Dec 2022, Alexey Lukyachuk wrote:
> On Tue, 27 Dec 2022 11:39:25 -0500
> Rodrigo Vivi wrote:
>
>> On Sun, Dec 25, 2022 at 09:55:08PM +0300, Alexey Lukyanchuk wrote:
>> > dell wyse 3040 doesn't peform poweroff properly, but instead remains in
>> > turned power on state.
>>
>> okay, th
On Tue, 27 Dec 2022 11:39:25 -0500
Rodrigo Vivi wrote:
> On Sun, Dec 25, 2022 at 09:55:08PM +0300, Alexey Lukyanchuk wrote:
> > dell wyse 3040 doesn't peform poweroff properly, but instead remains in
> > turned power on state.
>
> okay, the motivation is explained in the commit msg..
>
> > Add
On Sun, Dec 25, 2022 at 09:55:08PM +0300, Alexey Lukyanchuk wrote:
> dell wyse 3040 doesn't peform poweroff properly, but instead remains in
> turned power on state.
okay, the motivation is explained in the commit msg..
> Additional mutex_lock and
> intel_crtc_wait_for_next_vblank
> feature 6.
dell wyse 3040 doesn't peform poweroff properly, but instead remains in
turned power on state. Additional mutex_lock and
intel_crtc_wait_for_next_vblank
feature 6.2 kernel resolve this trouble.
cc: sta...@vger.kernel.org
original commit Link: https://patchwork.freedesktop.org/patch/508926/
fixe
12 matches
Mail list logo