On 7/22/09, Christopher Piggott <cpiggott@xxxxxxxxx> wrote:
> I think I have to add the symlink at one of the top two levels, but
> the port_number and idVendor/idProduct come lower (and themselves at
> different levels).
>
> I'm not sure how to reconcile this. I want to add a custom symlink on
> ALL of those things ... port_number 0, idVendor, idProduct. I knew
> about the restriction that all ATTR{} must match at the same level in
> a rule, but thought that I could construct a logical "and" operation
> by using GOTO and LABEL.
You can do that. For an individual rule, all ATTRS must match at the
same level. Each rule is treated separately though, so you should be
able to match at multiple levels by using multiple rules.
The technique as shown in your debug rules is workable, you would just
need to fix the problem with using != on ATTRS (and DRIVERS etc).
> Now that you've explained some of the rules, I guess I don't see why
> it can't go all the way back in the device hierarchy though. For
> instance, in the novatel case it would find an idVendor indicating
> "Novatel" and deeper in the ancestors it would find another saying
> "Intel" (for the USB controller) ..... but if ATTRS{idVendor} always
> finds the highest one, I don't see the problem?
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
