Date: Tue, 11 Aug 1998 14:40:42 -0700 From: Mike Smith <mike@smith.net.au> To: dmlb@ragnet.demon.co.uk Cc: Stefan Bethke <stefan@promo.de>, freebsd-hackers@FreeBSD.ORG Subject: Re: Network stack assumptions Message-ID: <199808112140.OAA01186@dingo.cdrom.com> In-Reply-To: Your message of "Tue, 11 Aug 1998 16:55:12 -0000." <199808111555.IAA02273@mailgate.cadence.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. > 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. > 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. -- \\ 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199808112140.OAA01186>