Re: DRM-KMS: add a devclass DV_DRMKMS and allow userconf to deal with classes

[Mouse <mouse%Rodents-Montreal.ORG@localhost>]

>>> [...DV_DRMKMS...userconf...]
>> [...devices in multiple classes...maybe use a separate namespace,
>> used by only config(1) and userconf?...]
> This is precisely why I ask for comment ;-)

:-)

> I have two requirements:

> - that the solution is not ad hoc i.e. that it can provide, in
> userconf, facilities not limited to drmkms (I don't want to implement
> a special case to recognize "drmkms" and to expand to all the STARred
> driver names implied);

I agree with this; special-casing drmkms would be...suboptimal.

> - that it will not imply to have to maintain special data for
> userconf to recognize some "magic" strings.

You already need that, in that userconf has to have some way to
recognize the string "drmkms" as a device category (hinted by the
"class =" syntax, but it still needs error-checking) and map it into
the corresponding DV_ value.  I don't see it as significantly worse for
config(1) to generate some data structure mapping device class names
into whatever userconf would need to affect all devices of that class.

Though it occurs to me that there are too many things called "class"
here.  "Group"?  "Category"?  "Collection"?

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		mouse%rodents-montreal.org@localhost
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B