Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support for RTL8723BU on kernel 2.6 #69

Open
francescoagostini93 opened this issue Dec 10, 2018 · 0 comments
Open

Support for RTL8723BU on kernel 2.6 #69

francescoagostini93 opened this issue Dec 10, 2018 · 0 comments

Comments

@francescoagostini93
Copy link

Hello, i'm trying to port rtk_btusb driver on kernel 2.6.35.3 compiled for i.MX51.
The dongle producted by LM tecnologies is an LM811 with RTL8732BU, as suggested by vendor, for the bluetooth driver i'm try to compile troy branch. Inside troy branch there is 3 different driver, btusb on the root and rtk_btus. For the 2.6.35.3 kernel i can compile only the rtk_btusb inside the bluetooth_usb_driver folder. When i probe driver got follow log

rtk_btusb: Realtek Bluetooth USB driver ver 2.11
rtk_btusb: btusb_probe intf->cur_altsetting->desc.bInterfaceNumber=0
rtk_btusb: btusb_probe can_wakeup=1 flag2=0
rtk_btusb: patch_add
rtk_btusb: pid = 0xb720
usbcore: registered new interface driver rtk_btusb

and when i rise hci0 interface got

rtk_btusb: btusb_open start pm_usage_cnt(0x1)
rtk_btusb: btusb_open hdev->promisc ==0
rtk_btusb: download_patch start
rtk_btusb: check_fw_version : read_ver_rsp->lmp_subver = 0x8723
rtk_btusb: check_fw_version : patch_entry->lmp_sub = 0x8723
rtk_btusb: get_firmware start
rtk_btusb: load_firmware start
rtk_btusb: lmp_version = 0x8723
rtk_btusb: This is not 8723a, use new patch style!
rtk_btusb: rtk_get_eversion::gEVersion=255
rtk_btusb: rtk_get_eversion : eversion->status = 0x0, eversion->version = 0x1
rtk_btusb: gEVersion=1
rtk_btusb: opcode = 0x0
rtk_btusb: length = 0x1
rtk_btusb: data = 0x1
rtk_btusb: lmp_version is 8723, project_id is 8723, match!
rtk_btusb: fm_version = 0xe2f9f73
rtk_btusb: number_of_total_patch = 2
rtk_btusb: chipID = 2
rtk_btusb: patch_length = 0x57e0
rtk_btusb: start_offset = 0x5800
rtk_btusb: buf_len = 0x57e0
rtk_btusb: Fw: exists, config file:not exists
rtk_btusb: load_firmware done
rtk_btusb: get_firmware done
rtk_btusb: download_data start
rtk_btusb: download_data done
rtk_btusb: check_fw_version : read_ver_rsp->lmp_subver = 0x9f73
rtk_btusb: check_fw_version : patch_entry->lmp_sub = 0x8723
rtk_btusb: Rtk patch end 0
rtk_btusb: btusb_open end pm_usage_cnt(0x0)
root@2win ~$ rtk_btusb: hci0 evt 3
rtk_btusb: btusb_notify : hci0 evt 3

if i try to run hcitool scan, i can't see any device. And if i try to run RFComm server i can't see it from other devices. If i try to do same operation with BT only dongle with btusb standard driver it works fine, but i need combo module wifi-bt. Reading other issue i tried to load wifi driver before and rise wlan0 interface. No result

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant