Date: Fri, 14 Nov 2008 20:17:48 +0100 From: Hans Petter Selasky <hselasky@c2i.net> To: freebsd-current@freebsd.org Cc: Diego Depaoli <trebestie@gmail.com>, Coleman Kane <cokane@freebsd.org> Subject: Re: Usb2 and hal issue Message-ID: <200811142017.49692.hselasky@c2i.net> In-Reply-To: <1226687528.19638.4.camel@localhost> References: <83e5fb980811051638n5f9a1a5dr60160ed7e2ed7a1c@mail.gmail.com> <1226687528.19638.4.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
Hi Kane! Your patch will solve the CPU problem, but will otherwise not fix FreeBSD USB support under HAL. 1) Hal should use "devd" to get attach/detach events. 2) Hal should use libusb20/libusb to access USB functions and to enumerate USB devices. --HPS On Friday 14 November 2008, Coleman Kane wrote: > On Thu, 2008-11-06 at 01:38 +0100, Diego Depaoli wrote: > > Hi all, > > I don't know how provide further details, but on my system there is > > something of wrong between new usb2 drivers and hald. > > Top shows hald's cpu load at 100% while with old drivers it's 2-4%. > > I tried rebuilding hald, loading/unloading each usb2_* device but > > nothing changed, so I suspect the problem is located in usb2_core. > > I figured out the problem, and I have a solution. As the other person > mentioned, the device name has changed from "/dev/usb" into "/dev/usb > " (the space is important). However, the hald daemon doesn't use libusb > on FreeBSD. Here's a patch which tells hald to look at the new device, > apply it to the root of your ports collection. > > Additionally, I think it is a bug that hald busy-loops trying (and > failing) to open "/dev/usb". Ideally, I think that hald should put a > sleep in there of some sort, to give up CPU to something else.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200811142017.49692.hselasky>