On Tue, Jan 19, 2010 at 8:21 PM, Jason Childs <
obliv...@users.sourceforge.net> wrote:
>
> > 0001-Input-wacom-Debian-patch-for-device-ids.patch
> >
> > No real comment on this one. It worked for me and I saw no issues.
> > I'm not sure I understand background of why patch was written. I
> > think the reason may be in mailing list archive but I didn't look.
>
> This came from the devel list a few weeks ago. It was supposed to help
> with the crashes I was seeing initially. I was fighting for spin locks
> around all static shared memory access in the kernel driver. But I
> promised Ping I'd back off on that since I haven't had any further
> crashes with the changes from the 0001 patch :).
>
I have a quick question for this patch: how difficult or reasonable would
it be for you to keep both the wacom_features_0x00 (etc.) and wacom_ids in
wacom_wac.c instead of moving to wacom_sys.c?
It makes much more sense to me, as a driver maintainer, to leave those two
sets of entity in wacom_wac,c since it can be shared among kernel releases.
The wacom_sys.c changes out of my control. But the good thing is that I
normally don't need to worry about those changes myself since kernel/input
maintainers would do the work for us.
Do you see my picture? I've asked this question in the other email thread
that you've cc'd to. Hope you don't feel too annoyed by hearing it again.
Ping
------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
Linuxwacom-devel mailing list
Linuxwacom-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
