Hi,
Dne četrtek, 08. marec 2018 ob 15:15:39 CET je @lex napisal(a):
> These are my
> changes: https://gist.github.com/avafinger/40e7751f5d8e8fbe0225e3ad4c5da0bf
>
> On Thursday, March 8, 2018 at 10:57:13 AM UTC-3, @lex wrote:
> > Ok, will test Ondřej and your branch. This can take some time, I
These are my
changes: https://gist.github.com/avafinger/40e7751f5d8e8fbe0225e3ad4c5da0bf
On Thursday, March 8, 2018 at 10:57:13 AM UTC-3, @lex wrote:
>
> Ok, will test Ondřej and your branch. This can take some time, I think
> this weekend I can build and test both.
>
> But this raised some
Ok, will test Ondřej and your branch. This can take some time, I think
this weekend I can build and test both.
But this raised some questions:
a) How is this going to help you guys fix the stable 4.15.y ?
b) I applied the significant changes on DRM and sun4i (that i think would
fix) on my 4.15
Hi,
Dne sreda, 07. marec 2018 ob 23:48:30 CET je 'Ondřej Jirman' via linux-sunxi
napisal(a):
> Hi,
>
> On Wed, Mar 07, 2018 at 02:17:42PM -0800, @lex wrote:
> > Hi Jernej,
> >
> > Unfortunately, this patch did not fix the issue, unless I did something
> > silly
Actually it did, just another
Hi,
On Wed, Mar 07, 2018 at 02:17:42PM -0800, @lex wrote:
> Hi Jernej,
>
> Unfortunately, this patch did not fix the issue, unless I did something
> silly.
> Here is the complete
> bootlog: https://gist.github.com/avafinger/ac6b5e73da87797c6ff32d6746e5fac5
>
> *code excerpt:*
>
> static void
Just for the record, bootlog without the patch looks better:
https://gist.github.com/avafinger/840c3e7743ead085f3c1f16bf10eaadc
On Wednesday, March 7, 2018 at 7:17:42 PM UTC-3, @lex wrote:
>
> Hi Jernej,
>
> Unfortunately, this patch did not fix the issue, unless I did something
> silly.
> Here
Hi Jernej,
Unfortunately, this patch did not fix the issue, unless I did something
silly.
Here is the complete
bootlog: https://gist.github.com/avafinger/ac6b5e73da87797c6ff32d6746e5fac5
*code excerpt:*
static void sun4i_crtc_atomic_disable(struct drm_crtc *crtc,
struct drm_crtc_state
Hi Jernej,
Yes, I missed the warning and the code was without that patch, I think this
will fix another issue I have when the monitor is still blank for the first
login message.
I will apply the fix and check again.
Thank you.
BR,
@lex
On Wednesday, March 7, 2018 at 5:39:10 PM UTC-3,
Hi,
Dne sreda, 07. marec 2018 ob 21:30:42 CET je @lex napisal(a):
> ops, i mean turning ON.
>
> On Wednesday, March 7, 2018 at 5:26:59 PM UTC-3, @lex wrote:
> > Hi,
> >
> > Turning HDMI monitor during boot or after complete boot kernel shows the
> > following error:
> >
> > [ 14.842605] []
ops, i mean turning ON.
On Wednesday, March 7, 2018 at 5:26:59 PM UTC-3, @lex wrote:
>
> Hi,
>
> Turning HDMI monitor during boot or after complete boot kernel shows the
> following error:
>
> [ 14.842605] [] (unwind_backtrace) from []
> (show_stack+0x10/0x14)
> [ 14.842698] [] (show_stack)
10 matches
Mail list logo
