All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chan-yeol Park <chanyeol.park@samsung.com>
To: Marcel Holtmann <marcel@holtmann.org>, chanyeol.park@gmail.com
Cc: linux-bluetooth@vger.kernel.org, Kim@samsung.com,
	Ben Young Tae <ytkim@qca.qualcomm.com>
Subject: Re: [PATCH] Bluetooth: btusb: Support for QCA61x4 on Samsung
Date: Wed, 20 May 2015 21:35:31 +0900	[thread overview]
Message-ID: <555C7F93.9080901@samsung.com> (raw)
In-Reply-To: <D5B20D85-8B5F-4694-8B5E-2BFC670BE85C@holtmann.org>

[-- Attachment #1: Type: text/plain, Size: 850 bytes --]

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.

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

Thanks
Chanyeol


[-- Attachment #2: Type: text/html, Size: 1596 bytes --]

  reply	other threads:[~2015-05-20 12:35 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 [this message]
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

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=555C7F93.9080901@samsung.com \
    --to=chanyeol.park@samsung.com \
    --cc=Kim@samsung.com \
    --cc=chanyeol.park@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=ytkim@qca.qualcomm.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.