Hello. On 08/18/2017 12:26 PM, Josef Filzmaier wrote:
Hi! I did refactor both repositories. I think they should now be much more enjoyable to review ;) - I would however like you to have another quick look within my github repo before i git send-mail it to the mailing list.
Will do that in a moment.
I rebased the patch of the linux driver to the 4.13-rc5 source code so it should be much easier to mainline. It is only a single commit, i was not sure how i should separate the commits without having "dead code". I think the patch is small enough that one commit is still feasible. [1]
It looks ok to be in one commit. It also applies cleanly on net-next which I use for testing.
I did separate the firmware into two commits: One that enables debugging and one that introduces the new board (with refactoring). [2]
Good.
The changes were tested again on the raspberry pi with linux 4.13-rc5 and both patches applied (Firmware and Kernel).
I did some testing now and so far it all looks good. The combinations I tested so far are:
1) ATUSB mainline driver + firmware with your patch 2) ATUSB driver with your patch + mainline firmware version 3) ATUSB driver with your patch + firmware with your patch No problems spotted so far. Good job! :) I still need to dig out my rzusb hardware and test it there as well.
Today i finally sent you the Busware HUL dongle, so you should receive it sometime next week.
It arrived, thanks a lot. How would I go about flashing it? I build the firmware already but I'm a bit unsure how the flashing would go. Do I need JTAG or SPI or can it be done with the Atmel DFU variant (I think the tool is called dfu-programmer)?
What would be the commandline for the flashing? Would be nice if we could document that for others.
regards Stefan Schmidt -- 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
