From: Marcos Chaparro <marcos@mrkindustries.com.ar>
To: Marcel Holtmann <marcel@holtmann.org>,
Gustavo Padovan <gustavo@padovan.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
linux-bluetooth@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] Add bluetooth support for VAIO VPCEH [0489:e027]
Date: Mon, 29 Oct 2012 10:05:40 -0300 [thread overview]
Message-ID: <201210291005.40680.marcos@mrkindustries.com.ar> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 907 bytes --]
Hi,
this patch against 3.7-rc3 identifies my Atheros AR3011 internal bluetooth
device, I just transferred some files from my phone to this debian PC using
bluetooth and it works fine (btw, it needs atheros-firmware package).
Before changing this, lsusb was identifying it as a Foxconn / Hon Hai device,
which is wrong, and it probably loaded a different firmware to the bluetooth
module.
The patches solves the following discussions:
https://answers.launchpad.net/ubuntu/+source/bluez/+question/168992
http://ubuntuforums.org/showthread.php?t=1867214
http://linux-unix-open-source.1053819.n5.nabble.com/Atheros-AR9285-on-
Ubuntu-11-10-Sony-Vaio-VPCEH-wifi-does-t-works-td4931321.html
http://www.vivaolinux.com.br/topico/Rede-Wireless/Bluetooth-vaio-VPCEH-
desabilitado
Please tell me if you won't add it to mainstream for some reason.
Thanks in advance, and greetings from Argentina.
--
Marcos
[-- Attachment #1.2: Type: text/html, Size: 4344 bytes --]
[-- Attachment #2: patchfile --]
[-- Type: text/x-patch, Size: 1165 bytes --]
diff -uNr linux-3.7-rc3.orig/drivers/bluetooth/ath3k.c linux-3.7-rc3.new/drivers/bluetooth/ath3k.c
--- linux-3.7-rc3.orig/drivers/bluetooth/ath3k.c 2012-10-28 16:24:48.000000000 -0300
+++ linux-3.7-rc3.new/drivers/bluetooth/ath3k.c 2012-10-29 09:39:03.459764720 -0300
@@ -67,6 +67,7 @@
{ USB_DEVICE(0x13d3, 0x3304) },
{ USB_DEVICE(0x0930, 0x0215) },
{ USB_DEVICE(0x0489, 0xE03D) },
+ { USB_DEVICE(0x0489, 0xE027) },
/* Atheros AR9285 Malbec with sflash firmware */
{ USB_DEVICE(0x03F0, 0x311D) },
diff -uNr linux-3.7-rc3.orig/drivers/bluetooth/btusb.c linux-3.7-rc3.new/drivers/bluetooth/btusb.c
--- linux-3.7-rc3.orig/drivers/bluetooth/btusb.c 2012-10-28 16:24:48.000000000 -0300
+++ linux-3.7-rc3.new/drivers/bluetooth/btusb.c 2012-10-29 09:39:06.219765159 -0300
@@ -124,6 +124,7 @@
{ USB_DEVICE(0x13d3, 0x3304), .driver_info = BTUSB_IGNORE },
{ USB_DEVICE(0x0930, 0x0215), .driver_info = BTUSB_IGNORE },
{ USB_DEVICE(0x0489, 0xe03d), .driver_info = BTUSB_IGNORE },
+ { USB_DEVICE(0x0489, 0xe027), .driver_info = BTUSB_IGNORE },
/* Atheros AR9285 Malbec with sflash firmware */
{ USB_DEVICE(0x03f0, 0x311d), .driver_info = BTUSB_IGNORE },
next reply other threads:[~2012-10-29 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 13:05 Marcos Chaparro [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-10-29 13:09 [PATCH] Add bluetooth support for VAIO VPCEH [0489:e027] Marcos Chaparro
2012-10-31 18:25 ` Gustavo Padovan
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=201210291005.40680.marcos@mrkindustries.com.ar \
--to=marcos@mrkindustries.com.ar \
--cc=gustavo@padovan.org \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@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).