9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fco.J.Ballesteros <nemo@plan9.escet.urjc.es>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] keyboard maps
Date: Mon, 17 Nov 2003 19:41:30 +0100	[thread overview]
Message-ID: <cd4a677b7bdb8b17b346640b2e6c579c@plan9.escet.urjc.es> (raw)
In-Reply-To: <Pine.LNX.4.44.0311171132580.6311-100000@maxroach.lanl.gov>

> this work you are doing with user-level USB is really interesting. It will
> be neat if this turns into "usb outside the kernel" given the amazing
> error-prone lockup nature of the usb chipsets we've seen. Supposing we can
> push all this USB crud into user procs, do you think we'll be able to suck
> up USB 2.0 at reasonable rates?

I've only done a HID driver, all of the usb code was already there, and
btw, all of the configuration is in usbd outside the kernel. The kernel seems
to configure (almost) the bare minimum in usb(3).

I'd like to keep the usb stack outside the kernel just while seeing errors;
once it gets stable, I don't know if I wouldnt want to put it all back in the kernel
just to avoid complexity (more file systems, more binds, more levels of
indirection, etc.).

Regarding 2.0, I'm in the mood of using usb for almost any new piece of hw
we buy that is not integrated inside the PC. This means that sooner or later
we'll have usb 2.0, it depends on who needs this earlier, if we or other 9fans.



  reply	other threads:[~2003-11-17 18:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-17 18:24 Fco.J.Ballesteros
2003-11-17 18:34 ` ron minnich
2003-11-17 18:41   ` Fco.J.Ballesteros [this message]
2003-11-17 19:56 ` mirtchov
2003-11-18  8:13   ` Fco.J.Ballesteros
  -- strict thread matches above, loose matches on Subject: below --
2005-11-01 21:48 Heiko Dudzus
2005-11-01 22:34 ` Russ Cox
2005-11-02 19:49   ` Heiko Dudzus
2004-03-16 14:31 David Presotto
2002-05-20  9:55 Joel Salomon
2002-05-21  8:47 ` Joel Salomon
2002-05-16 13:18 rob pike, esq.
2002-05-16 11:06 nigel
2002-05-16 10:00 Fco.J.Ballesteros
2002-05-14 21:36 rob pike, esq.
2002-05-14 20:15 rob pike, esq.
2002-05-14 19:40 andrey mirtchovski
2002-05-14 18:50 andrey mirtchovski
2002-05-14 17:37 Fco.J.Ballesteros
2002-05-15  9:05 ` Boyd Roberts
2002-05-15 21:34 ` Pavel Mihaylov
2002-05-16 10:02   ` Boyd Roberts
2002-05-18 19:57     ` Pavel Mihaylov
2002-05-21 10:43       ` Boyd Roberts
2002-05-21 11:35         ` Pavel Mihaylov

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=cd4a677b7bdb8b17b346640b2e6c579c@plan9.escet.urjc.es \
    --to=nemo@plan9.escet.urjc.es \
    --cc=9fans@cse.psu.edu \
    /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 NNTP newsgroup(s).