[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2011-01-23 Thread djp
@Chase,

Thanks for the info. My xorg input module has a touch helper to detect
right clicks etc (like the tablet pc service in windows), I am trying to
get permission to convert this into a patch for possible inclusion into
xorg evdev. I saw your evdev hooks into grails and have been testing the
same with my driver but in the future hope to be able to use evdev
directly.


@Bryce, cheers


@All, 

I am closing this bug now. Please feel free to log individual questions or 
issues:
 - https://bugs.launchpad.net/nwfermi
 - https://answers.launchpad.net/nwfermi

** Changed in: nwfermi
   Status: New = Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi
  (proprietary) driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2011-01-20 Thread Tom Dickson
Has anyone been able to get this to work on 10.04-1 x64? I had it
working in 32 mode, but now I can't seem to get it to work on the Sony
VAIO VPCL135FX. My Xorg.log shows:

(II) config/udev: Adding input device Nextwindow Fermi Touchscreen 
(/dev/input/event10)
(**) Nextwindow Fermi Touchscreen: Applying InputClass evdev pointer catchall
(**) Nextwindow Fermi Touchscreen: Applying InputClass nw fermi
(II) LoadModule: nextwindow
(II) Loading /usr/lib/xorg/modules/input/nextwindow_drv.so
(II) Module nextwindow: vendor=X.Org Foundation
compiled for 1.9.0, module version = 0.0.1
Module class: X.Org XInput Driver
ABI class: X.Org XInput driver, version 11.0
(WW) module ABI major version (11) doesn't match the server's version (7)
(**) Option Device /dev/input/event10
(II) Nextwindow Fermi Touchscreen: Using device /dev/input/event10.
(**) Option UseTouchHelp 1
(II) Nextwindow Fermi Touchscreen: Using touch help.
(**) Option DragThreshold 10
(**) Option RightClickTimeout 1200
(**) Option DoubleClickTimeout 500
(**) Nextwindow Fermi Touchscreen: always reports core events
(II) XINPUT: Adding extended input device Nextwindow Fermi Touchscreen (type: 
TOUCHSCREEN)
(II) Nextwindow Fermi Touchscreen: On.
(II) config/udev: Adding input device Nextwindow Fermi Touchscreen 
(/dev/input/js0)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device Nextwindow Fermi Touchscreen 
(/dev/input/mouse3)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device Macintosh mouse button emulation 
(/dev/input/event2)
(**) Macintosh mouse button emulation: Applying InputClass evdev pointer 
catchall
(**) Macintosh mouse button emulation: always reports core events
(**) Macintosh mouse button emulation: Device: /dev/input/event2
(II) Macintosh mouse button emulation: Found 3 mouse buttons
(II) Macintosh mouse button emulation: Found relative axes
(II) Macintosh mouse button emulation: Found x and y relative axes
(II) Macintosh mouse button emulation: Configuring as mouse
(**) Macintosh mouse button emulation: YAxisMapping: buttons 4 and 5
(**) Macintosh mouse button emulation: EmulateWheelButton: 4, 
EmulateWheelInertia: 10, EmulateWheelTimeout: 200
(II) XINPUT: Adding extended input device Macintosh mouse button emulation 
(type: MOUSE)
(II) Macintosh mouse button emulation: initialized for relative axes.
(II) config/udev: Adding input device Macintosh mouse button emulation 
(/dev/input/mouse0)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device Sony Vaio Jogdial (/dev/input/event9)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device Sony Vaio Jogdial (/dev/input/mouse2)
(II) No input driver/identifier specified (ignoring)

but nothing seems to work.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi
  (proprietary) driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2011-01-19 Thread WebNuLL
Ubuntu, and Ubuntu but how about Gentoo? How i can run this driver on
other Linux based operating systems for desktop x86/amd64 computers?

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi
  (proprietary) driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2011-01-18 Thread Chase Douglas
djp,

For full multitouch support both in Ubuntu 10.10 and future releases,
the X evdev input module should be used. In 10.10 this will enable
support for the uTouch stack, and in 11.04 this will allow for
multitouch support through the X window system.

One should not need to use a different X input module. If you are using
a different X input module, please provide more information so we can
figure out the best way forward.

Just to clarify, Ubuntu 10.10 desktop edition has uTouch support as
well, but the only package with uTouch integration is the Unity window
manager. Since Unity doesn't come with 10.10 by default, it seems like
uTouch is missing even though it's still there :). Natty will have more
integration across multiple apps, and the desktop edition will ship
Unity by default too.

Thanks!

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi
  (proprietary) driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2011-01-18 Thread Bryce Harrington
Moving this bug report from 'xorg' to the new 'nwfermi' project.  At
this time this driver is not shipped with the ubuntu distribution but
rather provided by a PPA, so support will be at
https://bugs.launchpad.net/nwfermi/ and the Ubuntu distro task is a
'Wont Fix'.  (Actually, maybe some day it will be included in ubuntu
once distribution terms are sorted and so on, but that bridge can be
crossed in its own time.)

I would recommend people file reports about new issues as new bugs rather than 
adding to this bug report.  I expect djp will prefer to close this bug report 
now that the issues can be handled individually, but I'll leave that to him.  
:-)
https://bugs.launchpad.net/nwfermi/+filebug


