From: Tristan <9p-st@imu.li>
To: <9fans@9fans.net>
Subject: [9fans] wifi interface
Date: Wed, 21 Mar 2012 01:43:47 -0400 [thread overview]
Message-ID: <2579c7.b6c4656c.fWVN.mx@tumtum.plumbweb.net> (raw)
In-Reply-To: <2579c7.a4dbcdb6.srLn.mx@tumtum.plumbweb.net>
> USB: Marvell 88W8388 aka olpc (probably not what you're looking for)
oh, and on that note:
said wireless driver is much nicer now (though far from perfect or
complete) and still in contrib/tristan/libertas.tgz.
the wavelan driver uses the ctl file in the connection (`{cat clone}/ctl)
to manage association and such (if i'm understanding correctly). i find
that fairly annoying to use and generally unintuitive.
i'm inclined to extend the ethernet interface an etherx/ctl file that
accepted commands along the lines of ssid, bssid, and channel to
configure the connection. did the wavelan driver not do this for a reason
beyond changing devether? any better ideas?
my guess is that the strongest argument against that is that wavelan does
it the other way and consistancy is important.
enjoy,
tristan
--
All original matter is hereby placed immediately under the public domain.
next prev parent reply other threads:[~2012-03-21 5:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-21 3:12 [9fans] known working wifi cards Stanley Lieber
2012-03-21 3:40 ` Tristan
2012-03-21 5:43 ` Tristan [this message]
2012-03-21 6:15 ` [9fans] wifi interface erik quanstrom
2012-03-21 7:01 ` Tristan
2012-03-21 7:03 ` erik quanstrom
2012-03-21 15:42 ` [9fans] known working wifi cards Richard Miller
2012-03-21 15:47 ` Stanley Lieber
2012-03-21 16:02 ` Richard Miller
2012-03-21 16:10 ` Stanley Lieber
2012-03-21 20:08 ` Jerome Ibanes
2012-03-22 13:59 ` Ethan Grammatikidis
2012-03-22 15:44 ` Gorka Guardiola
2012-03-22 17:51 ` Skip Tavakkolian
2012-03-23 9:51 ` Balwinder S Dheeman
2012-03-23 9:51 ` Balwinder S Dheeman
2012-03-23 21:26 ` Ethan Grammatikidis
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=2579c7.b6c4656c.fWVN.mx@tumtum.plumbweb.net \
--to=9p-st@imu.li \
--cc=9fans@9fans.net \
/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).