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

> >What's your flash/ROM budget
>4M of ROM and 8M RAM.

Ow. If it's really ROM and not flash, and you have no rewritable 
non-volatile storage, then you're in trouble and my feeling is that a 
rethink is in order. You won't be able to update your drivers without a ROM 
swap (which is doable, of course, but _expensive_).

If your only aim is to add wireless support for some specific protocol, it 
will be _so_ much easier to buy a prefab wireless module.

The memory budget isn't impossible for embedded Linux, but I'm no expert on 
it so I'll bow out in favor of those who are. The only distribution I've 
played with for a reasonable length of time is ucLinux. Whichever 
distribution you go with will be tempered strongly by your host CPU (you 
only mentioned that it's an ARM; did you really mean StrongARM [seems 
plausible given the talk of host-side USB]). You might want to look at 
Royal Linux (I've installed it once, haven't played with it much; I only 
mention it because I know it supports ARM).

>Ethernet-to-wireless-flavor-of-the-month adapter. My experience as a
>consumer of a couple of appliances with host-side USB is that the
>instruction manual says "You can use the USB ports to plug in a mouse or
>
>So you have done this?

Have we done what? I mention above that I have bought/owned a couple of 
appliances (set-top box, Internet appliance) that had host-side USB, and it 
went the way you might expect - too much engineering cost to support 
additional peripherals, so it's just a decorative hole in the box.

As for our own products, we decided that wireless is too infant and 
non-standardized right now. Also it is not an accepted standard in the way 
that Ethernet is. We don't want to tell our users to buy any specific piece 
of wireless hardware in order to talk to us, so we went with the lowest 
common denominator: Ethernet on the appliance, and if they want wireless 
they gate it themselves. At worst the user has to buy a $5 Ethernet card to 
talk to us.

This approach also reduces the ongoing support issues greatly; a big 
consideration for us.

=== 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 10:11 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
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 [this message]
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=4.3.2.7.2.20010220130140.00b65570@larwe.com \
    --to=larwe@larwe.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).