9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] port/devcons.c is not port-able
Date: Wed, 14 Jul 2004 21:14:59 +0100	[thread overview]
Message-ID: <444e999c69b8f67c65ef2ff9ce520927@terzarima.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0407141342210.9223-100000@maxroach.lanl.gov>

[-- Attachment #1: Type: text/plain, Size: 603 bytes --]

actually, although i thought it could have been better
in many ways, i didn't think USB-the-protocol was all that  bad.
the class/subclass/proto from the start was obviously going to
go the way of most global numbering systems, but the real
difficulty was the strange hardware/software interface produced
to drive it.  it was differently strange for everyone.
ambiguities in the standard as regards the nature of endpoints
didn't help.   i wonder if we ever make progress.
now, of course, it would have a SOAPy web services enabled
interface accessed by jakartatomcataxis servers in sillycon.

[-- Attachment #2: Type: message/rfc822, Size: 3263 bytes --]

From: ron minnich <rminnich@lanl.gov>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] port/devcons.c is not port-able
Date: Wed, 14 Jul 2004 13:42:53 -0600 (MDT)
Message-ID: <Pine.LNX.4.44.0407141342210.9223-100000@maxroach.lanl.gov>

On Wed, 14 Jul 2004, Dan Cross wrote:

> ron minnich <rminnich@lanl.gov> writes:
> > The keyboard-less, vga-less, serial-less nodes are all blades at this
> > point.  [[some not sold yet ]]
>
> Oo! Oo!  Do they have USB??  Okay, I'm going back into my corner now.

sadly, yes. Vendors like that usb stuff for some reason.

It makes my brain hurt, watching the gyrations of people trying to
write boot code for USB dongles.

ron

  reply	other threads:[~2004-07-14 20:14 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-13 13:57 ron minnich
2004-07-14  1:24 ` Geoff Collyer
2004-07-14  2:10   ` ron minnich
2004-07-14  2:30     ` Geoff Collyer
2004-07-14  2:47       ` ron minnich
2004-07-14  2:34     ` andrey mirtchovski
2004-07-14  2:47       ` ron minnich
2004-07-14  2:51         ` Kenji Okamoto
2004-07-14  4:40           ` Dan Cross
2004-07-14 13:33           ` OT: " Dave Lukes
2004-07-14 14:08             ` ron minnich
2004-07-14 15:31               ` Jack Johnson
2004-07-14  5:00         ` Skip Tavakkolian
2004-07-14 10:34         ` matt
2004-07-14 14:04           ` ron minnich
2004-07-14 14:04           ` Dave Lukes
2004-07-14 15:03             ` ron minnich
2004-07-14 16:13               ` boyd, rounin
2004-07-14 14:52           ` boyd, rounin
2004-07-14  2:49       ` Kenji Okamoto
2004-07-14  4:36       ` Dan Cross
2004-07-14  2:38     ` Kenji Okamoto
2004-07-14  2:49       ` ron minnich
2004-07-14  5:15         ` Geoff Collyer
2004-07-14  6:36           ` Geoff Collyer
2004-07-14 13:47           ` ron minnich
2004-07-14 18:29             ` Dan Cross
2004-07-14 18:53               ` boyd, rounin
2004-07-14 19:42               ` ron minnich
2004-07-14 20:14                 ` Charles Forsyth [this message]
2004-07-14 20:19                 ` Frank Palazzolo
2004-07-14 20:18                   ` Charles Forsyth
2004-07-14 21:06                     ` Geoff Collyer
2004-07-14 21:31                   ` boyd, rounin
2004-07-14  4:31 ` Dan Cross
     [not found] <00aba352392cbadebd943e05d1e17412@plan9.ucalgary.ca>
2004-07-15  3:14 ` Geoff Collyer

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=444e999c69b8f67c65ef2ff9ce520927@terzarima.net \
    --to=forsyth@terzarima.net \
    --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).