From: Jose Goncalves <jose.goncalves@inov.pt>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Bug in compat_ppoll
Date: Fri, 07 Mar 2008 14:43:16 +0000 [thread overview]
Message-ID: <47D15484.8060607@inov.pt> (raw)
In-Reply-To: <1204899573.28006.4.camel@californication>
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 <cmd>
>>
>> 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
prev parent reply other threads:[~2008-03-07 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 16:50 [Bluez-devel] Bug in compat_ppoll Jose Goncalves
2008-03-07 14:19 ` Marcel Holtmann
2008-03-07 14:43 ` Jose Goncalves [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47D15484.8060607@inov.pt \
--to=jose.goncalves@inov.pt \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox