On Sun, Jan 03, 2010 at 04:01:27PM +0100, Alberto Milone wrote:
> On Sunday 03 Jan 2010 12:42:19 you wrote:
> > this is too specific to the particular product and its quirks. It would be
> > better to use a tagging system or something similar. udev assigns a tag
> > based on whatever condition and that tag may be used by specific xorg.conf
> > sections. this way, you can tag your device as "need_touchpad_quirk" or
> > simply "inspiron" or whatever but the actual configuration is in
> > xorg.conf.d.
> >
> > I think this should fit into the current design and it is not bound to a
> > specific backend and splits configuration from quirk detection. Plus, how a
> > tag is assigned doesn't matter to us and what happens with the tags doesn't
> > matter for the tagger. How does that sound?
> >
> I really like this approach. Let's see if I fully understood your idea:
>
> the new system would allow us, for example, to have a udev rules file with
> the
> following line:
>
> ATTR{[dmi/id]product_name}=="Inspiron 1011|Inspiron 1012", \
> ENV{TAG}="Inspiron"
>
>
> and a file in the xorg.conf.d directory with, say, the "MatchTag" option:
>
> Section "InputClass"
> Identifier "synaptics"
> MatchIsTouchpad "true"
> MatchTag "Inspiron"
> Driver "synaptics"
> Option "AreaBottomEdge" 4100
> EndSection
>
> The quirk would be applied only if the tag matched the one assigned by udev.
>
> Is this correct?
yes, this was the idea, though we might need to think about namespacing the
tags. some discussion with the udev guys would be beneficial here.
Cheers,
Peter
_______________________________________________
xorg-devel mailing list
[email protected]
http://lists.x.org/mailman/listinfo/xorg-devel
