Date: Thu, 31 Mar 2005 14:30:08 +0200 From: Bernd Walter <ticso@cicely12.cicely.de> To: Richard Caley <rjc@interactive.co.uk> Cc: freebsd-usb@freebsd.org Subject: Re: USB Modems Message-ID: <20050331123008.GC2072@cicely12.cicely.de> In-Reply-To: <200503311136.j2VBaGI6014363@pele.r.caley.org.uk> References: <200503311136.j2VBaGI6014363@pele.r.caley.org.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, Mar 31, 2005 at 12:36:16PM +0100, Richard Caley wrote: > > > I want to add a USB modem to a FreeBSD 5.* machine. > > So, I built a kernel with ucom and umodem in it. > > I have tried one I bought a while ago for use with windows, it is > identified as STMicroelectronics Communicator and gets set up as > ugen0. I thought I should get a ucom or umodem device? > > Is this a dead end? I notice that this device name is in the usbdevs > file in the source, so maybe someone has done something with it > somewhere? There is only one product in the little table in umodem.c > so maybe this is just not a useful driver and I should be looking > somewhere lese, but I can't spot any clues. umodem should take every device that claims to be compatible with umodem AT class protocol specification. I don't think it makes much sense to build a tty without AT command set. Unfortunately vendors don't tell anything about the protocols they use. First chance to find out is by connecting the device and ask it. A more up to date list of known good devices in the manpage would be great. I think the exceptional device is umodem conform but to stupid to tell. -- B.Walter BWCT http://www.bwct.de bernd@bwct.de info@bwct.de
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050331123008.GC2072>