Return-Path: Date: Tue, 10 Jun 2008 10:52:03 +0900 From: =?utf-8?B?67CV7LCs7Je0?= To: bluez-devel@lists.sourceforge.net, marcel@holtmann.org Message-id: <000a01c8ca9c$94be0850$be3a18f0$%park@samsung.com> MIME-version: 1.0 Subject: [Bluez-devel] FW: BlueZ 3.32 HSP SCO Bug Report & Solution Reply-To: BlueZ development List-Id: BlueZ development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2006278362==" Sender: bluez-devel-bounces@lists.sourceforge.net Errors-To: bluez-devel-bounces@lists.sourceforge.net ???? ?κ????? ?????? MIME ?????? ?޽????Դϴ?. --===============2006278362== Content-type: multipart/alternative; boundary="Boundary_(ID_BSiXL0mx796q0T+mQEMHWw)" Content-language: ko ???? ?κ????? ?????? MIME ?????? ?޽????Դϴ?. --Boundary_(ID_BSiXL0mx796q0T+mQEMHWw) Content-type: text/plain; charset=utf-8 Content-transfer-encoding: quoted-printable Hello. =20 >can you please check with the latest CVS.=20 >I like to know if that issue is still present or if we actually fixed = in the meantime. =20 Yes, the Latest CVS code(Rev 1.32) has still bug. =20 In sco_connect(common/glib-helper.c), BT SCO socket "sk" is made,=20 but "sk" is not delivered to transport_connect function =20 so I add =E2=80=9Cio_ctxt->fd=3Dsk (669 line)=E2=80=9D . =20 If you let me know how to commit my code on CVS, I would do. =20 =20 Regards Chan-yeol Park (=EB=B0=95=EC=B0=AC=EC=97=B4) Engineer =20 Mobile S/W Platform Lab.=20 Telecommunication R&D Center SAMSUNG ELECTRONICS CO., LTD. =20 Tel : +82-31-279-5941=20 Mobile : +82-10-9978-5941 E-mail : chanyeol.park@samsung.com =20 -----Original Message----- From: Marcel Holtmann [mailto:marcel@holtmann.org]=20 Sent: Tuesday, June 10, 2008 9:38 AM To: BlueZ development Cc: '=EB=B0=95=EC=B0=AC=EC=97=B4' Subject: Re: [Bluez-devel] BlueZ 3.32 HSP SCO Bug Report & Solution =20 Hi, =20 > Recently I found BlueZ 3.32 HSP SCO connection bug. >=20 > Fortunately I fix the bug as follows.=20 >=20 >=20 > In the function "sco_connect (glib-helper.c)" > Bluez 3.32 code doesn't handle socket variable "sk" >=20 > So I add "socket file descriptor save routine" >=20 > 636 : io_cxtf->fd=3Dsk; >=20 >=20 > If you have any question about my idea, don't hesitate to tell me ^^ >=20 > If possible , could you let me know how to check out/check in my code = ? =20 can you please check with the latest CVS. I like to know if that issue is still present or if we actually fixed in the meantime. =20 Regards =20 Marcel =20 --Boundary_(ID_BSiXL0mx796q0T+mQEMHWw) Content-type: text/html; charset=utf-8 Content-transfer-encoding: quoted-printable

Hello.

 

>can you please check with = the latest CVS.

>I like to know if that = issue is still present or if we actually fixed in the = meantime.

 

Yes, the Latest CVS code(Rev = 1.32) has still bug.

 

In = sco_connect(common/glib-helper.c), BT SCO socket "sk" is made,

but "sk" is not = delivered to transport_connect function

 

so I add = =E2=80=9Cio_ctxt->fd=3Dsk (669 line)=E2=80=9D .

 

If you let me know how to = commit my code on CVS, I would do.

 

 

Regards

Chan-yeol Park (=EB=B0=95=EC=B0=AC=EC=97=B4)

Engineer

 

Mobile S/W Platform Lab. =

Telecommunication R&D = Center

SAMSUNG ELECTRONICS CO., = LTD.

 

Tel : +82-31-279-5941 =

Mobile : = +82-10-9978-5941

E-mail : = chanyeol.park@samsung.com

 

-----Original = Message-----
From: Marcel Holtmann [mailto:marcel@holtmann.org]
Sent: Tuesday, June 10, 2008 9:38 AM
To: BlueZ development
Cc: '
=EB=B0=95=EC=B0=AC=EC=97=B4'
Subject: Re: [Bluez-devel] BlueZ 3.32 HSP SCO Bug Report & = Solution

 

Hi,

 

> Recently I found BlueZ = 3.32 HSP SCO connection bug.

>

> Fortunately I fix the = bug as follows.

>

>

> In the function = "sco_connect (glib-helper.c)"

> Bluez 3.32 code doesn't = handle socket variable "sk"

>

> So I add "socket = file descriptor save routine"

>

> 636 : = io_cxtf->fd=3Dsk;

>

>

> If you have any question = about my idea, don't hesitate to tell me ^^

>

> If possible , could you = let me know how to check out/check in my code ?

 

can you please check with the = latest CVS. I like to know if that issue

is still present or if we = actually fixed in the meantime.

 

Regards

 

Marcel

 

--Boundary_(ID_BSiXL0mx796q0T+mQEMHWw)-- --===============2006278362== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php --===============2006278362== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel --===============2006278362==--