Hi,
On 01/30/2018 09:53 AM, Pavel Machek wrote:
> On Tue 2018-01-30 09:34:46, Ladislav Michl wrote:
>> On Tue, Jan 30, 2018 at 12:33:01AM +0100, Pavel Machek wrote:
>>> On Tue 2018-01-30 00:20:31, Ladislav Michl wrote:
On Tue, Jan 30, 2018 at 12:05:39AM +0100, Pavel Machek wrote:
>
>
Hi,
On 01/30/2018 09:53 AM, Pavel Machek wrote:
> On Tue 2018-01-30 09:34:46, Ladislav Michl wrote:
>> On Tue, Jan 30, 2018 at 12:33:01AM +0100, Pavel Machek wrote:
>>> On Tue 2018-01-30 00:20:31, Ladislav Michl wrote:
On Tue, Jan 30, 2018 at 12:05:39AM +0100, Pavel Machek wrote:
>
>
Hi,
On 01/03/2018 02:56 PM, Pavel Machek wrote:
> Hi!
>
> Sebasian, you submitted patch to enable vibrations on N950. I am
> trying to do the same now on N9... I guess I enabled the dts, but
> .. how do I actually ask for vibrations? /dev/input/eventX does not
> seem to be present.
>
> Did
Hi,
On 01/03/2018 02:56 PM, Pavel Machek wrote:
> Hi!
>
> Sebasian, you submitted patch to enable vibrations on N950. I am
> trying to do the same now on N9... I guess I enabled the dts, but
> .. how do I actually ask for vibrations? /dev/input/eventX does not
> seem to be present.
>
> Did
Hi,
On 01/02/2018 06:27 PM, Sebastian Reichel wrote:
> Hi,
>
> On Tue, Jan 02, 2018 at 02:17:22PM +0100, Pavel Machek wrote:
>> This adds dts support for magnetometer and touchscreen on Nokia N9.
>
> I think it makes sense to have this splitted.
>
>> Signed-off-by: Pavel Machek
Hi,
On 01/02/2018 06:27 PM, Sebastian Reichel wrote:
> Hi,
>
> On Tue, Jan 02, 2018 at 02:17:22PM +0100, Pavel Machek wrote:
>> This adds dts support for magnetometer and touchscreen on Nokia N9.
>
> I think it makes sense to have this splitted.
>
>> Signed-off-by: Pavel Machek
>>
>> diff
Hi Sakari,
and thank you for your input - I've added a few comments below.
On 12/27/2017 07:00 PM, Sakari Ailus wrote:
> Hi Pavel,
>
> Thanks for the patch. Please see my comments below.
>
> On Wed, Dec 27, 2017 at 10:18:28AM +0100, Pavel Machek wrote:
>> From: Filip Matij
Hi Sakari,
and thank you for your input - I've added a few comments below.
On 12/27/2017 07:00 PM, Sakari Ailus wrote:
> Hi Pavel,
>
> Thanks for the patch. Please see my comments below.
>
> On Wed, Dec 27, 2017 at 10:18:28AM +0100, Pavel Machek wrote:
>>
> If someone knows how to fix the backlight, it would still be useful.
In panel-dsi-cm.c it's set to maximum with
dsicm_dcs_write_1(ddata, DCS_BRIGHTNESS, 0xff);
Sebastian suggested the same but used 100 instead of 0xff, which might
be a bit too low. You can also add msleep(1000) after
> If someone knows how to fix the backlight, it would still be useful.
In panel-dsi-cm.c it's set to maximum with
dsicm_dcs_write_1(ddata, DCS_BRIGHTNESS, 0xff);
Sebastian suggested the same but used 100 instead of 0xff, which might
be a bit too low. You can also add msleep(1000) after
On 10/26/2017 09:16 AM, Pavel Machek wrote:
> "Uart pins not muxed in NOLO" would certainly explain my problems. In
> 3.5.X, output works even in decompressor ("Uncompressing
> kernel... done, booting linux").
IIRC bootloader passes some additional settings for gpio that kernel
should apply (2.6
On 10/26/2017 09:16 AM, Pavel Machek wrote:
> "Uart pins not muxed in NOLO" would certainly explain my problems. In
> 3.5.X, output works even in decompressor ("Uncompressing
> kernel... done, booting linux").
IIRC bootloader passes some additional settings for gpio that kernel
should apply (2.6
Hi Pavel,
On 10/25/2017 10:34 PM, Pavel Machek wrote:
> 3.5.3-nemo kernel seems to work
I did take a quick look at the board-rm680.c since there are some
conditional statements with regards to system revision but I didn't
notice anything that might prevent it from booting.
> If you have
> any
Hi Pavel,
On 10/25/2017 10:34 PM, Pavel Machek wrote:
> 3.5.3-nemo kernel seems to work
I did take a quick look at the board-rm680.c since there are some
conditional statements with regards to system revision but I didn't
notice anything that might prevent it from booting.
> If you have
> any
14 matches
Mail list logo