public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: 박찬열 <chanyeol.park@samsung.com>
To: bluez-devel@lists.sourceforge.net, marcel@holtmann.org
Subject: [Bluez-devel] FW:  BlueZ 3.32 HSP SCO Bug Report & Solution
Date: Tue, 10 Jun 2008 10:52:03 +0900	[thread overview]
Message-ID: <000a01c8ca9c$94be0850$be3a18f0$%park@samsung.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1640 bytes --]

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 “io_ctxt->fd=sk (669 line)” .

 

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

 

 

Regards

Chan-yeol Park (박찬열)

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: '박찬열'
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=sk;

> 

> 

> 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

 


[-- Attachment #1.2: Type: text/html, Size: 7393 bytes --]

[-- Attachment #2: Type: text/plain, Size: 247 bytes --]

-------------------------------------------------------------------------
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

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

             reply	other threads:[~2008-06-10  1:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10  1:52 박찬열 [this message]
2008-06-10  2:51 ` [Bluez-devel] FW: BlueZ 3.32 HSP SCO Bug Report & Solution Johan Hedberg
2008-08-03  9:05   ` [Bluez-devel] AVRCP usage Paula Stanciu

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='000a01c8ca9c$94be0850$be3a18f0$%park@samsung.com' \
    --to=chanyeol.park@samsung.com \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=marcel@holtmann.org \
    /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