** Also affects: nwfermi
   Importance: Undecided
   Status: New

** Changed in: xorg (Ubuntu)
   Status: In Progress = Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi
  (proprietary) driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2011-01-17 Thread WebNuLL
I tested nwfermi0.5 on Ubuntu and Gentoo Linux but multi-touch is still
not working.

My device:
Bus 001 Device 008: ID 1926:0086 NextWindow 1950 HID Touchscreen

I just see single mouse, cant touch more than one point on screen - its
looks like single touch.

On Ubuntu i just installed package and restarted computer, on Gentoo
Linux i copied all files, built kernel module, modified xorg
configuration - it should work but it isn't.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi
  (proprietary) driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2011-01-17 Thread Aymeric
Same as WebNuLL, on Ubuntu Lucid after installing package and restarted
computer, multitouch don't work.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi
  (proprietary) driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2011-01-17 Thread WebNuLL
Here is /var/log/Xorg.0.log

Xorg recognizing device, but i think it not classifying it as multi-
touch capable.

** Attachment added: xorg-nw-fermi
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/379313/+attachment/1797024/+files/xorg-nw-fermi

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi
  (proprietary) driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2011-01-17 Thread WebNuLL
I tried many combinations of input xorg settings in 70-nwfermi.conf but
it still doesn't work.

Any help?

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi
  (proprietary) driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2011-01-17 Thread WebNuLL
Im not a C programmer but i debugged the code, and found that kernel
module is always handling touchscreen as mouse.

** Attachment added: fermi-debug
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/379313/+attachment/1797040/+files/fermi-debug

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi
  (proprietary) driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2011-01-17 Thread djp
As far as I know the X included with ubuntu does not handle multitouch
input directly. Ubuntu has a multitouch framework called uTouch (not
installed on the desktop edition by default
(https://wiki.ubuntu.com/Multitouch).

If you want to relatively easily test if the kernel multitouch
information is being supplied a good example is the PyMT demo
(https://wiki.ubuntu.com/Multitouch/PyMT).

Although my X input driver might be blocking the gesture daemon
somehow...

Anyhow post bug reports at https://bugs.launchpad.net/nwfermi

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi
  (proprietary) driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2011-01-16 Thread djp
A annoncement for anyone who was waiting for multitouch support. There
is now a new release (0.5) at
https://launchpad.net/nwfermi/trunk/nwfermi0.5

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi
  (proprietary) driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2011-01-11 Thread djp
Ok I have created a launchpad project for nwfermi
(https://launchpad.net/nwfermi). Future nwfermi releases will be posted
there and anyone interested should be able to post bug reports,
questions, etc.

I havent made much progress with creating a source package for the ppa
yet (the various different tools and methods are overwhelming me!) but
should have a multitouch release ready shortly.

Cheers again for all the help Bryce.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi
  (proprietary) driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


Re: [Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2011-01-04 Thread Bryce Harrington
On Fri, Dec 24, 2010 at 02:28:50AM -, djp wrote:
 @Bryce, cheers that is helpful I will try to make a PPA early next year.
 I do have one question, is it possible to put a EULA type agreement (do
 not sue us etc) into a deb or PPA?

You can put it into the deb.

The PPA has a description field, but it's purely informational and
doesn't support click-thru-agreement type behavior.  It's good for
putting directions or caveats.

Regarding EULAs in debs, I've never done this myself, but you can put a
question into the preinst script.  Some more info (and a tutorial):

  
http://stackoverflow.com/questions/2154352/including-license-agreement-in-deb-file

Not sure how that'd work in conjunction with a PPA, so you'll want to
test it.  IIRC, it just does a text prompt on the command line, but
hopefully that'll get you in the right direction.

Some packages like mscorefonts and iirc some java packages include
install-time eula agreements, which might be worth studying.  Fwiw I
think fglrx and nvidia do *not* require click thru's, but I'm not sure
how they handle the EULA agreement - perhaps the way they solved it
would be worth looking at as an alternate approach.
 


___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2011-01-04 Thread Bryce Harrington
Alright, I'm going to move this bug report off -evdev and back to just
xorg for now (actually I think it really should belong to the kernel,
but we'll continue tracking it with X for now).

It sounds like this package will be requiring an EULA, which makes me
doubtful it's something we can distribute with Ubuntu itself.  Thus I'll
decline the nominations and drop the natty tag for now.

** Package changed: xserver-xorg-input-evdev (Ubuntu) = xorg (Ubuntu)

** Changed in: xorg (Ubuntu)
   Status: Triaged = In Progress

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) 
driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2011-01-04 Thread Bryce Harrington
djp, I would recommend that you create a nwfermi project in launchpad
for tracking the driver.  You can do this here:

https://launchpad.net/projects/+new

It's pretty easy, and I'd do it for you but I think you'd be better as
the owner of it so you have full control.

Once you have a project set up, you can attach one or more PPAs to it,
and we can move this bug report over to it.  It will have its own bug
tracker, and you can add public or private mailing lists if you'd like.
It should be straightforward but if you have any questions, feel free to
contact me directly.

** Tags removed: jaunty maverick natty needs-retested-on-lucid-by-june
patch

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) 
driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2010-12-25 Thread WebNuLL
I compiled kernel module, copied to
/lib/modules/2.6.36-gentoo-r5/kernel/drivers/usb/nw-fermi.ko where i had
old module.

killall nwfermi_daemon -9
rmmod nw-fermi
modprobe nw-fermi

The mouse automaticaly is moving fastly from down right to up left
corner very fast when i touch some point on screen i got old calibration
and screen working normally without any changes on calibration.

I will try today on Ubuntu (i have dualboot with Gentoo) to check whats
wrong.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) 
driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2010-12-25 Thread Jiandong Zheng
What is the purpose of the user space daemon (nwfermi_daemon) since
driver already uses event interface? As I am trying to use Dell touch
screen monior with ARM dev board, it won't work for me because I can't
find the armel daemon.

djp, can you also release armel deb?

Thanks!

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) 
driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2010-12-25 Thread Jiandong Zheng
What is the purpose of the user space daemon (nwfermi_daemon) since
driver already uses event interface? As I am trying to use Dell touch
screen monior with ARM dev board, it won't work for me because I can't
find the armel daemon.

djp, can you also release armel deb?

Thanks!

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) 
driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2010-12-23 Thread djp
@Bryce, cheers that is helpful I will try to make a PPA early next year.
I do have one question, is it possible to put a EULA type agreement (do
not sue us etc) into a deb or PPA?

@Mathijs, there will a multitouch release in January,  I havent seen
nwtool but I will take a look

@WebNuLL @ Aymeric, we already have a calibration facility, I will
explain how to use it in this new release

I am attaching fermi 0.4.5, the main fixes here are:
  - nwfermi_daemon udev coldboot doesnt always work
  - configuration settings are available via named pipe

To start the calibration procedure run the following command:
  ‘echo -e C\x02\x21\x01  /tmp/nwfermi0-tl-in’

The cursor will move to four locations around the screen and to complete
calibration you just need to touch and hold at the cursor positions
untill they move to the next location. Upon successful calibration
settings will be saved to /etc/nextwindow/nw-
fermi/_XX_DriverSettings.dat, you can delete this file to
return to factory defaults.

I hope this is helpful you all.

Cheers,
Dan


** Attachment added: nwfermi-0.4.5_i386.deb
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/379313/+attachment/1774978/+files/nwfermi-0.4.5_i386.deb

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) 
driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2010-12-23 Thread djp

