Hi, please don't send me tcpdumps from interfaces. Instrument the driver, which is the lowest level which we have, for dumping the framebuffer at before willing at xmit function and on receiving. Don't know exactly the function inside at86rf230 driver, I said that previously. If the transmitted frame and received frame is different, then I don't know what's going on there and can't help you. It seems for me that your spi functionality is broken. The reason why you should not dump the wpan/lowpan interface is that the data goes through the layers and I will detect if the raw data which should be transmitted is correctly received. If not -> something weird goes wrong. And again, I would not trust the wpan/lowpan dumps because it will goes through layers which "could maybe" manipulate the raw data. My consideration was look if the "raw" data is correct, because we don't do anything which "raw" data. If you send "0xabcd" as frame to some node and the receiving node receives "0xefgh" then something goes wrong with the transceiver and I don't know why. So please capture the raw data with the printk_hex_dump functionality and do a diff afterwards. On transmit and receiving side. - Alex -- To unsubscribe from this list: send the line "unsubscribe linux-wpan" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
