public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Sarah A Bailey" <saharabeara@gmail.com>
To: ecos-discuss@ecos.sourceware.org
Subject: [ECOS] USB with eCos?
Date: Thu, 01 Jun 2006 00:31:00 -0000	[thread overview]
Message-ID: <4c8f91e80605311731h63f864a7qbe89bbc89c46f0eb@mail.gmail.com> (raw)

Greetings,
I'm currently working on a project with Portland State Aerospace
Society[1] that involves using eCos on an LPC2148 board.  I've used
Pawel Wodnicki's patch[2] to port eCos and a simple "hello blinky
world" program to the board.

Eventually, we'd like to use the LPC2148 in a USB application.  I've
been reading the current documentation on writing a USB device driver
with eCos, and I have a couple questions:

First, is it still true that there's only been one USB device driver
written with eCos?  (I know documentation doesn't always keep up with
the code base.)  Is the lack of USB drivers due to flaws in eCos, a
steep learning curve, no need for USB drivers, or something else?

Where is that USB device driver located in the repository?

Has anyone added isocronous transfer support to the eCos USB base?
The documentation seemed to imply this was something that would be
added soon.  I'm willing to work on this, but I wanted to check first
and see if someone else was.

Whew, that was a lot of questions. :)  Thanks in advance for any answers.

Sarah Bailey

[1] http://psas.pdx.edu
[2] http://sourceware.org/ml/ecos-patches/2005-11/msg00014.html

-- 
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss

             reply	other threads:[~2006-06-01  0:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-01  0:31 Sarah A Bailey [this message]
2006-06-01  6:45 ` Andrew Lunn

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=4c8f91e80605311731h63f864a7qbe89bbc89c46f0eb@mail.gmail.com \
    --to=saharabeara@gmail.com \
    --cc=ecos-discuss@ecos.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).