On Tue, Jul 31, 2012 at 11:27:50PM -0400, Lwazi Dube wrote: > On Tue, Jul 31, 2012 at 10:07 AM, Jason McIntyre <j...@kerhand.co.uk> wrote: > > On Mon, Jul 23, 2012 at 09:41:43PM +0200, Eivind Evensen wrote: > >> The umct(4) man page states: > >> > >> > BUGS > >> > This driver is not known to work currently. If someone does > >> > discover > >> > that it is working, please report this. > >> > >> I see that this message was added in 2002 according to cvs ann, but in > >> case it's of interest, the device from the dmesg below works mostly. > >> The only thing I've noticed doesn't work is sending a break with ~# in cu. > >> At least I haven't been able to get the machine into ddb using it. > >> > > > > if no one objects, i'll remove the BUGS entry after the tree unlocks. > > jmc > > > > The last time I checked (5.0) the driver was broken for the two Belkin > F5U409 devices that I tried. > Receive worked but transmit was broken. I could not send anything out. >
ho hum. in that case maybe i won;t remove the BUGS entry - just the line asking people to report whether it works. and if some developer gets round to working on it, it could eventually be removed. let us know if you get a chance to try these on a more recent version of obsd. jmc
