public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: "Lewin A.R.W. Edwards" <larwe@larwe.com>
To: "Nick - eCos Developer" <n_ecos@steve.targus.net>,
	"Ecos - Discuss" <ecos-discuss@sourceware.cygnus.com>
Subject: Re: [ECOS] USB Device support
Date: Wed, 17 Jan 2001 12:33:00 -0000	[thread overview]
Message-ID: <4.3.2.7.2.20010117153013.00afebf0@larwe.com> (raw)
In-Reply-To: <00f301c080c2$995be0c0$7f00a8c0@domain.targus.net>

>I saw a few posts a while back from people working on drivers for the
>Phillips USB interface device, PDIUSBD12. Note that this is not a USB host
>controller. Has anyone got a working driver of any sort for this chip?

What type of drivers are you talking about? For USB, the drivers on the 
host end are the complex hassle, or that has been my experience anyway. 
Once you can work out how to get the host to squirt data, interfacing to 
the parallel type USB appliance-end ICs is pretty simple.

We have chosen to use a USB to RS232 solution for our USB product, because 
it can be boilerplated into our design, and I am trying to get the USB port 
totally eliminated off the product if possible. So much hassle to support 
it with all the different Windows and MacOS flavors and idiosyncratic host 
controller ICs out there.

=== 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-01-17 12:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-17 12:22 Nick - eCos Developer
2001-01-17 12:33 ` Lewin A.R.W. Edwards [this message]
2001-01-18  1:14   ` Charles-Henri
2001-01-17 13:30 ` Bart Veer
2001-01-18  4:12 Siegfried Schaefer

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.20010117153013.00afebf0@larwe.com \
    --to=larwe@larwe.com \
    --cc=ecos-discuss@sourceware.cygnus.com \
    --cc=n_ecos@steve.targus.net \
    /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).