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] Writing device drivers
Date: Sat, 15 Apr 2006 00:58:38 -0400	[thread overview]
Message-ID: <dac558da83c93993e9348a8034788e85@plan9.bell-labs.com> (raw)
In-Reply-To: <820bc1260604140836p4ba0baby9b9ef3d081d2fb51@mail.gmail.com>

Brantley's comments are pretty much on the mark.
However, I'd try something simpler than the WPN311
to start with. I think it uses the Atheros 5212
chip and I looked at writing a driver for that a
few weeks ago and decided it was probably more man
years than I had available. On the other hand, we
need to be able to use some newer wireless hardware
than the old Wavelan 802.11b chips. If you have
access to a system with an Intel Centrino wireless
chip there is a partial driver available which
needs someone to finish and debug. That's if you
are set on doing wireless; otherwise there are
many simpler projects you could usefully do and
I'm sure the list could suggest some if you were
interested in alternatives. In any case, be assured
we welcome your enthusiasm and are happy to help
with any questions you may have.

--jim


  parent reply	other threads:[~2006-04-15  4:58 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8a5bd8ccbc2e53557663e2a9020fb26c@coraid.com>
     [not found] ` <820bc1260604140834v2a773ev90ff46b4e6b2427f@mail.gmail.com>
2006-04-14 15:36   ` Eric Smith
2006-04-14 19:33     ` David Leimbach
2006-04-15  4:58     ` jmk [this message]
2006-04-15 13:24       ` Eric Smith
2006-04-15 14:16         ` Anthony Sorace
2006-04-16 23:00           ` Paweł Lasek
2006-04-19  3:10 erik quanstrom
2006-04-19  4:02 ` jmk
2006-04-19  4:57   ` lucio
2006-04-19  6:59   ` Nigel Roles
2006-04-19 21:12   ` quanstro
  -- strict thread matches above, loose matches on Subject: below --
2006-04-17  0:31 erik quanstrom
2006-04-17  1:44 ` Russ Cox
2006-04-17 10:01   ` Nigel Roles
2006-04-18  1:34     ` erik quanstrom
2006-04-18 14:49       ` Nigel Roles
2006-04-18 15:42         ` jmk
2006-04-18 15:59         ` Moritz Kiese
2006-04-18 16:03           ` Nigel Roles
2006-04-18 19:15       ` Paweł Lasek
2006-04-17  0:11 erik quanstrom
2006-04-17  1:24 ` Russ Cox
2006-04-16  1:02 erik quanstrom
2006-04-16  2:36 ` Anthony Sorace
2006-04-16  8:06   ` Bruce Ellis
2006-04-15 23:34 erik quanstrom
2006-04-15 23:55 ` Skip Tavakkolian
2006-04-15 15:26 erik quanstrom
2006-04-15 23:04 ` Federico Benavento
2006-04-15 23:18   ` Skip Tavakkolian
2006-04-16  0:43     ` Federico G. Benavento
2006-04-16 18:03     ` Charles Forsyth
2006-04-16 18:14       ` Bruce Ellis
2006-04-16 21:31         ` Charles Forsyth
2006-04-14  3:20 Eric Smith

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=dac558da83c93993e9348a8034788e85@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).