public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: tim@cygnetinc.com (Tim Michals)
To: "Lewin A.R.W. Edwards" <larwe@larwe.com>,
	<ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] USB host mode support?
Date: Tue, 20 Feb 2001 06:17:00 -0000	[thread overview]
Message-ID: <NEBBKDICKKKKBCIKLHHKIELECJAA.tim@cygnetinc.com> (raw)
In-Reply-To: <4.3.2.7.2.20010220084532.00b46140@larwe.com>

Lewin,

>I'm curious to know what kind of USB peripherals you think will be
>important to support in embedded systems. It would be pretty easy to add
>generic HID support, but almost every other device you can think of is
>proprietary. There are some generic chipsets e.g. for ATA interfaces and
>scanners, but often the implementation is customized so a vanilla driver
>won't work properly. Basically you're buying into the whole minefield of
>maintaining a general-purpose operating system, when consumers call you and
>say "My new widget no worky when I plug it in". So at that point it makes
>perfect sense (to me to cross over to a GP OS like Linux, as Bart said.

Mostly wireless USB devices, the idea is still to keep the OS very small and
able to do some type of plugNPlay.  ie download a new OS if required.
Dynamic loading
would be nice.  I agree to some of the ideas of Linux, but the issue is we
have a size
issue.  Yes, USB is a pain to support on the host side.  But as devices
become
more internet and device aware this will become a requirement.
Also, it is still me understanding most of the USB device support under
Linux must
be compiled, therefore, as you add a new device you must recompile the OS?

>As another BTW, although eCos doesn't explicitly support dynamic loading,
>it is possible to implement it with some magic. I have a (grossly
>imperfect) module-loader as a work-in-progress. The reason I need one is
>because we wish to allow developers to write add-on modules for our product
>without wiping the whole OS out of flash. I seem to recall someone (Grant
>Edwards?) writing about a similar need on the list some weeks ago.

Thanks

-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com
[ mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of Lewin A.R.W.
Edwards
Sent: Tuesday, February 20, 2001 7:53 AM
To: ecos-discuss@sources.redhat.com
Subject: RE: [ECOS] USB host mode support?


Hi Tim,

>I think as more embedded systems grow there will be a need for host mode
>USB.  At this time I'm going to try a do a host mode version.  Do you see
>any big issues in porting BSD or Linux implementation to eCOS?

I'm curious to know what kind of USB peripherals you think will be
important to support in embedded systems. It would be pretty easy to add
generic HID support, but almost every other device you can think of is
proprietary. There are some generic chipsets e.g. for ATA interfaces and
scanners, but often the implementation is customized so a vanilla driver
won't work properly. Basically you're buying into the whole minefield of
maintaining a general-purpose operating system, when consumers call you and
say "My new widget no worky when I plug it in". So at that point it makes
perfect sense (to me to cross over to a GP OS like Linux, as Bart said.

As another BTW, although eCos doesn't explicitly support dynamic loading,
it is possible to implement it with some magic. I have a (grossly
imperfect) module-loader as a work-in-progress. The reason I need one is
because we wish to allow developers to write add-on modules for our product
without wiping the whole OS out of flash. I seem to recall someone (Grant
Edwards?) writing about a similar need on the list some weeks ago.

=== Lewin A.R.W. Edwards (Embedded Engineer)
Work: http://www.digi-frame.com/
Personal: http://www.zws.com/ and http://www.larwe.com/

"Und setzet ihr nicht das Leben ein,
Nie wird euch das Leben gewonnen sein."

  reply	other threads:[~2001-02-20  6:17 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
2001-02-20  5:32       ` Tim Michals
2001-02-20  5:54         ` Lewin A.R.W. Edwards
2001-02-20  6:17           ` Tim Michals [this message]
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=NEBBKDICKKKKBCIKLHHKIELECJAA.tim@cygnetinc.com \
    --to=tim@cygnetinc.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=larwe@larwe.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).