9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: jmk@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] bge
Date: Thu,  9 Mar 2006 14:37:46 -0500	[thread overview]
Message-ID: <682b3e41a24ef46605ea2d7c2e5582ac@plan9.bell-labs.com> (raw)
In-Reply-To: <2ffbd19d80520432d76a9698f45c7aa1@plan9.bell-labs.com>

>From the Fount of All Knowledge:

uriel     (from what I recall, there are some issues with something
          reading one byte at a time or somesuch, but I'm personally
          clueless about USB stack internals, but the people
          I have heard talk about it do have a clue)
          didn't jmk ask for testers of the damn broadcom drivers
          like months ago? /me has yet to see a single line of
          code of them... *Sigh*

I think you are referring to this:

On Fri Feb 10 23:14:07 EST 2006, jmk@plan9.bell-labs.com wrote:
> As mentioned last week, Christopher Nielsen <cnielsen@pobox.com>
> has volunteered some time to work on the 57xx driver.
> I'm expecting a laptop with a 44xx chip to arrive while
> I am away all next week. Whether I'll decide to piss myself off
> with the Atheros driver or the Broadcom driver first is up for
> grabs, send your votes in.
>
> On Fri Feb 10 22:38:41 EST 2006, lyndon@orthanc.ca wrote:
> >
> > On Feb 10, 2006, at 7:03 PM, jmk@plan9.bell-labs.com wrote:
> >
> > > Which bge, the 44xx or the 57xx?
> >
> > 57xx.  (Dell Latitude D610)

which does not ask for testers, only votes, and was less than a
month ago. Anyway, a BCM4401 driver has been written and
is being tested by others. However, in light of the following:

uriel     the live CD needs a bit of polishing, but I plan to
          merge it with the installer
          but before that comes killing 9load

I'll just hang on to it and save myself the time and trouble of
polishing it off until I can integrate it with your replacement
for 9load (if necessary). Let me know when it's ready.

--jim


  parent reply	other threads:[~2006-03-09 19:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-11  2:42 [9fans] SSH v2 Lyndon Nerenberg
2006-02-11  3:03 ` jmk
2006-02-11  3:37   ` [9fans] bge Lyndon Nerenberg
2006-02-11  4:12     ` jmk
2006-02-11  4:16       ` jmk
2006-02-11  4:23       ` Lyndon Nerenberg
2006-03-09 19:37       ` jmk [this message]
2006-03-09 19:45         ` uriel
2006-03-09 19:57           ` Russ Cox
2006-03-09 20:12             ` andrey mirtchovski
2006-03-09 21:04               ` Bruce Ellis
2006-03-09 21:18                 ` jmk
2006-03-09 23:32           ` Dan Cross
2006-03-10  6:44             ` Bruce Ellis
2006-03-10 13:41               ` Dan Cross
2006-02-11  3:10 ` [9fans] SSH v2 Russ Cox
2006-02-14  6:56   ` William Josephson

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=682b3e41a24ef46605ea2d7c2e5582ac@plan9.bell-labs.com \
    --to=jmk@plan9.bell-labs.com \
    --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).