** Attachment added: nwfermi-0.4.5_amd64.deb
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-evdev/+bug/379313/+attachment/1774979/+files/nwfermi-0.4.5_amd64.deb

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) 
driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2010-12-22 Thread Aymeric
After installing the nwfermi package on Ubuntu 10.04 my Samsung 22” Lapfit 
Touchscreen Monitor (LD220Z) work with the touchscreen.
Like #118 it's not calibrated, I can touch the left corners but not the right.
From the documentation of my screen, it seem to be multi-touch, but I don't 
know what application I can use to know if multi-touch work or not, so it's 
untested.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) 
driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2010-12-20 Thread WebNuLL
Im now using NextWindow touchscreen on Gentoo Linux and it works fine.
Its not callibrated (on Ubuntu too) - i can touch all but corners of screen.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) 
driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2010-12-15 Thread Mathijs
Hi,


@djp: Can you perhaps give a status update of the nw-fermi driver that includes 
mutlitouch capabilities?
@djp: have you also looked at the nwtool? It says it is able to set modes and 
save settings, (like those modes described in the Windows API). 
You can find nwtool here: https://patchwork.kernel.org/patch/64411/

Regards,

Mathijs

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) 
driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2010-12-15 Thread WebNuLL
djp, can you also add calibration possibility via xinput?

I can calibrate eGalax touchscreen in Samsung Q1 Tablet PC with this command:
xinput set-int-prop Touchkit HID-USB Touchscreen Evdev Axis Calibration 32 
80 3950 150 3900

It works perfectly, can it be possible with nwfermi?

Im installing Gentoo today, i dont know nwfermi will works correctly on
it, can you implement calibration function to driver?

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) 
driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp


[Ubuntu-x-swat] [Bug 379313] Re: Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) driver

2010-12-13 Thread Bryce Harrington
Hi djp,

Since PPAs require uploading source packages rather than pre-built debs,
what you'll need to do is create a wrapper source package, that contains
the precompiled binaries.  The build process for this package would
merely copy the appropriate binary into place.

I don't know if there is official documentation for doing this, but
here's a guide that explains it with examples:

http://www.debian-administration.org/articles/529

Hope this helps, let me know if you have more questions.

-- 
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-input-evdev in ubuntu.
https://bugs.launchpad.net/bugs/379313

Title:
  Handling NextWindow Touchscreen (multitouch) via the nwfermi (proprietary) 
driver

___
Mailing list: https://launchpad.net/~ubuntu-x-swat
Post to : ubuntu-x-swat@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-x-swat
More help   : https://help.launchpad.net/ListHelp