linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Young Tae Kim <ytkim@qca.qualcomm.com>
To: Chanyeol Park <chanyeol.park@gmail.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	<linux-bluetooth@vger.kernel.org>,
	"Kim, Ben Young Tae" <ytkim@qca.qualcomm.com>
Subject: Re: [PATCH] Bluetooth: btusb: Support for QCA61x4 on Samsung
Date: Wed, 20 May 2015 17:45:02 -0700	[thread overview]
Message-ID: <555D2A8E.7040805@qca.qualcomm.com> (raw)
In-Reply-To: <1432168603.2474.20.camel@gmail.com>

Hi Chanyeol,

On 05/20/15 17:36, Chanyeol Park wrote:
> Hi,Ben Kim
>
> On Wed, 2015-05-20 at 10:54 -0700, Ben Young Tae Kim wrote:
>> Hi Chan-yeol,
>>
>> On 05/20/15 05:44, Chan-yeol Park wrote:
>>> Hi Marcel,
>>>
>>> On 05/20/2015 09:35 PM, Chan-yeol Park wrote:
>>>> Hi Marcel,
>>>> On 05/20/2015 03:21 AM, Marcel Holtmann wrote:
>>>>> Hi Chan-yeol,
>>>>>> The previous commit(3267c88) regressed QCA61x4 BT on Samsung 
>>>>>> because its device info is missed in qca_devices_table[], so 
>>>>>> btusb_open() return error unexpectedly.
>>>>> how does this regress. We never had QCA module support in the 
>>>>> first place. The patch looks good, I was just wondering what 
>>>>> the regression will be here?
>>>> My environment was virtual box on windows.
>>>> I guess windows download QC firmware successfully, so without 
>>>> firmware handling in the linux I could use bluetooth adapter.
>>>>
>> I didn't realize ROME v2.0 was out to the market. Where did you get 
>> this module? Does it built-in on your laptop?
> Yes. It's built-in in my Samsung labtop bought on market.
>
>> Your patch looks good, however, I need your confirmation that it will 
>> work on your board since I don't have ROME v2.0 HW. I'll send you 
>> ROME v2.0 FW files for you and will upstream it to linux-firmware.git 
>> if it works.
> It works well. I test basic things such as searching, sdp, and pairing.
> and they works fine.
>
> Actually before I use your driver/firmware, my "hciconfig -a" shows
> wrong address and hci 4.0. but thanks to your driver/firmware I could
> get hci 4.1 and normal address.
>>  
>>>> Until now , I fail to find the exact firmware , 
>>>> "qca/rampatch_usb_*.bin" for QCA61x4.
>>>> I just saw the mail that Kyle McMartin reject firmware patches 
>>>> made by Ben Young Tae Kim.
>>>> Could you tell where I can get it?
>>>>
>>>> Actually my wifi QCA61x4 does not work well..
>> QCA61x4 WiFi will use 'ATH10k' driver. Did you enable this module 
>> compiled on your kernel tree
> No. I just use fedora 22, 4.0.3-300.fc22.x86_64. In case of wifi they
> use PCI, so it's not easy to use it in guest os that use latest kernel
> tree.
>
> Also I search some mail thread for ath10k, it seems that firmware is
> not added in linux-firmware until now.
>>> I am sending this mail again because previous mail is not sent to 
>>> bluetooth-next due to HTML format.
>>>
>>> Thanks
>>> Chanyeol
>>>
>> Thanks
>> -- Ben Kim
> I appreciate your help a lot. I could use my Bluetooth on my labtop
> from now on.

Thanks for your time & feedback. I'm going to send firmware patch to linux-firmware soon.

> Thanks
> Chanyeol
> --
> To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
Thanks
-- Ben Kim

      reply	other threads:[~2015-05-21  0:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-19  6:41 [PATCH] Bluetooth: btusb: Support for QCA61x4 on Samsung chanyeol.park
2015-05-19 18:21 ` Marcel Holtmann
2015-05-20 12:35   ` Chan-yeol Park
2015-05-20 12:44     ` Chan-yeol Park
2015-05-20 17:54       ` Ben Young Tae Kim
2015-05-21  0:36         ` Chanyeol Park
2015-05-21  0:45           ` Ben Young Tae Kim [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=555D2A8E.7040805@qca.qualcomm.com \
    --to=ytkim@qca.qualcomm.com \
    --cc=chanyeol.park@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).