Re: [PATCH v2 0/7] Input: elantech: add support for newer hardware

[JJ Ding <jj_ding@emc.com.tw>]

Sorry.
linux-kernel and linux-input complains patch #2's subject
ETP_2FT_XXXX looks like spam.
(5.1.0 - Unknown address error 550-'5.7.1 Content-Policy reject msg: The
capital Triple-X in subject is way too often associated with junk email,
please rephrase.  BF:<H 0>; S1752956Ab1HXFgV'
)
so patch #2 is blocked.
Please ignore this series.
I will rephase and resend.

Sorry for the noise.

jj

On Wed, 24 Aug 2011 13:38:16 +0800, JJ Ding <jj_ding@emc.com.tw> wrote:
> Hi Lists,
> 
> This is a series of patches to add support for newer generation of ELAN
> touchpad.
> 
> Patches #1~#6 are essentially fixes and cleanups that pave the way for
> patch #7, which really adds code for v3 hardware.
> 
> Any comments, suggestoins are welcome.
> 
> Thank you.
> 
> Changes since v1:
> - drop EC workaround patch.
> - add patch #2, make ST and MT have the same range, as Dmitry suggested.
> - add patch #4, remove ETP_EDGE_FUZZ_V2, as Éric suggested.
> - rename all packet checking functions so they are consistent.
> - some code cleanup, and don't report ABS_[XY] when fingers == 0, as Seth suggested.
> - add document for v3 debounce, and now check debounce in elantech_packet_check_v3.
> 
> JJ Ding (7):
>   Input: elantech - correct x, y value range for v2 hardware
>   Input: elantech - get rid of ETP_2FT_XXXX in elantech.h
>   Input: elantech - use firmware provided x, y ranges
>   Input: elantech - remove ETP_EDGE_FUZZ_V2
>   Input: elantech - packet checking for v2 hardware
>   Input: elantech - clean up elantech_init
>   Input: elantech - add v3 hardware support
> 
>  Documentation/input/elantech.txt |  125 +++++++++++--
>  drivers/input/mouse/elantech.c   |  387 +++++++++++++++++++++++++++++++-------
>  drivers/input/mouse/elantech.h   |   35 ++--
>  3 files changed, 444 insertions(+), 103 deletions(-)
> 
> -- 
> 1.7.4.1
> 
--
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