public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
* [gentoo-user] surface ntrig touchscreen
@ 2016-06-05  1:01 Bill Kenworthy
  2016-06-05 20:12 ` [gentoo-user] " James
  2016-06-05 20:22 ` [gentoo-user] " R0b0t1
  0 siblings, 2 replies; 6+ messages in thread
From: Bill Kenworthy @ 2016-06-05  1:01 UTC (permalink / raw
  To: gentoo-user

Has anyone been able to get the surface pro ntrig touchscreen to work
... and if so how?

MS recently changed from the wacom to a ntrig touchscreen (they
apparently bought the company!) for the latest pro models.  The kernel
guys have a surface3_spi module being worked on which I have patched
into 4.6.1 ... but neither dmesg or lspci still shows a ntrig device.

BillK


^ permalink raw reply	[flat|nested] 6+ messages in thread

* [gentoo-user] Re: surface ntrig touchscreen
  2016-06-05  1:01 [gentoo-user] surface ntrig touchscreen Bill Kenworthy
@ 2016-06-05 20:12 ` James
  2016-06-06  1:18   ` Bill Kenworthy
  2016-06-05 20:22 ` [gentoo-user] " R0b0t1
  1 sibling, 1 reply; 6+ messages in thread
From: James @ 2016-06-05 20:12 UTC (permalink / raw
  To: gentoo-user

Bill Kenworthy <billk <at> iinet.net.au> writes:


> Has anyone been able to get the surface pro ntrig touchscreen to work
> ... and if so how?

Sorry, never tried...

> MS recently changed from the wacom to a ntrig touchscreen (they
> apparently bought the company!) for the latest pro models.  The kernel
> guys have a surface3_spi module being worked on which I have patched
> into 4.6.1 ... but neither dmesg or lspci still shows a ntrig device.

'lshw' or other hardware scanning tools might show something.


Also install sys-apps/hwids  to the latest version and see if that
hardware shows up.

hth,
James







^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-user] surface ntrig touchscreen
  2016-06-05  1:01 [gentoo-user] surface ntrig touchscreen Bill Kenworthy
  2016-06-05 20:12 ` [gentoo-user] " James
@ 2016-06-05 20:22 ` R0b0t1
  1 sibling, 0 replies; 6+ messages in thread
From: R0b0t1 @ 2016-06-05 20:22 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 753 bytes --]

On Jun 4, 2016 8:04 PM, "Bill Kenworthy" <billk@iinet.net.au> wrote:
>
> Has anyone been able to get the surface pro ntrig touchscreen to work
> ... and if so how?
>
> MS recently changed from the wacom to a ntrig touchscreen (they
> apparently bought the company!) for the latest pro models.  The kernel
> guys have a surface3_spi module being worked on which I have patched
> into 4.6.1 ... but neither dmesg or lspci still shows a ntrig device.
>
> BillK
>

Depends what you expect to use it for. Linux software is playing catch up.

I would pass the hardware to a Windows VM and use the software that can
take advantage of it.

This is a great place for FOSS development if anyone has the resources.
Currently I am unable to afford a Surface.

Sid.

[-- Attachment #2: Type: text/html, Size: 996 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-user] Re: surface ntrig touchscreen
  2016-06-05 20:12 ` [gentoo-user] " James
@ 2016-06-06  1:18   ` Bill Kenworthy
  2016-06-06  1:43     ` James
  2016-06-06  1:45     ` R0b0t1
  0 siblings, 2 replies; 6+ messages in thread
From: Bill Kenworthy @ 2016-06-06  1:18 UTC (permalink / raw
  To: gentoo-user

On 06/06/16 04:12, James wrote:
> Bill Kenworthy <billk <at> iinet.net.au> writes:
> 
> 
>> Has anyone been able to get the surface pro ntrig touchscreen to work
>> ... and if so how?
> 
> Sorry, never tried...
> 
>> MS recently changed from the wacom to a ntrig touchscreen (they
>> apparently bought the company!) for the latest pro models.  The kernel
>> guys have a surface3_spi module being worked on which I have patched
>> into 4.6.1 ... but neither dmesg or lspci still shows a ntrig device.
> 
> 'lshw' or other hardware scanning tools might show something.
> 
> 
> Also install sys-apps/hwids  to the latest version and see if that
> hardware shows up.
> 
> hth,
> James
> 
> 

Unfortunately no ... the first device is 8086:9d3a which shows up, but
the touchscreen at 8086:9d3e dosent.  The problem is that the detection
code does not enumerate secondary devices - there was a patch against
the spi bus in the kernel a few versions back, but it wont apply to
4.6.1. This is the likely problem but the code is very opaque :(

I'll try and manually add an appropriate stanza in tonight.

BillK



^ permalink raw reply	[flat|nested] 6+ messages in thread

* [gentoo-user] Re: surface ntrig touchscreen
  2016-06-06  1:18   ` Bill Kenworthy
@ 2016-06-06  1:43     ` James
  2016-06-06  1:45     ` R0b0t1
  1 sibling, 0 replies; 6+ messages in thread
From: James @ 2016-06-06  1:43 UTC (permalink / raw
  To: gentoo-user

Bill Kenworthy <billk <at> iinet.net.au> writes:


> Unfortunately no ... the first device is 8086:9d3a which shows up, but
> the touchscreen at 8086:9d3e dosent.  The problem is that the detection
> code does not enumerate secondary devices - there was a patch against
> the spi bus in the kernel a few versions back, but it wont apply to
> 4.6.1. This is the likely problem but the code is very opaque :(


This info should be added to hwids upstream. So make contact there
and list the hardware and see if you can get it included.

> I'll try and manually add an appropriate stanza in tonight.


Munge around the kernel githubs, find the right dev and try that pathway.....

> BillK


hth,
James




^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [gentoo-user] Re: surface ntrig touchscreen
  2016-06-06  1:18   ` Bill Kenworthy
  2016-06-06  1:43     ` James
@ 2016-06-06  1:45     ` R0b0t1
  1 sibling, 0 replies; 6+ messages in thread
From: R0b0t1 @ 2016-06-06  1:45 UTC (permalink / raw
  To: gentoo-user

[-- Attachment #1: Type: text/plain, Size: 1330 bytes --]

On Jun 5, 2016 8:20 PM, "Bill Kenworthy" <billk@iinet.net.au> wrote:
>
> On 06/06/16 04:12, James wrote:
> > Bill Kenworthy <billk <at> iinet.net.au> writes:
> >
> >
> >> Has anyone been able to get the surface pro ntrig touchscreen to work
> >> ... and if so how?
> >
> > Sorry, never tried...
> >
> >> MS recently changed from the wacom to a ntrig touchscreen (they
> >> apparently bought the company!) for the latest pro models.  The kernel
> >> guys have a surface3_spi module being worked on which I have patched
> >> into 4.6.1 ... but neither dmesg or lspci still shows a ntrig device.
> >
> > 'lshw' or other hardware scanning tools might show something.
> >
> >
> > Also install sys-apps/hwids  to the latest version and see if that
> > hardware shows up.
> >
> > hth,
> > James
> >
> >
>
> Unfortunately no ... the first device is 8086:9d3a which shows up, but
> the touchscreen at 8086:9d3e dosent.  The problem is that the detection
> code does not enumerate secondary devices - there was a patch against
> the spi bus in the kernel a few versions back, but it wont apply to
> 4.6.1. This is the likely problem but the code is very opaque :(
>
> I'll try and manually add an appropriate stanza in tonight.
>
> BillK
>

Please post your results. I am able to help. I'm also interested in knowing
if you do it properly.

[-- Attachment #2: Type: text/html, Size: 1873 bytes --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2016-06-06  1:45 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-06-05  1:01 [gentoo-user] surface ntrig touchscreen Bill Kenworthy
2016-06-05 20:12 ` [gentoo-user] " James
2016-06-06  1:18   ` Bill Kenworthy
2016-06-06  1:43     ` James
2016-06-06  1:45     ` R0b0t1
2016-06-05 20:22 ` [gentoo-user] " R0b0t1

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox