┏━━━┓
☆ 人妻との○秘の出会い
☆彡 完全永久無料の大人の社交場
┗━━━┛
大人のお付き合い〜割り切った交際♪ＳＥＸが大好きだから・・・
旦那では物足りない♪貴方の○○○が欲しいの・
☆。・:*:．・★,。・:*:．☆。・:*:．・★,☆。・:*:．・★,。・:*:．☆
完全永久無料⇒ http://i-lav.com/r20/index.php?media=pc734
☆。・:*:．・★,。・:*:．☆。・:
Hi,
I am using a telephony device, too, and seem to have similar issues. It
is a Yealink P1K for which there is a kernel driver available. As long
as this driver is not loaded the ALSA mixer controls (volume and mute)
work fine. But as soon as the kernel driver (or my own userspace driver)
star
On Sat, 5 May 2007 11:25:50 -0700 [EMAIL PROTECTED] wrote:
> http://bugzilla.kernel.org/show_bug.cgi?id=8432
>
>Summary: USB device keeps reseting while using ehci_hcd
> Kernel Version: 2.6.20
> Status: NEW
> Severity: high
> Owner: [EMAIL PROTEC
On Fri, 4 May 2007, Mike Nuss wrote:
> Further support (I dumped the 'dummy' td before freeing it). This is a
> new trace so the addresses won't match the last trace.
>
> kernel: ohci_hcd :00:13.0: leak ed c3e8e680 (#82) state 0 (has tds)
> kernel: ohci_hcd :00:13.0: ed->dummy td c3e8d8c0
--- Alan Stern <[EMAIL PROTECTED]> wrote:
> However it is usually the same endpoint number and the same device (even
> if the device number changes)? In that case we can tell the code where to
> look for errors, because we will always know when that particular endpoint
> file is created and whe
On Fri, 4 May 2007, Mike Nuss wrote:
> As I understand it, the HC will not do any queue processing while HeadP
> and TailP are equal (which is the case here; they are both pointing to
> dummy). This explains why nothing is happening - the HC will never do
> anything more with this endpoint because
On Sat, 5 May 2007, Chris Rankin wrote:
> --- Alan Stern <[EMAIL PROTECTED]> wrote:
> > When the crash does occur, does it always involve the same sysfs file (or
> > at least, the same endpoint number for the same device)?
>
> Not always, no. But it *usually* does. This is the endpoint whose dir
On Fri, 4 May 2007, Oliver Neukum wrote:
> Am Freitag, 4. Mai 2007 21:46 schrieb Alan Stern:
> > On Fri, 4 May 2007, Oliver Neukum wrote:
> >
> > > > A better approach would be to have a routine which would block until
> > > > all
> > > > URBs on an anchor have completed. With a timeout, so th
This was partly my fault. They were all queued up as the author had bcced
the list (at least that is what lists.sf.net thought). I rejected on set
but didn't realise there was eight copies in each of the two sets...
On Fri, 4 May 2007, David Brownell wrote:
> On Thursday 03 May 2007, Ragner Mag
--- Alan Stern <[EMAIL PROTECTED]> wrote:
> When the crash does occur, does it always involve the same sysfs file (or
> at least, the same endpoint number for the same device)?
Not always, no. But it *usually* does. This is the endpoint whose directory is
being repeatedly
created and destroyed.
From: Rene van Paassen <[EMAIL PROTECTED]>
Documentation on the changes from the v1.5 to the v2.3 version.
Also updated credits and version number to 2.3
Signed-off-by: Rene van Paassen <[EMAIL PROTECTED]>
---
drivers/usb/input/aiptek.c | 27 +--
1 files changed, 25 ins
From: Rene van Paassen <[EMAIL PROTECTED]>
function keys (called macro keys too, why?) code corrected. Using a
lastMacro variable to keep track of key currently pressed. This ensures
proper resetting when dragging the pen in the drawing area or to another
key. Also suppress sending pressure report
From: Rene van Paassen <[EMAIL PROTECTED]>
now echo "some value" > /sys/.../somefile is also acceptable
By the way, all trailing characters are ignored
Signed-off-by: Rene van Paassen <[EMAIL PROTECTED]>
---
drivers/usb/input/aiptek.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(
From: Rene van Paassen <[EMAIL PROTECTED]>
Added warnings to the points where the tablet probe may fail
Signed-off-by: Rene van Paassen <[EMAIL PROTECTED]>
---
drivers/usb/input/aiptek.c | 28 ++--
1 files changed, 22 insertions(+), 6 deletions(-)
diff --git a/drivers/
From: Rene van Paassen <[EMAIL PROTECTED]>
Now the old tool is remembered, and reset when a new tool is selected via
the sysfs files.
Signed-off-by: Rene van Paassen <[EMAIL PROTECTED]>
---
drivers/usb/input/aiptek.c | 98
1 files changed, 54 insert
From: Rene van Paassen <[EMAIL PROTECTED]>
To get an on - off reporting for proximity, absolute misc reports are
used. The mixture of absolute and relative reports is awkward
Signed-off-by: Rene van Paassen <[EMAIL PROTECTED]>
---
drivers/usb/input/aiptek.c |5 -
1 files changed, 4 inser
From: Rene van Paassen <[EMAIL PROTECTED]>
Have to use set_bit since some bit values are over 32, and bitwise or
won't work on these. To be safe for the future too, use set_bit for all
input dev capabilities
Signed-off-by: Rene van Paassen <[EMAIL PROTECTED]>
---
drivers/usb/input/aiptek.c | 2
From: Rene van Paassen <[EMAIL PROTECTED]>
corrections to relative mode, was looking at wrong byte
Signed-off-by: Rene van Paassen <[EMAIL PROTECTED]>
---
drivers/usb/input/aiptek.c | 12 +++-
1 files changed, 7 insertions(+), 5 deletions(-)
diff --git a/drivers/usb/input/aiptek.c b/d
From: Rene van Paassen <[EMAIL PROTECTED]>
Mouse button defines tested the wrong bits, now fixed
Signed-off-by: Rene van Paassen <[EMAIL PROTECTED]>
---
drivers/usb/input/aiptek.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/usb/input/aiptek.c b/drivers/u
From: Rene van Paassen <[EMAIL PROTECTED]>
Calculation of proximity bit and of data valid bit was reversed for
stylus reports
Signed-off-by: Rene van Paassen <[EMAIL PROTECTED]>
---
drivers/usb/input/aiptek.c | 16
1 files changed, 8 insertions(+), 8 deletions(-)
diff --git a
From: Rene van Paassen <[EMAIL PROTECTED]>
Small fix that corrects the documentation on the report byte
format produced by the mouse
Signed-off-by: Rene van Paassen <[EMAIL PROTECTED]>
---
drivers/usb/input/aiptek.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/driv
From: Rene van Paassen <[EMAIL PROTECTED]>
When setting up input device use an array to list all the buttons
instead of setting every bit separately.
Signed-off-by: Rene van Paassen <[EMAIL PROTECTED]>
---
drivers/usb/input/aiptek.c | 29 -
1 files changed, 12 inser
From: Rene van Paassen <[EMAIL PROTECTED]>
There is no reason to do that, just tell the compiler that
we are dealing with signed values in buffer, that's it.
Signed-off-by: Rene van Paassen <[EMAIL PROTECTED]>
---
drivers/usb/input/aiptek.c | 24 ++--
1 files changed, 2 ins
From: Rene van Paassen <[EMAIL PROTECTED]>
Use maps to convert for strings to internal constants and vice versa
in aiptek's sysfs attribute methods instead of open-coding it. This
results in smaller code that is also easier to maintain.
Signed-off-by: Rene van Paassen <[EMAIL PROTECTED]>
---
dri
From: Rene van Paassen <[EMAIL PROTECTED]>
It makes no sense to check for NULL in attribute methods -
we do usb_set_intfdata before creating attributes and once
attributes have been removed we are guaranteed to not be
called.
Signed-off-by: Rene van Paassen <[EMAIL PROTECTED]>
---
drivers/usb/in
From: Rene van Paassen <[EMAIL PROTECTED]>
Use attribute group as per the patch by Dmitry
Corrected by adding a NULL in the aiptek_attributes list (had a nice crash)
Signed-off-by: Rene van Paassen <[EMAIL PROTECTED]>
---
drivers/usb/input/aiptek.c | 109
From: Rene van Paassen <[EMAIL PROTECTED]>
They are alreay exported by input corei; there is no need to do it twice.
Signed-off-by: Rene van Paassen <[EMAIL PROTECTED]>
---
drivers/usb/input/aiptek.c | 73
1 files changed, 0 insertions(+), 73 deleti
From: Rene van Paassen <[EMAIL PROTECTED]>
Donot try to export via sysfs associated event device - it does not
work when evdev is a module that is loaded after aiptek; also it pokes
too deply into input core internals.
Userspace should rely on udev to set up permanent device name for
touchpad.
S
This is a series of patches for the aiptek usb tablet driver.
The series represents the development done on aiptektablet.sourceforge.net
over the last years. It is a substitute for the mega-patch I sent earlier
(sorry about that). I produced these patches on Dmitry's kernel tree.
The first seven
29 matches
Mail list logo
