On Fri, Mar 25, 2011 at 1:28 AM, Werner Almesberger <[email protected]> wrote: > Richard Sharpe wrote: >> What endpoints exist in the ATMEGA32U2? What is the firmware? > > ben-wpan/atusb/fw/ep0.c is the "heart" of the firmware. It's just raw > register and send/receive frame buffer access. Its counterpart is in > ben-wpan/tools/lib/ (atrf.c for the device-independent API, atusb.c > for the device-specific driver.) > > Hmm, we should continue this discussion on the list. Not only may > other people be interested (or get drawn into the project ;-), but > it's also good to show some activity.
OK, thanks for that info. I have started having brief thoughts about the drivers necessary for these parts in the the kernel as well. Since the two devices are different, we will need different drivers. However, since the model is one of accessing registers on the RF controller chip, but directly by SPI on the Ben, while via USB on the ATUSB, it seems that there is a lot of commonality, and we can split the driver into two layers. For the ATUSB, the bottom layer will talk to the USB layer on Linux, while for the Ben version, the bottom layer will be an SPI-based layer that uses the SPI capabilities of SDIO, and later will directly interface with SPI on the subsequent product. Does this sound reasonable? -- Regards, Richard Sharpe _______________________________________________ Qi Hardware Discussion List Mail to list (members only): [email protected] Subscribe or Unsubscribe: http://lists.en.qi-hardware.com/mailman/listinfo/discussion
