From: Mike Frysinger <hidden> Date: 2010-03-09 14:51:20
On Mon, Mar 1, 2010 at 03:03, Dmitry Torokhov wrote:
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive first round of updates for the input subsystem.
i'm trying to figure out what the problem is with the ADXL34x and
AD714x drivers you seem to have accepted (at least, you didnt say
there was anything left for us to do). i would have expected them to
be in 2.6.33/2.6.34 already, but it seems they arent moving now. so
what's up ?
-mike
On Tue, Mar 9, 2010 at 6:44 AM, Mike Frysinger [off-list ref] wrote:
On Mon, Mar 1, 2010 at 03:03, Dmitry Torokhov wrote:
quoted
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive first round of updates for the input subsystem.
i'm trying to figure out what the problem is with the ADXL34x and
AD714x drivers you seem to have accepted (at least, you didnt say
there was anything left for us to do). i would have expected them to
be in 2.6.33/2.6.34 already, but it seems they arent moving now. so
what's up ?
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
I'm in the same boat with my TSC2046 driver. Any idea why this hasn't
moved? I have received no comments, nor has the driver been included
/ accepted. Do I need to make revisions, or can it be included?
- Cory
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Mar 09, 2010 at 09:44:08AM -0500, Mike Frysinger wrote:
On Mon, Mar 1, 2010 at 03:03, Dmitry Torokhov wrote:
quoted
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive first round of updates for the input subsystem.
i'm trying to figure out what the problem is with the ADXL34x and
AD714x drivers you seem to have accepted (at least, you didnt say
there was anything left for us to do). i would have expected them to
be in 2.6.33/2.6.34 already, but it seems they arent moving now. so
what's up ?
I am still spooked by the fact that this is an accelerometer and does
not have to be an input device but maybe used for different purposes as
well.
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Mar 09, 2010 at 08:15:06AM -0800, Cory Maccarrone wrote:
On Tue, Mar 9, 2010 at 6:44 AM, Mike Frysinger [off-list ref] wrote:
quoted
On Mon, Mar 1, 2010 at 03:03, Dmitry Torokhov wrote:
quoted
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive first round of updates for the input subsystem.
i'm trying to figure out what the problem is with the ADXL34x and
AD714x drivers you seem to have accepted (at least, you didnt say
there was anything left for us to do). i would have expected them to
be in 2.6.33/2.6.34 already, but it seems they arent moving now. so
what's up ?
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
I'm in the same boat with my TSC2046 driver. Any idea why this hasn't
moved? I have received no comments, nor has the driver been included
/ accepted. Do I need to make revisions, or can it be included?
I am yet to review the driver (usual time constraints, unfortunately).
Very sorry about it.
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Mike Frysinger <hidden> Date: 2010-03-09 17:58:48
On Tue, Mar 9, 2010 at 12:51, Dmitry Torokhov wrote:
On Tue, Mar 09, 2010 at 09:44:08AM -0500, Mike Frysinger wrote:
quoted
On Mon, Mar 1, 2010 at 03:03, Dmitry Torokhov wrote:
quoted
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive first round of updates for the input subsystem.
i'm trying to figure out what the problem is with the ADXL34x and
AD714x drivers you seem to have accepted (at least, you didnt say
there was anything left for us to do). i would have expected them to
be in 2.6.33/2.6.34 already, but it seems they arent moving now. so
what's up ?
I am still spooked by the fact that this is an accelerometer and does
not have to be an input device but maybe used for different purposes as
well.
the AD714x is not an accelerometer, it's a capacitance touch sensor
i understand the ADXL34x is a bit wonky, but what else would you
propose ? or just leave the driver in limbo forever until people
forget about it ?
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, Mar 09, 2010 at 12:58:24PM -0500, Mike Frysinger wrote:
On Tue, Mar 9, 2010 at 12:51, Dmitry Torokhov wrote:
quoted
On Tue, Mar 09, 2010 at 09:44:08AM -0500, Mike Frysinger wrote:
quoted
On Mon, Mar 1, 2010 at 03:03, Dmitry Torokhov wrote:
quoted
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive first round of updates for the input subsystem.
i'm trying to figure out what the problem is with the ADXL34x and
AD714x drivers you seem to have accepted (at least, you didnt say
there was anything left for us to do). i would have expected them to
be in 2.6.33/2.6.34 already, but it seems they arent moving now. so
what's up ?
I am still spooked by the fact that this is an accelerometer and does
not have to be an input device but maybe used for different purposes as
well.
the AD714x is not an accelerometer, it's a capacitance touch sensor
OK, will dig it up.
i understand the ADXL34x is a bit wonky, but what else would you
propose ? or just leave the driver in limbo forever until people
forget about it ?
No, just till we have proper framework for it to be merged into.
--
Dmitry
From: Mike Frysinger <hidden> Date: 2010-03-09 18:13:57
On Tue, Mar 9, 2010 at 13:10, Dmitry Torokhov wrote:
On Tue, Mar 09, 2010 at 12:58:24PM -0500, Mike Frysinger wrote:
quoted
On Tue, Mar 9, 2010 at 12:51, Dmitry Torokhov wrote:
quoted
On Tue, Mar 09, 2010 at 09:44:08AM -0500, Mike Frysinger wrote:
quoted
On Mon, Mar 1, 2010 at 03:03, Dmitry Torokhov wrote:
quoted
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive first round of updates for the input subsystem.
i'm trying to figure out what the problem is with the ADXL34x and
AD714x drivers you seem to have accepted (at least, you didnt say
there was anything left for us to do). i would have expected them to
be in 2.6.33/2.6.34 already, but it seems they arent moving now. so
what's up ?
I am still spooked by the fact that this is an accelerometer and does
not have to be an input device but maybe used for different purposes as
well.
the AD714x is not an accelerometer, it's a capacitance touch sensor
OK, will dig it up.
thanks
quoted
i understand the ADXL34x is a bit wonky, but what else would you
propose ? or just leave the driver in limbo forever until people
forget about it ?
No, just till we have proper framework for it to be merged into.
that sounds fine, but is there actually something in progress for that
? waiting for a framework no one is working on is the same in
practice ...
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Jonathan Cameron <hidden> Date: 2010-03-09 18:16:22
On 03/09/10 17:58, Mike Frysinger wrote:
On Tue, Mar 9, 2010 at 12:51, Dmitry Torokhov wrote:
quoted
On Tue, Mar 09, 2010 at 09:44:08AM -0500, Mike Frysinger wrote:
quoted
On Mon, Mar 1, 2010 at 03:03, Dmitry Torokhov wrote:
quoted
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive first round of updates for the input subsystem.
i'm trying to figure out what the problem is with the ADXL34x and
AD714x drivers you seem to have accepted (at least, you didnt say
there was anything left for us to do). i would have expected them to
be in 2.6.33/2.6.34 already, but it seems they arent moving now. so
what's up ?
I am still spooked by the fact that this is an accelerometer and does
not have to be an input device but maybe used for different purposes as
well.
the AD714x is not an accelerometer, it's a capacitance touch sensor
i understand the ADXL34x is a bit wonky, but what else would you
propose ? or just leave the driver in limbo forever until people
forget about it ?
Hi Mike,
Perhaps whilst this remains in debate it might merge under misc, or
even staging temporarily. That would avoid setting a precedent for
putting them in input. I personally agree with Dmitry's wish to
avoid feature drift in input, but then we don't have anything else ready
for the big time. Under staging the entire TODO list would be along
lines of awaiting a suitable framework... This is effectively what
is going to happen to the various Ambient Light sensor drivers for
pretty much the same reason (see responses to our recent pull request).
We certainly want to be careful not to loose good drivers like this
and also to make them available to those who wish to use them.
Jonathan
On Tue, Mar 09, 2010 at 01:13:34PM -0500, Mike Frysinger wrote:
On Tue, Mar 9, 2010 at 13:10, Dmitry Torokhov wrote:
quoted
On Tue, Mar 09, 2010 at 12:58:24PM -0500, Mike Frysinger wrote:
quoted
On Tue, Mar 9, 2010 at 12:51, Dmitry Torokhov wrote:
quoted
On Tue, Mar 09, 2010 at 09:44:08AM -0500, Mike Frysinger wrote:
quoted
On Mon, Mar 1, 2010 at 03:03, Dmitry Torokhov wrote:
quoted
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive first round of updates for the input subsystem.
i'm trying to figure out what the problem is with the ADXL34x and
AD714x drivers you seem to have accepted (at least, you didnt say
there was anything left for us to do). i would have expected them to
be in 2.6.33/2.6.34 already, but it seems they arent moving now. so
what's up ?
I am still spooked by the fact that this is an accelerometer and does
not have to be an input device but maybe used for different purposes as
well.
the AD714x is not an accelerometer, it's a capacitance touch sensor
OK, will dig it up.
thanks
quoted
quoted
i understand the ADXL34x is a bit wonky, but what else would you
propose ? or just leave the driver in limbo forever until people
forget about it ?
No, just till we have proper framework for it to be merged into.
that sounds fine, but is there actually something in progress for that
? waiting for a framework no one is working on is the same in
practice ...
I have high hopes that IIO will fill the needs of these kinds of devices.
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Mike Frysinger <hidden> Date: 2010-03-09 18:21:45
On Tue, Mar 9, 2010 at 13:18, Jonathan Cameron wrote:
On 03/09/10 17:58, Mike Frysinger wrote:
quoted
On Tue, Mar 9, 2010 at 12:51, Dmitry Torokhov wrote:
quoted
On Tue, Mar 09, 2010 at 09:44:08AM -0500, Mike Frysinger wrote:
quoted
On Mon, Mar 1, 2010 at 03:03, Dmitry Torokhov wrote:
quoted
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive first round of updates for the input subsystem.
i'm trying to figure out what the problem is with the ADXL34x and
AD714x drivers you seem to have accepted (at least, you didnt say
there was anything left for us to do). i would have expected them to
be in 2.6.33/2.6.34 already, but it seems they arent moving now. so
what's up ?
I am still spooked by the fact that this is an accelerometer and does
not have to be an input device but maybe used for different purposes as
well.
the AD714x is not an accelerometer, it's a capacitance touch sensor
i understand the ADXL34x is a bit wonky, but what else would you
propose ? or just leave the driver in limbo forever until people
forget about it ?
Perhaps whilst this remains in debate it might merge under misc, or
even staging temporarily. That would avoid setting a precedent for
putting them in input. I personally agree with Dmitry's wish to
avoid feature drift in input, but then we don't have anything else ready
for the big time. Under staging the entire TODO list would be along
lines of awaiting a suitable framework... This is effectively what
is going to happen to the various Ambient Light sensor drivers for
pretty much the same reason (see responses to our recent pull request).
We certainly want to be careful not to loose good drivers like this
and also to make them available to those who wish to use them.
i dont have any problems with where exactly the driver gets merged, or
if we have a goal we're working towards (in terms of a "better"
place). but drivers sitting in perpetual limbo sucks.
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Jonathan Cameron <hidden> Date: 2010-03-09 19:06:18
On 03/09/10 18:21, Mike Frysinger wrote:
On Tue, Mar 9, 2010 at 13:18, Jonathan Cameron wrote:
quoted
On 03/09/10 17:58, Mike Frysinger wrote:
quoted
On Tue, Mar 9, 2010 at 12:51, Dmitry Torokhov wrote:
quoted
On Tue, Mar 09, 2010 at 09:44:08AM -0500, Mike Frysinger wrote:
quoted
On Mon, Mar 1, 2010 at 03:03, Dmitry Torokhov wrote:
quoted
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive first round of updates for the input subsystem.
i'm trying to figure out what the problem is with the ADXL34x and
AD714x drivers you seem to have accepted (at least, you didnt say
there was anything left for us to do). i would have expected them to
be in 2.6.33/2.6.34 already, but it seems they arent moving now. so
what's up ?
I am still spooked by the fact that this is an accelerometer and does
not have to be an input device but maybe used for different purposes as
well.
the AD714x is not an accelerometer, it's a capacitance touch sensor
i understand the ADXL34x is a bit wonky, but what else would you
propose ? or just leave the driver in limbo forever until people
forget about it ?
Perhaps whilst this remains in debate it might merge under misc, or
even staging temporarily. That would avoid setting a precedent for
putting them in input. I personally agree with Dmitry's wish to
avoid feature drift in input, but then we don't have anything else ready
for the big time. Under staging the entire TODO list would be along
lines of awaiting a suitable framework... This is effectively what
is going to happen to the various Ambient Light sensor drivers for
pretty much the same reason (see responses to our recent pull request).
We certainly want to be careful not to loose good drivers like this
and also to make them available to those who wish to use them.
i dont have any problems with where exactly the driver gets merged, or
if we have a goal we're working towards (in terms of a "better"
place). but drivers sitting in perpetual limbo sucks.
-mike
In that case, I suggest asking Greg KH to pull it into staging for now
with suitable explanation (and perhaps an ack for putting it there from
Dmitry?)
Jonathan
From: Robin Getz <hidden> Date: 2010-03-09 19:39:55
On Tue 9 Mar 2010 13:20, Dmitry Torokhov pondered:
On Tue, Mar 09, 2010 at 01:13:34PM -0500, Mike Frysinger wrote:
quoted
On Tue, Mar 9, 2010 at 13:10, Dmitry Torokhov wrote:
quoted
On Tue, Mar 09, 2010 at 12:58:24PM -0500, Mike Frysinger wrote:
quoted
On Tue, Mar 9, 2010 at 12:51, Dmitry Torokhov wrote:
quoted
On Tue, Mar 09, 2010 at 09:44:08AM -0500, Mike Frysinger wrote:
[snip]
quoted
quoted
quoted
i understand the ADXL34x is a bit wonky, but what else would you
propose ? or just leave the driver in limbo forever until people
forget about it ?
No, just till we have proper framework for it to be merged into.
that sounds fine, but is there actually something in progress for that
? waiting for a framework no one is working on is the same in
practice ...
I have high hopes that IIO will fill the needs of these kinds of devices.
The fact of things is that many people are using this as pointing device.
I'm not convinced that IIO is the best place for these types of things...
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue 9 Mar 2010 13:20, Dmitry Torokhov pondered:
quoted
On Tue, Mar 09, 2010 at 01:13:34PM -0500, Mike Frysinger wrote:
quoted
On Tue, Mar 9, 2010 at 13:10, Dmitry Torokhov wrote:
quoted
On Tue, Mar 09, 2010 at 12:58:24PM -0500, Mike Frysinger wrote:
quoted
On Tue, Mar 9, 2010 at 12:51, Dmitry Torokhov wrote:
quoted
On Tue, Mar 09, 2010 at 09:44:08AM -0500, Mike Frysinger
wrote:
[snip]
quoted
quoted
quoted
quoted
i understand the ADXL34x is a bit wonky, but what else would you
propose ? or just leave the driver in limbo forever until people
forget about it ?
No, just till we have proper framework for it to be merged into.
that sounds fine, but is there actually something in progress for
that ? waiting for a framework no one is working on is the same
in practice ...
I have high hopes that IIO will fill the needs of these kinds of
devices.
The fact of things is that many people are using this as pointing device.
I'm not convinced that IIO is the best place for these types of
things...
Very true - this driver was originally targeted and designed as a typical human interface input device.
Greetings,
Michael
Analog Devices GmbH Wilhelm-Wagenfeld-Str. 6 80807 Muenchen
Sitz der Gesellschaft Muenchen, Registergericht Muenchen HRB 4036 Geschaeftsfuehrer Thomas Wessel, William A. Martin, Margaret Seif
From: Robin Getz <hidden> Date: 2010-03-12 20:55:42
On Wed 10 Mar 2010 03:30, Hennerich, Michael pondered:
Robin Getz wrote on 2010-03-09:
quoted
On Tue 9 Mar 2010 13:20, Dmitry Torokhov pondered:
quoted
On Tue, Mar 09, 2010 at 01:13:34PM -0500, Mike Frysinger wrote:
quoted
On Tue, Mar 9, 2010 at 13:10, Dmitry Torokhov wrote:
quoted
On Tue, Mar 09, 2010 at 12:58:24PM -0500, Mike Frysinger wrote:
quoted
On Tue, Mar 9, 2010 at 12:51, Dmitry Torokhov wrote:
quoted
On Tue, Mar 09, 2010 at 09:44:08AM -0500, Mike Frysinger
wrote:
[snip]
quoted
quoted
quoted
quoted
i understand the ADXL34x is a bit wonky, but what else would you
propose ? or just leave the driver in limbo forever until people
forget about it ?
No, just till we have proper framework for it to be merged into.
that sounds fine, but is there actually something in progress for
that ? waiting for a framework no one is working on is the same
in practice ...
I have high hopes that IIO will fill the needs of these kinds of
devices.
The fact of things is that many people are using this as pointing device.
I'm not convinced that IIO is the best place for these types of
things...
Very true - this driver was originally targeted and designed as a
typical human interface input device.
Dmitry:
Care to comment? I would prefer to come to some sort of conclusion. As Mike
said - leaving the driver in limbo forever isn't really a solution for
anyone....
On Fri, Mar 12, 2010 at 03:55:37PM -0500, Robin Getz wrote:
On Wed 10 Mar 2010 03:30, Hennerich, Michael pondered:
quoted
Robin Getz wrote on 2010-03-09:
quoted
On Tue 9 Mar 2010 13:20, Dmitry Torokhov pondered:
quoted
On Tue, Mar 09, 2010 at 01:13:34PM -0500, Mike Frysinger wrote:
quoted
On Tue, Mar 9, 2010 at 13:10, Dmitry Torokhov wrote:
quoted
On Tue, Mar 09, 2010 at 12:58:24PM -0500, Mike Frysinger wrote:
quoted
On Tue, Mar 9, 2010 at 12:51, Dmitry Torokhov wrote:
quoted
On Tue, Mar 09, 2010 at 09:44:08AM -0500, Mike Frysinger
wrote:
[snip]
quoted
quoted
quoted
quoted
i understand the ADXL34x is a bit wonky, but what else would you
propose ? or just leave the driver in limbo forever until people
forget about it ?
No, just till we have proper framework for it to be merged into.
that sounds fine, but is there actually something in progress for
that ? waiting for a framework no one is working on is the same
in practice ...
I have high hopes that IIO will fill the needs of these kinds of
devices.
The fact of things is that many people are using this as pointing device.
I'm not convinced that IIO is the best place for these types of
things...
Very true - this driver was originally targeted and designed as a
typical human interface input device.
Dmitry:
Care to comment? I would prefer to come to some sort of conclusion. As Mike
said - leaving the driver in limbo forever isn't really a solution for
anyone....
OK, you swayed my opinion about 3-axis accelerometers, I will review the
patch again (although IIRC I was pretty satisfied with it) and apply.
--
Dmitry
On Tue, Mar 09, 2010 at 01:13:34PM -0500, Mike Frysinger wrote:
On Tue, Mar 9, 2010 at 13:10, Dmitry Torokhov wrote:
quoted
On Tue, Mar 09, 2010 at 12:58:24PM -0500, Mike Frysinger wrote:
quoted
On Tue, Mar 9, 2010 at 12:51, Dmitry Torokhov wrote:
quoted
On Tue, Mar 09, 2010 at 09:44:08AM -0500, Mike Frysinger wrote:
quoted
On Mon, Mar 1, 2010 at 03:03, Dmitry Torokhov wrote:
quoted
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus
to receive first round of updates for the input subsystem.
i'm trying to figure out what the problem is with the ADXL34x and
AD714x drivers you seem to have accepted (at least, you didnt say
there was anything left for us to do). i would have expected them to
be in 2.6.33/2.6.34 already, but it seems they arent moving now. so
what's up ?
I am still spooked by the fact that this is an accelerometer and does
not have to be an input device but maybe used for different purposes as
well.
the AD714x is not an accelerometer, it's a capacitance touch sensor
OK, will dig it up.
thanks
Mike, could you please take a look at mny 'next' branch and give the
version there a try - I made a couple of small changes before
applying...
Thanks!
--
Dmitry
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
From: Mike Frysinger <hidden> Date: 2010-03-22 07:45:01
On Mon, Mar 22, 2010 at 02:37, Dmitry Torokhov wrote:
On Tue, Mar 09, 2010 at 01:13:34PM -0500, Mike Frysinger wrote:
quoted
On Tue, Mar 9, 2010 at 13:10, Dmitry Torokhov wrote:
quoted
On Tue, Mar 09, 2010 at 12:58:24PM -0500, Mike Frysinger wrote:
quoted
the AD714x is not an accelerometer, it's a capacitance touch sensor
OK, will dig it up.
thanks
Mike, could you please take a look at mny 'next' branch and give the
version there a try - I made a couple of small changes before
applying...
changes look ok to me, and it seems to build fine. maybe Barry can
give it a quick test to make sure it still probes/works, but i dont
see anything to suggest it wouldnt ...
if you're doing cosmetic fixes, i'd suggest squashing the attached into it too.
-mike