Finally got around to resolving this over the winter holiday. Built a bodhi kernel with yaffs2 ported into it, extracted the gzipped ext image file from the MTD rootfs, disassembled and string'ed out zyshd to get: # i2cset -y 0x0 0x50 0x06 0x01 b (One byte before the magic address for the NSA325.) One more bit of data for your Wiki. Thank you a million times over bodhi for all the woby Safari Jack - Debian
No dice, nothing on i2c-0 at that address # /usr/sbin/i2cdetect -y 0 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 5by Safari Jack - Debian
I've looked around several times in the forum for NSA320 I2C settings for this. I've found the 310 thread which I had hoped would be close enough, but I2C read shows the bits are already set in that register, so it must be somewhere else. No luck elsewhere on Google either. Does anybody have the magic settings for these by any chance? If so, it would be a handy thing to add to theby Safari Jack - Debian
I swear I'm not crazy, but now it's matching Was ~/Downloads$ sha256sum Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855 Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 ~/Downloads$ rm Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2 (downloaded it again...) ~/Downloads$ md5sum Debian-5.2.9-kirkwood-tld-1-rootby Safari Jack - Debian
I just downloaded Debian-5.2.9-kirkwood-tld-1-rootfs-bodhi.tar.bz2, but the sha256 signature does not match the value in the first post. Did something secretly change?by Safari Jack - Debian