On Tue 2018-05-29 23:09:09, Sebastian Reichel wrote:
> Hi Pavel,
>
> On Tue, May 29, 2018 at 10:45:17PM +0200, Pavel Machek wrote:
> > > > > still results in working touchscreen, removing any of the three fields
> > > > > breaks it again.
> > > >
> > > > I bisected one regression down, see
On Tue 2018-05-29 23:09:09, Sebastian Reichel wrote:
> Hi Pavel,
>
> On Tue, May 29, 2018 at 10:45:17PM +0200, Pavel Machek wrote:
> > > > > still results in working touchscreen, removing any of the three fields
> > > > > breaks it again.
> > > >
> > > > I bisected one regression down, see
Hi Pavel,
On Tue, May 29, 2018 at 10:45:17PM +0200, Pavel Machek wrote:
> > > > still results in working touchscreen, removing any of the three fields
> > > > breaks it again.
> > >
> > > I bisected one regression down, see "omapdrm regression in v4.17-rc
> > > series"
> > > not sure if it
Hi Pavel,
On Tue, May 29, 2018 at 10:45:17PM +0200, Pavel Machek wrote:
> > > > still results in working touchscreen, removing any of the three fields
> > > > breaks it again.
> > >
> > > I bisected one regression down, see "omapdrm regression in v4.17-rc
> > > series"
> > > not sure if it
Hi!
> > > still results in working touchscreen, removing any of the three fields
> > > breaks it again.
> >
> > I bisected one regression down, see "omapdrm regression in v4.17-rc series"
> > not sure if it covers all the issues being discussed here though.
>
> Reverting 24aac6011f70 fixes
Hi!
> > > still results in working touchscreen, removing any of the three fields
> > > breaks it again.
> >
> > I bisected one regression down, see "omapdrm regression in v4.17-rc series"
> > not sure if it covers all the issues being discussed here though.
>
> Reverting 24aac6011f70 fixes
Hi!
> > > So... I did some experiments on v4.16.
> > >
> > > Swapping tsc2005@0 and lcd: acx565akm@2 entries in the dts does break
> > > stuff.
> > >
> > > I thought it might be due to vio regulator, but it does not appear
> > > so... screen still works with tsc2005 driver disabled in .config.
Hi!
> > > So... I did some experiments on v4.16.
> > >
> > > Swapping tsc2005@0 and lcd: acx565akm@2 entries in the dts does break
> > > stuff.
> > >
> > > I thought it might be due to vio regulator, but it does not appear
> > > so... screen still works with tsc2005 driver disabled in .config.
On Wed 2018-05-23 15:04:56, Tony Lindgren wrote:
> * Pavel Machek [180523 20:14]:
> > On Wed 2018-05-23 16:06:15, Pavel Machek wrote:
> > > On Wed 2018-05-23 00:56:38, Aaro Koskinen wrote:
> > > > Hi,
> > > >
> > > > On Tue, May 22, 2018 at 10:58:26PM +0200, Pavel Machek wrote:
> >
On Wed 2018-05-23 15:04:56, Tony Lindgren wrote:
> * Pavel Machek [180523 20:14]:
> > On Wed 2018-05-23 16:06:15, Pavel Machek wrote:
> > > On Wed 2018-05-23 00:56:38, Aaro Koskinen wrote:
> > > > Hi,
> > > >
> > > > On Tue, May 22, 2018 at 10:58:26PM +0200, Pavel Machek wrote:
> > > > > On Tue
On 24/05/18 01:02, Aaro Koskinen wrote:
But turns out that omapdrm tree is unbisectable, as I get build failures such
as (commit 28d79f3e56b2c1d5ff0fd363da3229be0962cc85):
/home/aaro/git/devel/linux/drivers/gpu/drm/omapdrm/dss/dss.c:1473:52: error:
undefined identifier 'dss_debug_dump_clocks'
On 24/05/18 01:02, Aaro Koskinen wrote:
But turns out that omapdrm tree is unbisectable, as I get build failures such
as (commit 28d79f3e56b2c1d5ff0fd363da3229be0962cc85):
/home/aaro/git/devel/linux/drivers/gpu/drm/omapdrm/dss/dss.c:1473:52: error:
undefined identifier 'dss_debug_dump_clocks'
* Pavel Machek [180523 20:14]:
> On Wed 2018-05-23 16:06:15, Pavel Machek wrote:
> > On Wed 2018-05-23 00:56:38, Aaro Koskinen wrote:
> > > Hi,
> > >
> > > On Tue, May 22, 2018 at 10:58:26PM +0200, Pavel Machek wrote:
> > > > On Tue 2018-05-22 22:41:39, Aaro Koskinen wrote:
> > > >
* Pavel Machek [180523 20:14]:
> On Wed 2018-05-23 16:06:15, Pavel Machek wrote:
> > On Wed 2018-05-23 00:56:38, Aaro Koskinen wrote:
> > > Hi,
> > >
> > > On Tue, May 22, 2018 at 10:58:26PM +0200, Pavel Machek wrote:
> > > > On Tue 2018-05-22 22:41:39, Aaro Koskinen wrote:
> > > > > My device
On Wed, May 23, 2018 at 12:56:38AM +0300, Aaro Koskinen wrote:
> On Tue, May 22, 2018 at 10:58:26PM +0200, Pavel Machek wrote:
> > On Tue 2018-05-22 22:41:39, Aaro Koskinen wrote:
> > > My device worked with v4.17-rc1 (haven't found time to test newer
> > > kernels),
> > > but if you say the
On Wed, May 23, 2018 at 12:56:38AM +0300, Aaro Koskinen wrote:
> On Tue, May 22, 2018 at 10:58:26PM +0200, Pavel Machek wrote:
> > On Tue 2018-05-22 22:41:39, Aaro Koskinen wrote:
> > > My device worked with v4.17-rc1 (haven't found time to test newer
> > > kernels),
> > > but if you say the
On Wed 2018-05-23 16:06:15, Pavel Machek wrote:
> On Wed 2018-05-23 00:56:38, Aaro Koskinen wrote:
> > Hi,
> >
> > On Tue, May 22, 2018 at 10:58:26PM +0200, Pavel Machek wrote:
> > > On Tue 2018-05-22 22:41:39, Aaro Koskinen wrote:
> > > > My device worked with v4.17-rc1 (haven't found time to
On Wed 2018-05-23 16:06:15, Pavel Machek wrote:
> On Wed 2018-05-23 00:56:38, Aaro Koskinen wrote:
> > Hi,
> >
> > On Tue, May 22, 2018 at 10:58:26PM +0200, Pavel Machek wrote:
> > > On Tue 2018-05-22 22:41:39, Aaro Koskinen wrote:
> > > > My device worked with v4.17-rc1 (haven't found time to
On Wed 2018-05-23 00:56:38, Aaro Koskinen wrote:
> Hi,
>
> On Tue, May 22, 2018 at 10:58:26PM +0200, Pavel Machek wrote:
> > On Tue 2018-05-22 22:41:39, Aaro Koskinen wrote:
> > > My device worked with v4.17-rc1 (haven't found time to test newer
> > > kernels),
> > > but if you say the probe
On Wed 2018-05-23 00:56:38, Aaro Koskinen wrote:
> Hi,
>
> On Tue, May 22, 2018 at 10:58:26PM +0200, Pavel Machek wrote:
> > On Tue 2018-05-22 22:41:39, Aaro Koskinen wrote:
> > > My device worked with v4.17-rc1 (haven't found time to test newer
> > > kernels),
> > > but if you say the probe
Hi,
On Tue, May 22, 2018 at 10:58:26PM +0200, Pavel Machek wrote:
> On Tue 2018-05-22 22:41:39, Aaro Koskinen wrote:
> > My device worked with v4.17-rc1 (haven't found time to test newer kernels),
> > but if you say the probe order is random then we must find some proper way
> > to express the
Hi,
On Tue, May 22, 2018 at 10:58:26PM +0200, Pavel Machek wrote:
> On Tue 2018-05-22 22:41:39, Aaro Koskinen wrote:
> > My device worked with v4.17-rc1 (haven't found time to test newer kernels),
> > but if you say the probe order is random then we must find some proper way
> > to express the
On Tue 2018-05-22 22:41:39, Aaro Koskinen wrote:
> Hi,
>
> On Tue, May 22, 2018 at 10:02:50AM +0200, Pali Rohár wrote:
> > Hi! I remember that in time of migration from platform board code to
> > device tree structures there appeared some bug which caused that
> > sometimes display were not
On Tue 2018-05-22 22:41:39, Aaro Koskinen wrote:
> Hi,
>
> On Tue, May 22, 2018 at 10:02:50AM +0200, Pali Rohár wrote:
> > Hi! I remember that in time of migration from platform board code to
> > device tree structures there appeared some bug which caused that
> > sometimes display were not
Hi,
On Tue, May 22, 2018 at 10:02:50AM +0200, Pali Rohár wrote:
> Hi! I remember that in time of migration from platform board code to
> device tree structures there appeared some bug which caused that
> sometimes display were not initialized. And somebody figured out that
> display
Hi,
On Tue, May 22, 2018 at 10:02:50AM +0200, Pali Rohár wrote:
> Hi! I remember that in time of migration from platform board code to
> device tree structures there appeared some bug which caused that
> sometimes display were not initialized. And somebody figured out that
> display
On Monday 21 May 2018 23:39:53 Pavel Machek wrote:
> HI!
>
> > On Sun, Apr 22, 2018 at 09:42:13AM +0200, Pavel Machek wrote:
> > > v4.17-rc1 broke display for me on Nokia N900. (I don't know if system
> > > boots, but I can see on red flash LED that at least that driver
> > > succeeded. So it
On Monday 21 May 2018 23:39:53 Pavel Machek wrote:
> HI!
>
> > On Sun, Apr 22, 2018 at 09:42:13AM +0200, Pavel Machek wrote:
> > > v4.17-rc1 broke display for me on Nokia N900. (I don't know if system
> > > boots, but I can see on red flash LED that at least that driver
> > > succeeded. So it
HI!
> On Sun, Apr 22, 2018 at 09:42:13AM +0200, Pavel Machek wrote:
> > v4.17-rc1 broke display for me on Nokia N900. (I don't know if system
> > boots, but I can see on red flash LED that at least that driver
> > succeeded. So it should not be early boot crash).
> >
> > v4.17-rc1 also broke
HI!
> On Sun, Apr 22, 2018 at 09:42:13AM +0200, Pavel Machek wrote:
> > v4.17-rc1 broke display for me on Nokia N900. (I don't know if system
> > boots, but I can see on red flash LED that at least that driver
> > succeeded. So it should not be early boot crash).
> >
> > v4.17-rc1 also broke
Hi,
On Sun, Apr 22, 2018 at 09:42:13AM +0200, Pavel Machek wrote:
> v4.17-rc1 broke display for me on Nokia N900. (I don't know if system
> boots, but I can see on red flash LED that at least that driver
> succeeded. So it should not be early boot crash).
>
> v4.17-rc1 also broke boot on N950.
>
Hi,
On Sun, Apr 22, 2018 at 09:42:13AM +0200, Pavel Machek wrote:
> v4.17-rc1 broke display for me on Nokia N900. (I don't know if system
> boots, but I can see on red flash LED that at least that driver
> succeeded. So it should not be early boot crash).
>
> v4.17-rc1 also broke boot on N950.
>
Hi!
v4.17-rc1 broke display for me on Nokia N900. (I don't know if system
boots, but I can see on red flash LED that at least that driver
succeeded. So it should not be early boot crash).
v4.17-rc1 also broke boot on N950.
Any ideas? Does it work for you?
Hi!
v4.17-rc1 broke display for me on Nokia N900. (I don't know if system
boots, but I can see on red flash LED that at least that driver
succeeded. So it should not be early boot crash).
v4.17-rc1 also broke boot on N950.
Any ideas? Does it work for you?
34 matches
Mail list logo