From owner-freebsd-hackers Tue Aug 11 18:06:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA14570 for freebsd-hackers-outgoing; Tue, 11 Aug 1998 18:06:44 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from post.mail.demon.net (post-12.mail.demon.net [194.217.242.41]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA14549 for ; Tue, 11 Aug 1998 18:06:38 -0700 (PDT) (envelope-from dmlb@ragnet.demon.co.uk) Received: from (ragnet.demon.co.uk) [158.152.46.40] by post.mail.demon.net with smtp (Exim 1.82 #2) id 0z6PMc-0003Co-00; Wed, 12 Aug 1998 01:06:07 +0000 Received: from dmlb by ragnet.demon.co.uk with local (Exim 1.82 #1) id 0z6O5u-0004EF-00; Wed, 12 Aug 1998 00:44:46 +0100 Message-ID: X-Mailer: XFMail 1.2 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199808112140.OAA01186@dingo.cdrom.com> Date: Wed, 12 Aug 1998 00:44:46 +0100 (BST) From: Duncan Barclay To: Mike Smith Subject: Re: Network stack assumptions Cc: freebsd-hackers@FreeBSD.ORG, Stefan Bethke Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 11-Aug-98 Mike Smith wrote: >> Okay, can the kernel cope with a device hanging off a USB port or >> integrated into the motherboard or a PCI card which provides wireless >> LAN capabilities with mutliple protocols running on it? > > Not as it stands, no. By this I mean that we have no protocol support > for these devices, however the infrastructure is there to handle this. Good, I brought it up as there was a section in the SWAP spec. where mumble company said their new OS doesn't have this capability. >> Asynchronous data is 802.11 style, isochronous data is DECT sytle for >> SWAP, can't remember the protocols for Bluetooth. They will support a >> number of concurrent voice calls between handsets/apps software on >> your PC along with LAN activity (i.e. wireless printing from your >> laptop). > > We would need extra code to handle these protocols. Sure, I don't know how the voice stuff is meant to work from the point of view of a computer as one end of a call. >> In some instances the FreeBSD box will have to be a some form of >> controller which manages the routing of the network. >> >> [tutorial snipped]. Sorry, I meant the device driver and network >> stack framework! > > Device drivers, no. Networking infrastructure, yes. Well as the spec. isn't finished for SWAP no has anything anyway, Bluetooth is a bit different as there is a complete spec. from one of the core companies, but this is likely to change as more people get involved. These technologies aren't going to hit the streets for a couple of years yet and as they are literally industry standards who knows how "Open" they will be. Lets hope that we don't get into an I2O situtation. Duncan > -- > \\ Sometimes you're ahead, \\ Mike Smith > \\ sometimes you're behind. \\ mike@smith.net.au > \\ The race is long, and in the \\ msmith@freebsd.org > \\ end it's only with yourself. \\ msmith@cdrom.com > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message --- ________________________________________________________________________ Duncan Barclay | God smiles upon the little children, dmlb@ragnet.demon.co.uk | the alcoholics, and the permanently stoned. ________________________________________________________________________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message