From: "oliver munz @ s p e a g" <munz@speag.ch>
To: <ecos-devel@sourceware.org>
Subject: Changing the USB-driver datas... Using an array: usb_working_endpoint ep[ENDPOINTS-1]
Date: Tue, 07 Feb 2006 00:02:00 -0000 [thread overview]
Message-ID: <049901c62b7a$08013860$1f01a8c0@haus.hellmutstrasse.ch> (raw)
I think the eCos-USB-slave endpoint data structures should be changed. The
USB-slave-package should define one struct for all endpoint types whitout
the control-endpoint.
The device-driver should define an array of all working endpoint-structs
ep1..n. All enndpoint-functions should get an index variable, so that they
can address the right struct from the array.
The device-driver and the USBS-interface should define a function to control
the type and state of an working endpoint.
I don't see any reason in using blabla_ep1(&ep1) and so on, instead of
something like blabla_ep(ep_array, 1);
Are there other ideas how to improve the USBS and USB-driver APIs?
Thanks
Oliver Munz
next reply other threads:[~2006-02-07 0:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 0:02 oliver munz @ s p e a g [this message]
2006-06-02 15:22 ` Frank Pagliughi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='049901c62b7a$08013860$1f01a8c0@haus.hellmutstrasse.ch' \
--to=munz@speag.ch \
--cc=ecos-devel@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).