From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kay Sievers Date: Sat, 09 May 2009 11:49:09 +0000 Subject: Re: hal, udev and video4linux probers Message-Id: List-Id: References: <8ceb98f20905081004l52ac4b95h1c23d9e8ed209e37@mail.gmail.com> In-Reply-To: <8ceb98f20905081004l52ac4b95h1c23d9e8ed209e37@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable To: linux-hotplug@vger.kernel.org On Fri, May 8, 2009 at 22:38, Filippo Argiolas wrote: > On Fri, May 8, 2009 at 10:06 PM, Kay Sievers wrote: > Seems fine to me. Actually I had some spare time this evening and come > up with a similar program myself :P > Glad to see I was almost right on the way to do it. Attaching it here, > feel free to choose the one you like most (yours seems more simple, > probably is better). > Mine lists the capability into a single variable like > ID_V4L_CAPS=CApture:radio:tuner and it takes the device path as > argument just because I copied it from usb_id.c :) I've committed a merge of both versions. We can use the device node directly, so we don't need to look it up. I've used your all-in-one capability string, just added a leading and trailing ':", so matches can always use CAP =3D "*:capture:*" and can not get confused by other possible variables which start or end with the same string. We do this in other places like this already. Thanks, Kay