public inbox for ecos-devel@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Frank Pagliughi <fpagliughi@mindspring.com>
Cc: eCos Devel <ecos-devel@ecos.sourceware.org>
Subject: Re: "usbhid-ups" programing problem...
Date: Thu, 01 May 2008 18:24:00 -0000	[thread overview]
Message-ID: <20080501182411.GG14773@lunn.ch> (raw)
In-Reply-To: <4819FC43.5000905@mindspring.com>

> Most of the recent chips that I've seen appear to have a control  
> endpoint and some number of fairly generic endpoints. Combining the  
> usbs_rx_endpoint and usbs_tx_endpoint into a single thing  
> (usbs_endpoint), adding an endpoint number and direction, and things  
> like that would be helpful. I could make a list.

The AT91 USB driver already does that to some extent.

> Many of the ideas could break the existing USBS drivers. Would this be OK?

Sorry, no. 

However you can add a new USB package parallel to the existing
one. That is the nice thing about the package system.

> A common code base for USB drivers might be really helpful.   I could do  
> this work, but would it be accepted?

Sure, so long as the assignment is in place so we can accept it.

      Andrew

      reply	other threads:[~2008-05-01 18:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-30 12:16 Michelle Konzack
2008-05-01 10:04 ` Andrew Lunn
2008-05-01 15:38   ` Frank Pagliughi
2008-05-09 12:36     ` Michelle Konzack
     [not found]   ` <4819DEFF.2040007@mindspring.com>
2008-05-01 15:52     ` Andrew Lunn
2008-05-01 15:57       ` Gary Thomas
2008-05-01 16:01         ` Andrew Lunn
2008-05-01 17:22       ` Frank Pagliughi
2008-05-01 18:24         ` Andrew Lunn [this message]

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=20080501182411.GG14773@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=ecos-devel@ecos.sourceware.org \
    --cc=fpagliughi@mindspring.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).