On Fri, Sep 9, 2011 at 11:27 AM, Favux ... wrote:
> OK, I'll do it that way and see if Ping minds.
If you are talking about adding res to input-wacom/2.6.36, I do not
mind. In fact, I am grateful for your contributions to linux-wacom and
linux-input. Any effort to bring the two repos in sync is
OK, I'll do it that way and see if Ping minds.
Wonder how long kernel.org is down for?
Dave
--
Why Cloud-Based Security and Archiving Make Sense
Osterman Research conducted this study that outlines how and why cloud
comp
On Fri, Sep 9, 2011 at 12:18 PM, Favux ... wrote:
> Hi Chris,
>
> Thanks, I missed it was in dtor's for-linus. So he did follow your
> suggestion. I did check dtor'is input branch and didn't see it.
I know how you feel. I'm always forgetting to check both and missing something.
>
> I have:
>
Hi Chris,
Thanks, I missed it was in dtor's for-linus. So he did follow your
suggestion. I did check dtor'is input branch and didn't see it.
I have:
static const struct wacom_features wacom_features_0xD5 =
{ "Wacom Bamboo Pen 6x8", WACOM_PKGLEN_BBFUN, 21650, 13700, 1023,
63, BAMBOO_
Oh yeah, I forgot to mention that I did rebase last week and saw 0xD5
in dtor's for-linus branch as this. Maybe you want to verify if your
patch matches since the naming is in line with our suggestions:
static const struct wacom_features wacom_features_0xD5 =
{ "Wacom Bamboo Pen 6x8",
Sounds good. You do input-wacom and I'll do linux-input at least
I'll do it once git.kernel.org issues are resolved. Hard to update my
clone right now.
Chris
On Thu, Sep 8, 2011 at 5:28 PM, Favux ... wrote:
> That sounds reasonable.
>
> I can resubmit the D5 and another patch to correct th
That sounds reasonable.
I can resubmit the D5 and another patch to correct the active areas
for the other Mediums to input-wacom. You'll handle linux-input?
Dave
--
Doing More with Less: The Next Generation Virtual Desk
And to make it a little more complicated, here is a Wacom site that
shows it as 217mm. Probably they are rounding because they list
everything in round numbers, including small as 147 instead of 147.2.
http://www.wacom.com.au/bamboo/whichone/
I can see why US site rounded down to 216mm. That's
Thanks Chris.
OK, we're confident of the Bamboo Small's active area.
You've tracked down and solved the Medium active area discrepancy.
I went ahead and looked at different Bamboo Medium models at different
Wacom sites. They all agree on 137mm (13700). But the other
dimension is a little varia
I just found older Medium Bamboo 1 on Amazon and it lists 21648, 13530
values as active area. So this was copy&paste error based on older
Bamboo's.
I also looked at linux history and it was my patch that first
introduced 0xD3 with wrong values (take from linuxwacom values though
at the time) and
OK, I was able to reproduce your testing on a D1 of 1420/9200 using
evtest though. I couldn't reproduce with xinput test because
xf86-input-wacom averaging. Even when I set Sample to 1, I still
couldn't do it. So something else on X side is averaging as well (or
we have a bug in Sample logic).
I don't know where they came from. I think some Wacom literature only
lists inches so there could be a rounding error. But usually they
list both and I'm pretty sure they convert from cm to inch.
In Calibration on the HOW TO page you can see me manually testing my
D1 with xinput test (as you des
I'll resubmit the lkml patch after we finish topic on this list.
Was the user able to test and see what real max reports occur?
I've no idea really were current values came from. I've never really
tested max. Just assumed someone got it right. :-)
In your values, its 0.02mm and 1.7mm off so kin
13 matches
Mail list logo
