Return-Path: In-Reply-To: To: bluez-devel@lists.sourceforge.net Subject: RE: [Bluez-devel] HCI-Uart Driver & Kernel 2.4.25 , Headset/Handsfree Profile MIME-Version: 1.0 Message-ID: From: gao.yingbin@zte.com.cn Content-Type: multipart/alternative; boundary="=_alternative 00334A4B48257004_=" Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net Reply-To: bluez-devel@lists.sourceforge.net List-Unsubscribe: , List-Id: BlueZ development List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 17 May 2005 17:26:44 +0800 This is a multipart message in MIME format. --=_alternative 00334A4B48257004_= Content-Type: text/plain; charset="US-ASCII" I have faced this problem when I debug my applications over bluez kernel,on embedded OS. Everytimes I turned on the macro "CONFIG_BLUEZ_DEBUG" to display the debug information and compiled, when bluez was running ,and other device was connected to it, the following erro appeared: ............ h4_recv: Unknown HCI packet type 05 h4_recv: Unknown HCI packet type 00 ............ and the connection was failed. maybe try it again, the connection could finish. However, When I turned on the macro "CONFIG_BLUEZ_DEBUG", the connection always finished very well, so I didn't mind the problem any more. I think there are some little bugs in the HCI uart driver, which affect the application of bluez on embedded linux OS. *********************************************** 信息安全声明：本邮件包含信息归ZTE所有， ZTE对该邮件拥有所有权利。请接收者注意 保密，未经发件人书面许可，不得向任何第 三方组织和个人透露本邮件所含信息的全部 或部分。以上声明仅适用于工作邮件。 Information Security Notice： The information contained in this mail is solely property of ZTE Corporation. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others. *********************************************** --=_alternative 00334A4B48257004_= Content-Type: text/html; charset="US-ASCII"
I have faced this problem when I debug my applications over bluez kernel,on embedded OS. Everytimes I turned on the macro "CONFIG_BLUEZ_DEBUG" to display the debug information and compiled, when bluez was running ,and  other device was connected to it, the following erro appeared:
............
h4_recv: Unknown HCI packet type 05  
h4_recv: Unknown HCI packet type 00  
............
and the connection was failed. maybe try it again, the connection could finish.

However, When I turned on the macro "CONFIG_BLUEZ_DEBUG", the connection always finished very well, so I didn't mind the problem any more. I think there are some little bugs in the HCI uart driver, which affect the application of bluez on embedded linux OS.
 


***********************************************
信息安全声明：本邮件包含信息归ZTE所有，
ZTE对该邮件拥有所有权利。请接收者注意
保密，未经发件人书面许可，不得向任何第
三方组织和个人透露本邮件所含信息的全部
或部分。以上声明仅适用于工作邮件。
Information Security  Notice：
The information contained in this mail is
solely property of  ZTE Corporation. 
This mail communication is confidential.
Recipients named above are obligated to
maintain secrecy and are not permitted to
disclose the contents of this communication
to others.
***********************************************
--=_alternative 00334A4B48257004_=-- ------------------------------------------------------- This SF.Net email is sponsored by Oracle Space Sweepstakes Want to be the first software developer in space? Enter now for the Oracle Space Sweepstakes! http://ads.osdn.com/?ad_id=7412&alloc_id=16344&op=click _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel