From: "dong yan" <semiydsemiyd@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] Bluez kernel patch for linux2.6.18?
Date: Tue, 15 Jul 2008 14:19:53 +0800 [thread overview]
Message-ID: <194c6ea30807142319n30e57bd6w348956da1ddca2f7@mail.gmail.com> (raw)
In-Reply-To: <00ec01c8e628$cc0f8a70$6e01a8c0@Raymondpc>
Hi Raymond:
Thanks for the responce.I didn't actually find any wrong
with the 2.6.18-mh8 patch.In fact im having problems when i tried to
use HSP/HFP under qtopia,which is running based on linux+bluez.Some
bluetooth headsets have disconnection failures in HSP/HFP in qtopia.So
i want to make sure that i have the latest bluez kernel patch.
I checked the location
:http://www.bluez.org/download/patches/ and comfirmed that there is
a patch for 2.6.23.But looks like there's still nowhere to find
patches for 2.6.18....
Thanks.
semiyd
2008/7/15 colorant <colorant@163.com>:
>> Hi All:
>> Im using bluez based on linux 2.6.18.Can somebody tell me
>> what is the latest version of bluez kernel patch for 2.6.18? And
>> where to get it?
>> The patch im using right now is bluez-linux2.6.18-mh8.patch ,
>> downloaded from the old bluez website one year ago.But i can't find
>> any patch for kernel in the new bluez website.I want to know if im
>> using the latest version of bluez kernel patch....btw,i won't be able
>> to upgrade the version of the kernel because my boss doesn't allow me
>> to do so.Otherwise maybe i won't be needing such a patch:[.......
>> Thanks!
>>
>> semiyd
>
> Hi Semiyd
> Did you find anything wrong with this patch ?
> I think the recent patch on new kernel version is just to add features, you
> might not really need them.
> And actually there are a download page for kernel patchs at:
> http://www.bluez.org/download/patches/ however it's for 2.6.23
> seems their server crashed a few weeks ago, and lot of thing lost.
>
> Raymond
>
>
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
prev parent reply other threads:[~2008-07-15 6:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 2:58 [Bluez-users] Bluez kernel patch for linux2.6.18? dong yan
2008-07-15 3:13 ` colorant
2008-07-15 6:19 ` dong yan [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=194c6ea30807142319n30e57bd6w348956da1ddca2f7@mail.gmail.com \
--to=semiydsemiyd@gmail.com \
--cc=bluez-users@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