I suppose we need to figure out this chip identification/detection before the patch can be accepted.
So, David: - Have you tried using the driver, the VLANs? Did it happen to work, did it fail catastrophically, dit it just do nothing? :) - Could you perhaps compile the ADM6996 driver with #define DEBUG 1, and run the attached script on your device. It dumps all the MDIO-accessible registers. I'd like to see what it is like on your device. Especially because of the Chip Identifier register, which the driver tries to use to determine if a compatible chip is attached. Perhaps I will even recognise some registers by their initial value. Thanks, Peter. -- I use the GNU Privacy Guard (GnuPG) in combination with Enigmail. You can send me encrypted mail if you want some privacy. My key is available at http://wwwhome.cs.utwente.nl/~lebbing/pubkey.txt (new, larger key created on Nov 12, 2009)
#!/bin/sh echo -n >regs for x in $(seq 0 1023); do swconfig dev eth0 set addr $x echo $x $(swconfig dev eth0 get data) >>regs done
_______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel
