On Thu, Apr 21, 2011 at 12:22 AM, Peter Hutterer <peter.hutte...@who-t.net> wrote: > On Mon, Apr 18, 2011 at 11:26:42AM -0700, Jason Gerecke wrote: >> Since only protocol 5 devices (Intuos, Cintiq) allow tool-specific >> serial numbers, we limit hotplugging to devices supporting that >> protocol. >> >> For this to work, we need to move the call to wcmInitModel (which >> several calls down sets common->wcmProtocolLevel) before the call >> to wcmParseOptions. From what I can tell, the order of calls shouldn't >> otherwise matter here. > > I dont think that will work for ISDv4. The baud rate is set during > wcmParseOptions and used in wcmInitModel.
I had a similar feeling but was trying to find to to confirm this is true. > > I think wcmParseOptions() should be split up into two separate parsing > options, one for model/system specific configuration and one for actual > options that apply to a tool. > I agree. Although I'd just call it something like wcmPreOpenParseOptions() and wcmPostOpenParseOptions() instead of giving it strict classifications on device/system vs. tool. For example, the Lenovo tablet resolution issue requires setting device wide MaxZ to 255 and its best to put that logic in the Post function to give higher priority than queried 127 value. So to me its more a priority issue then type of data issue. Chris ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Linuxwacom-devel mailing list Linuxwacom-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxwacom-devel
