From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tristan <9p-st@imu.li> To: <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Message-Id: <2579c7.b6c4656c.fWVN.mx@tumtum.plumbweb.net> In-Reply-To: <2579c7.a4dbcdb6.srLn.mx@tumtum.plumbweb.net> References: <2579c7.a4dbcdb6.srLn.mx@tumtum.plumbweb.net> Date: Wed, 21 Mar 2012 01:43:47 -0400 User-Agent: mx-alpha Content-Transfer-Encoding: quoted-printable Subject: [9fans] wifi interface Topicbox-Message-UUID: 6c92ca42-ead7-11e9-9d60-3106f5b1d025 > 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 --=20 All original matter is hereby placed immediately under the public domain.