Date: Thu, 20 Nov 2003 09:20:06 +0100 From: des@des.no (Dag-Erling =?iso-8859-1?q?Sm=F8rgrav?=) To: "Brian F. Feldman" <green@FreeBSD.org> Cc: current@FreeBSD.org Subject: Re: kernel panic trying to utilize a da(4)/umass(4) device with ohci(4) Message-ID: <xzpoev7moy1.fsf@dwp.des.no> In-Reply-To: <200311200326.hAK3Qqvf024651@green.bikeshed.org> (Brian F. Feldman's message of "Wed, 19 Nov 2003 22:26:51 -0500") References: <200311200326.hAK3Qqvf024651@green.bikeshed.org>
next in thread | previous in thread | raw e-mail | index | archive | help
"Brian F. Feldman" <green@FreeBSD.org> writes: > Jeez, it's been broken a year and it's almost 5.2-RELEASE now. Does anyo= ne=20 > have ANY leads on these problems? I know precisely nothing about how my = USB=20 > hardware is supposed to work, but this OHCI+EHCI stuff definitely doesn't= ,=20 > and it's really not uncommon at all. Is it unbroken in NetBSD currently? *shrug* I have never been able to get my USB printer to work with FreeBSD, and I gave up writing drivers for USB crypto tokens because the USB drivers were too broken (reading any amount of data from the ugen device returns garbage with no error message and no indication of the actual amount of data obtained from the device). Neither could I get anybody with USB clue interested in the problem long enough to actually try to fix it. In conclusion, I simply don't consider FreeBSD's USB support usable for anything more complex than mice and keyboards. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzpoev7moy1.fsf>