From owner-freebsd-wireless@FreeBSD.ORG Tue Apr 10 06:21:44 2012 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D4B1E106566B; Tue, 10 Apr 2012 06:21:44 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 69EA58FC0A; Tue, 10 Apr 2012 06:21:44 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (89.112.15.178.pppoe.eltel.net [89.112.15.178]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 3EAFE4AC1C; Tue, 10 Apr 2012 10:21:43 +0400 (MSK) Date: Tue, 10 Apr 2012 10:21:40 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <973223342.20120410102140@serebryakov.spb.ru> To: PseudoCylon In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=windows-874 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org, Bernhard Schmidt Subject: Re: Intel 6250 and WiMax X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Apr 2012 06:21:44 -0000 Hello, PseudoCylon. You wrote 10 ?????? 2012 ?., 5:55:06: >> It looks like Samsung USB stick contains stack in firmware, because >> driver is VERY simple and has size of several KILOBYTES of C code, >> really, only couple of USB commands like "set SSID", "get signal >> strength", "send frame" and "poll for received frame", and it's all. >> > It wasn't particularly WiMax, but when I worked on HSPA+ device, > usie(4) it worked like that, set up usb xfers and throw ethernet > packets at the device, that was it. Probably, one simple generic stack > would work for most of them if needed. > The problem I had was there is no mechanism to pass device info (i.e > link state up/down, signal strength, IP addresses) to other part of > the system. I thought about adding it, but I haven't because there > isn't lots of demand. WiMax driver senses "up/down" state and IP is assigned by generic base-system dhclinet :) --=20 // Black Lion AKA Lev Serebryakov