From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <47D15484.8060607@inov.pt> Date: Fri, 07 Mar 2008 14:43:16 +0000 From: Jose Goncalves MIME-Version: 1.0 To: BlueZ development References: <47D020D1.9020204@inov.pt> <1204899573.28006.4.camel@californication> In-Reply-To: <1204899573.28006.4.camel@californication> Subject: Re: [Bluez-devel] Bug in compat_ppoll Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net Marcel Holtmann wrote: > Hi Jose, > > = >> When I was cross-compiling Bluez for a system without the ppoll() system >> call, I've found a bug on you ppoll() stub, compat_ppoll(), that causes >> rfcomm to eat all CPU power when called in this way: >> >> $ rfcomm listen 0 1 >> >> After the RFCOMM connection is established and the command is executed >> the CPU load reaches 100%. >> >> This patch solved my problem: >> = > > your patch has been applied. Thanks. > > I was actually considering to simply fail compilation on systems that > don't support ppoll(). > > = I don't think that is such a good idea because there are still several embedded systems that use an old Linux kernel or an old Glibc (that's my case, I'm using Glibc 2.3.6 on my board). Regards, Jos=E9 Miguel Gon=E7alves ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel