After extensive testing, it's clear that the omap driver in kernel/drivers/w1/masters/omap_hdq.c reports the slave address in reversed byte order compared to all the other drivers.
This is in the netlink LIST_SLAVE message. I've discovered this when testing support in OWFS -- one-wire-file-system (www.owfs.org) which is probably the most comprehensive 1-wire support around. I'd be glad to supply detailed information. The sysfs report is correct, and the CRC8 is computed correctly. If I just reverse the netlink slave addresses, everything functions well. If it is not possible to correct the driver, my next alternative is to always test the address forward and backward (the CRC8 will probably work only in one direction) and compensate for the bug in that manner. Paul Alfille -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
