I never got any comment back on this. In order for udev to use the existing attribute, it needs to be moved out of the scsi_host device, and udev needs patched to handle bitwise comparisons, or my simple patch adding the new attribute can be applied. Are you certain you do not want to add a new attribute, and if so, would you accept a patch moving the existing one out of the scsi_host device so it will be a proper ancestor of the disk device? On 11/13/2010 10:46 AM, Phillip Susi wrote: > On 11/13/2010 12:30 AM, Jeff Garzik wrote: >> As you noted in your previous mail, the entire PORT_CMD is already >> exported as a attribute. I don't see much point in exporting this >> information a second time. > > Unfortunately it is not exported in a way that udev can make use of it. > Firstly because udev can only compare on specific value matches rather > than an individual bit, and secondly because it is in the weird > scsi_host device rather than the host device, so the attribute is not in > an ancestor device of the disk device. Placing this attribute this way > puts it in the ancestry of the disk device so it can be matched by a > udev ATTRS rule. -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
