This is the mail archive of the
ecos-devel@sourceware.org
mailing list for the eCos project.
What is the reason of not using the same struct for usbs_rx_endpoint and usbs_tx_endpoint ???
- From: "oliver munz @ s p e a g" <munz at speag dot ch>
- To: <ecos-devel at sourceware dot org>
- Date: Thu, 2 Feb 2006 00:15:52 +0100
- Subject: What is the reason of not using the same struct for usbs_rx_endpoint and usbs_tx_endpoint ???
- Reply-to: "oliver munz @ s p e a g" <munz at speag dot ch>
Im want my USB-driver to be able to change dynamical his endpoint
configurations... I dont't really understand the difference between the
usbs_rx_endpoint and usbs_tx_endpoint struct's. I want use only one of them,
and fill it with the rx- or tx-functions.
I think the only problem i can get, are the optional static IO-entry for the
USB-endpoints. But maybe its the better idea to make IO-entrys in a
USB-Class like CDC Package...
Is there somebody who can see other problems in using "usbs_rx_endpoint" as
tx-endpoint?
Thanks for any answer
Oliver Munz