Hi folks, I've written a 1Wire slave implementation for ARM (which I will be open sourcing), in order to implement some functionality that does not exist in the 1Wire world (multichannel RGBW control).
Given the small amount of address space available in the family, I figured the best course of action for further implementations would be to keep the family code, and add a command to allow the master to query the device specifics. The problem I am now facing is how to cache the information, and despatch calls to the appropriate driver (of which there is only 1 at the moment) once a device appears on the bus. I was thinking of adding an opaque, device instance specific struct pointer somewhere under the parsedname struct, as well as init and term function pointers in the device struct. The init call could then query the device subtype, and stash it away in the device instance specific struct, and potentially alter the visibility of the files so that only the relevant content is visible to the user. Could you please advise whether I am on the right track, or if there is a better solution? Cheers, -- Alastair D'Silva mob: 0423 762 819 skype: alastair_dsilva msn: alast...@d-silva.org blog: http://alastair.d-silva.org Twitter: @EvilDeece ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
