From: Bart Veer <bartv@redhat.com>
To: tim@cygnetinc.com
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] USB host mode support?
Date: Tue, 20 Feb 2001 05:26:00 -0000 [thread overview]
Message-ID: <200102201325.f1KDPGj27999@host184.cambridge.redhat.com> (raw)
In-Reply-To: <NEBBKDICKKKKBCIKLHHKAEKNCJAA.tim@cygnetinc.com>
>>>>> "Tim" == Tim Michals <tim@cygnetinc.com> writes:
Tim> All,
Tim> Is this in the works?
Not as far as I know.
In some ways eCos and USB host support do not really go together. USB
involves plug and play so you cannot know in advance what USB
peripherals may get plugged in - including ones that have not even
been invented yet at the time you ship your eCos-based product. This
implies that you will need to load appropriate device drivers at
run-time, and eCos does not support dynamic loading of code.
There may be specific applications where this does not matter,
especially if you know in advance exactly what is going to be
connected to the USB bus, but for a general-purpose host solution you
would be looking at something like embedded Linux rather than eCos.
Of course when it comes to developing USB peripherals, eCos may well
be a sensible choice. Red Hat has recently contributed USB slave
support.
Bart
next prev parent reply other threads:[~2001-02-20 5:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-17 21:54 [ECOS] new ecosconfig tool di yan
2001-02-18 6:06 ` Lewin A.R.W. Edwards
2001-02-19 6:29 ` Bart Veer
2001-02-19 6:33 ` Lewin A.R.W. Edwards
2001-02-19 6:53 ` [ECOS] Still having problems getting networking up Bart Veer
2001-02-19 22:13 ` [ECOS] new ecosconfig tool di yan
2001-02-23 9:47 ` Jonathan Larmour
2001-02-19 13:32 ` [ECOS] USB host mode support? Tim Michals
2001-02-20 5:26 ` Bart Veer [this message]
2001-02-20 5:32 ` Tim Michals
2001-02-20 5:54 ` Lewin A.R.W. Edwards
2001-02-20 6:17 ` Tim Michals
2001-02-20 7:10 ` Andrew Lunn
2001-02-20 7:41 ` Lewin A.R.W. Edwards
2001-02-20 9:50 ` Tim Michals
2001-02-20 10:11 ` Lewin A.R.W. Edwards
2001-02-21 6:42 ` Bart Veer
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=200102201325.f1KDPGj27999@host184.cambridge.redhat.com \
--to=bartv@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=tim@cygnetinc.com \
/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).