9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: uriel@cat-v.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Status of 3C589D driver (and BCM57XX)
Date: Fri,  3 Feb 2006 15:20:21 +0100	[thread overview]
Message-ID: <bd02145d2333e675db7aa4b068690c3d@cat-v.org> (raw)
In-Reply-To: <e256117032b3615cb9e60f3b4903d9ed@coraid.com>

When will people learn that to hope that people will ask about code
they don't even know that exists just doesn't work.  And much less
will get it fixed or improved.

Unless we change this tradition of keeping all development as secret
and closed as possible(unless someone by chance happens to ask the
right question in 9fans or privately), Plan 9 is doomed.

Russ did the right thing already when he put his half finished
centrino driver in sources and even announced it in 9fans, many kudos
to him.  Maybe the driver never gets finished, but the chances of it
being finished are about a billion times higher than if he had let it
rot in a corner of his hardisk.

Open source might produce tons of crap, but it is the only hope if
Plan 9 is going to survive.

And I would also love to test the BCM57XX driver.

uriel


> We would LOVE to test it!
>
>>===> 2/ (message/rfc822) [inline]
>>Date: Thu, 2 Feb 2006 18:57:35 -0800
>>From: Christopher Nielsen <cnielsen@pobox.com>
>>To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
>>Subject: Re: [9fans] Status of 3C589D driver (and BCM57XX)
>>
>>On 2/2/06, Lyndon Nerenberg <lyndon@orthanc.ca> wrote:
>>> I have started examining the FreeBSD bge driver in the hope it will make the
>>> basis for a driver port.  (Anyone out there have a pointer to
>>> hardware doc for the 57XX series?  I've looked in the obvious places
>>> but can't find anything.)
>>
>>the only docs for the BCM57XX family are the open source drivers.
>>jmk has sent me what he started on for a driver, and he and i are
>>actively working on a driver for the broadcom chips. he has hardware
>>to tes it, and i have time to write it. if you'd like to be a tester,
>>that would be helpful.



  reply	other threads:[~2006-02-03 14:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-03  2:43 Lyndon Nerenberg
2006-02-03  2:57 ` Christopher Nielsen
2006-02-03  3:12   ` Lyndon Nerenberg
2006-02-03 13:30   ` Brantley Coile
2006-02-03 14:20     ` uriel [this message]
2006-02-03 14:24       ` Dan Cross
2006-03-02 16:08   ` Gabriel Diaz
2006-02-03  3:23 ` jmk
2006-02-03 10:13 ` Martin Neubauer
2006-02-03 16:02   ` jmk

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=bd02145d2333e675db7aa4b068690c3d@cat-v.org \
    --to=uriel@cat-v.org \
    --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).