public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: mike <mikelee@avantwave.com>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] About rfcomm socket
Date: Tue, 07 Dec 2004 17:13:58 +0800	[thread overview]
Message-ID: <41B57456.3080103@avantwave.com> (raw)
In-Reply-To: <1102342812.9644.26.camel@pegasus>

Dear Marcel
    After i make install bluez-lib-2.12 , i found that there is no sdp 
lib. Does it combine to bluetooth lib? or i need to enable it in 
configuration.

Best Regard
Mike,Lee

Marcel Holtmann wrote:

>Hi Mike,
>
>  
>
>>   You mean that i can patch the 2.4 to 2.6? from kernel.org?
>>    
>>
>
>no. You already use the newest Bluetooth subsystem available for 2.4 and
>if you wanna use the Bluetooth subsystem of 2.6, you have to backport
>over 30 patches. It is a doable job, but not an easy one.
>
>Regards
>
>Marcel
>
>
>
>
>-------------------------------------------------------
>SF email is sponsored by - The IT Product Guide
>Read honest & candid reviews on hundreds of IT Products from real users.
>Discover which products truly live up to the hype. Start reading now. 
>http://productguide.itmanagersjournal.com/
>_______________________________________________
>Bluez-devel mailing list
>Bluez-devel@lists.sourceforge.net
>https://lists.sourceforge.net/lists/listinfo/bluez-devel
>
>  
>




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  parent reply	other threads:[~2004-12-07  9:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-01  2:25 [Bluez-devel] About rfcomm socket mike
2004-12-01  6:28 ` Marcel Holtmann
2004-12-01  8:53   ` [Bluez-users] " mike
2004-12-01  9:48     ` Marcel Holtmann
2004-12-02  4:26       ` mike
2004-12-02  7:44         ` Marcel Holtmann
2004-12-03  3:16           ` mike
2004-12-03  3:15             ` Marcel Holtmann
2004-12-06  7:37               ` mike
2004-12-06  7:38                 ` Marcel Holtmann
2004-12-06 11:29                   ` mike
2004-12-06 11:27                     ` Marcel Holtmann
2004-12-06 13:17                       ` Mike Lee
2004-12-06 13:27                         ` Marcel Holtmann
2004-12-06 14:04                           ` Mike Lee
2004-12-06 14:20                             ` Marcel Holtmann
2004-12-06 14:47                               ` Mike Lee
2004-12-06 15:41                                 ` Marcel Holtmann
2004-12-07  9:13                               ` mike [this message]
2004-12-07  9:10                                 ` [Bluez-devel] " Sebastian Roth
2004-12-07  9:18                                 ` [Bluez-devel] " Marcel Holtmann

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=41B57456.3080103@avantwave.com \
    --to=mikelee@avantwave.com \
    --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