Stefan Schmidt wrote:
> 1) Fill in the bwPollTimeout value with a sensible value (?6.1).

I set it to 100 ms. If I understand things correctly, this should
be the time it takes the device to process one packet. The MCU
takes about 5 ms per Flash operation, making the worst case (write
followed by erase) 10 ms plus processing overhead.

> 2) Have a real USB from the USB forum assigned and be prepared to have
> a way to identify between different hardware revisions.

atusb uses a PID under the official VID of qi-hw. It's even
registered at ... wait a minute ! www.linux-usb.org has fallen
into the clutches of a domain grabber ? Wow :-(

I don't manage bcdDevice for now. There's a bunch of ID features
in the atusb-specific protocol, though.

> 3) Add a dfu-suffix to your firmware file.

Okay, that may be something useful to add in the future. Not that
it would be particularly horrible to flash some junk, because
recovery is easy enough.

- Werner

_______________________________________________
Qi Hardware Discussion List
Mail to list (members only): [email protected]
Subscribe or Unsubscribe: 
http://lists.en.qi-hardware.com/mailman/listinfo/discussion

Reply via email to