> EIRP has been reduced by 4dBm because of TPC requirement.
This is a typo. It's actuall 3dBm for 5 GHz.
been reduced by 4dBm because of TPC requirement.
Signed-off-by: Dmitry Tunin
---
db.txt | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/db.txt b/db.txt
index 37393e6..9e4dc27 100644
--- a/db.txt
+++ b/db.txt
@@ -1097,14 +1097,12 @@ country RS: DFS-ETSI
# 60
And the worst thing is that if has been CCed to
sta...@vger.kernel.org. This means that the regression will affect all
supported kernels soon. This should be fixed!!
2018-05-13 16:08 GMT+03:00 Dmitry Tunin :
> Hi, Marcel
>
> Since f44cb4b older AR3012 devices stopped working. We discu
Hi, Marcel
Since f44cb4b older AR3012 devices stopped working. We discussed that
before that QCA released a ROME device with a duplicate code.
If there is no easy way to check which one is used, then it may be a
good decision to change the kernel code for the newer device in new
kernels.
But an
=01(Isoc) MxPS= 33 Ivl=1ms
I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/bluetooth/btusb.c | 1 +
1 file changed, 1 insertion
.) Sub=ff Prot=ff Driver=(none)
>> I: If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)
>>
>> Since we have Cls=ff, we can add all of them.
>>
>> Signed-off-by: Dmitry Tunin
>> Cc: sta...@vger.kernel.org
>> ---
>> drivers/bluetooth/bt
Hi Marcel,
This one
https://github.com/0day-ci/linux/commits/Dmitry-Tunin/Add-support-of-all-Foxconn-105b-Broadcom-devices/20170708-021656
is really garbled. But I wrote to you in a couple of minutes after I
sent it. And then sent the v2.
It looks like you applied a wrong one.
Regards,
Dmitry
I lost a line here. Sending v2.
2017-07-06 14:29 GMT+03:00 Dmitry Tunin :
> There is another device
>
> T: Bus=01 Lev=02 Prnt=02 Port=00 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
> D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
> P: Vendor=105b ProdID=e066 Rev=01.12
>
have Cls=ff, we can add all of them.
Signed-off-by: Dmitry Tunin
---
drivers/bluetooth/btusb.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index fa24d69..b1e01b0 100644
--- a/drivers/bluetooth/btusb.c
+++ b/drivers
have Cls=ff, we can add all of them.
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/bluetooth/btusb.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index fa24d69..bf95c13 100644
--- a/drivers/bluetooth
= 6 Cls=ff(vend.) Sub=00 Prot=00 Driver=(none)
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/net/wireless/ath/ath9k/hif_usb.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/net/wireless/ath/ath9k/hif_usb.c
b/drivers/net/wireless/ath/ath9k/hif_usb.c
index de2d212
Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/bluetooth/ath3k.c | 2 ++
drivers/bluetooth/btusb.c | 1 +
2 files changed, 3 insertions(+)
diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
index fadba88..b793853
er have the hardware.
>
> Am 08.10.2016 um 12:38 schrieb Dmitry Tunin:
>> psmouse->name "Focaltech Touchpad" is an overkill. In xinput it is too long
>> as
>> "FocaltechPS/2 Focaltech Focaltech Touchpad"
>>
>> In focaltech_report_state()
psmouse->name "Focaltech Touchpad" is an overkill. In xinput it is too long as
"FocaltechPS/2 Focaltech Focaltech Touchpad"
In focaltech_report_state() pointer to psmouse->dev is already stored as *dev
Signed-off-by: Dmitry Tunin
---
drivers/input/mouse/focaltech.c
=01 Prot=01 Driver=btusb
I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/bluetooth/btusb.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/bluetooth/btusb.c b/drivers/bluetooth/btusb.c
index 9ebd73d
(wlcon) Sub=01 Prot=01 Driver=btusb
BugLink: https://bugs.launchpad.net/bugs/1600623
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/bluetooth/ath3k.c | 2 ++
drivers/bluetooth/btusb.c | 1 +
2 files changed, 3 insertions(+)
diff --git a/drivers/bluetooth/ath3k.c b/drivers
(wlcon) Sub=01 Prot=01 Driver=btusb
BugLink: https://bugs.launchpad.net/bugs/1552925
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/bluetooth/ath3k.c | 2 ++
drivers/bluetooth/btusb.c | 1 +
2 files changed, 3 insertions(+)
diff --git a/drivers/bluetooth/ath3k.c b/drivers
Hi, Marcel
We have a problem with Atheros 0cf3:3004 devices.
Atheros people re-used the PID for a new Rome device.
This is a Rome device:
T: Bus=01 Lev=02 Prnt=02 Port=02 Cnt=01 Dev#= 3 Spd=12 MxCh= 0
D: Ver= 1.10 Cls=e0(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0cf3 ProdID=3004 Rev=00.0
(wlcon) Sub=01 Prot=01 Driver=btusb
BugLink: https://bugs.launchpad.net/bugs/1546694
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/bluetooth/ath3k.c | 2 ++
drivers/bluetooth/btusb.c | 1 +
2 files changed, 3 insertions(+)
diff --git a/drivers/bluetooth/ath3k.c b/drivers
(wlcon) Sub=01 Prot=01 Driver=btusb
BugLink: https://bugs.launchpad.net/bugs/1542564
Reported-and-tested-by: Christopher Simerly
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/bluetooth/ath3k.c | 2 ++
drivers/bluetooth/btusb.c | 1 +
2 files changed, 3 insertions(+)
diff
(wlcon) Sub=01 Prot=01 Driver=btusb
This device requires ar3k/AthrBT_0x31010100.dfu and
ar3k/ramps_0x31010100_40.dfu firmware files that are not in
linux-firmware yet.
BugLink: https://bugs.launchpad.net/bugs/1542944
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/bluetooth
(wlcon) Sub=01 Prot=01 Driver=btusb
BugLink: https://bugs.launchpad.net/bugs/1506615
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/bluetooth/ath3k.c | 2 ++
drivers/bluetooth/btusb.c | 1 +
2 files changed, 3 insertions(+)
diff --git a/drivers/bluetooth/ath3k.c b/drivers
) Sub=01 Prot=01 Driver=btusb
I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
BugLink: https://bugs.launchpad.net/bugs/1502781
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/bluetooth/ath3k.c | 2 ++
drivers/bluetooth/btusb.c | 1 +
2 files changed, 3
The previous mail was a wrong file. Here is the original Raphael report
Hello,
[1.] One line summary of the problem:
AR9462: ath3k and btusb: support for device 04ca:300d makes it
disconnect/reconnect indefinitely
[2.] Full description of the problem/report:
I have an Acer Aspire V3-371-31
11.08.2015 22:43, Dmitry Tunin пишет:
>
>
> 11.08.2015 22:23, Marcel Holtmann пишет:
>> Hi Dmitry,
>>
>>> This patch causes infinite loop on loading firmware on Acer Aspire
>>> V3è371-31KW and probably other laptops.
>>>
>>> This is
11.08.2015 22:23, Marcel Holtmann пишет:
> Hi Dmitry,
>
>> This patch causes infinite loop on loading firmware on Acer Aspire
>> V3è371-31KW and probably other laptops.
>>
>> This is a serious regression, because system becomes unresponsive.
>>
>> This should be reverted until the firmware loadi
11.08.2015 13:50, Dmitry Tunin пишет:
> This patch causes infinite loop on loading firmware on Acer Aspire
> V3è371-31KW and probably other laptops.
>
> This is a serious regression, because system becomes unresponsive.
>
> This should be reverted until the firmware loading i
This patch causes infinite loop on loading firmware on Acer Aspire
V3è371-31KW and probably other laptops.
This is a serious regression, because system becomes unresponsive.
This should be reverted until the firmware loading issue is sorted out.
Signed-off-by: Dmitry Tunin
Cc: sta
This patch causes a regression on some Acer Aspire laptops.
See last comments in https://bugs.launchpad.net/bugs/1394368
2015-08-10 13:12 GMT+03:00 Ben Hutchings :
> 3.2.71-rc1 review patch. If anyone has any objections, please let me know.
>
> --
>
> Fro
This patch was sent by a mistake. I rebased it and there was an error. Sent v2.
2015-06-29 18:29 GMT+03:00 Dmitry Tunin :
> Wireless is not blocked without this quirk, but
> wireless LED does not follow wireless status.
> With this quirk it accurately reflects if wireless is on or off.
&
Wireless is not blocked without this quirk, but
wireless LED does not follow wireless status.
With this quirk it accurately reflects if wireless is on or off.
Signed-off-by: Dmitry Tunin
Acked-by: Corentin Chary
Cc: sta...@vger.kernel.org
---
drivers/platform/x86/asus-nb-wmi.c | 9 +
1
Wireless is not blocked without this quirk, but
wireless LED does not follow wireless status.
With this quirk it accurately reflects if wireless is on or off.
Signed-off-by: Dmitry Tunin
Acked-by: Corentin Chary
Cc: sta...@vger.kernel.org
---
drivers/platform/x86/asus-nb-wmi.c | 9 +
1
= 49 Ivl=1ms
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/bluetooth/ath3k.c | 2 ++
drivers/bluetooth/btusb.c | 1 +
2 files changed, 3 insertions(+)
diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
index 2fa6588..e527a3e 100644
--- a/drivers/bluetooth
: Bluetooth
Soft blocked: no
Hard blocked: no
Only with wapf=1 everything works OK.
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/platform/x86/asus-nb-wmi.c | 13 +
1 file changed, 13 insertions(+)
diff --git a/drivers/platform/x86/asus-nb-wmi.c
b/drivers
06.06.2015 20:25, Dmitry Tunin пишет:
BugLink: https://bugs.launchpad.net/bugs/1462614
This device requires new firmware files
AthrBT_0x11020100.dfu and ramps_0x11020100_40.dfu added to
/lib/firmware/ar3k/ that are not included in linux-firmware yet.
T: Bus=03 Lev=01 Prnt=01 Port=09 Cnt=06
(wlcon) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=13d3 ProdID=3474 Rev=00.01
C: #Ifs= 2 Cfg#= 1 Atr=e0 MxPwr=100mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
Signed-off-by: Dmitry Tunin
Cc: sta
(Isoc) MxPS= 49 Ivl=1ms
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/bluetooth/ath3k.c | 2 ++
drivers/bluetooth/btusb.c | 1 +
2 files changed, 3 insertions(+)
diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
index 8c81af6..ee64764 100644
--- a/drivers
Focaltech touchpads report finger width in packet[5] of absolute packet.
Range for width in raw format is 0x10 - 0x70. Second half-byte is always 0.
0xff is reported, when a large contact area is detected.
This can be handled in userspace.
Signed-off-by: Dmitry Tunin
---
drivers/input/mouse
30.05.2015 02:37, Dmitry Torokhov пишет:
> On Sat, May 30, 2015 at 02:00:59AM +0300, Dmitry Tunin wrote:
>> Focaltech touchpads report finger width in packet[5] of absolute packet.
>> Range for width in raw format is 0x10 - 0x70. Second half-byte is always 0.
>> 0xff is r
30.05.2015 02:37, Dmitry Torokhov пишет:
> On Sat, May 30, 2015 at 02:00:59AM +0300, Dmitry Tunin wrote:
>> Focaltech touchpads report finger width in packet[5] of absolute packet.
>> Range for width in raw format is 0x10 - 0x70. Second half-byte is always 0.
>> 0xff is r
Focaltech touchpads report finger width in packet[5] of absolute packet.
Range for width in raw format is 0x10 - 0x70. Second half-byte is always 0.
0xff is reported, when a large contact area is detected.
This can be handled in userspace.
Signed-off-by: Dmitry Tunin
---
drivers/input/mouse
Wireless is not blocked without this quirk, but
wireless LED does not follow wireless status.
With this quirk it accurately reflects if wireless is on or off.
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/platform/x86/asus-nb-wmi.c | 9 +
1 file changed, 9
OK. Thanks.
29.05.2015 22:30, Darren Hart пишет:
> On Fri, May 29, 2015 at 08:18:57PM +0300, Dmitry Tunin wrote:
>> Darren,
>>
>> And also I think it can be cc'ed to stable too.
>>
>
> I mined your second version off the list, added Phillipe's Si
Darren,
And also I think it can be cc'ed to stable too.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkm
Darren,
I sent this patch twice, second time with more detailed explanation.
But got no answer. So I asked Philippe to push it.
Regards,
Dmitry.
29.05.2015 19:49, Darren Hart пишет:
> On Fri, May 29, 2015 at 03:20:01PM +0200, Philippe Coval wrote:
>> From: Dmitry Tunin
>>
&
=01 Driver=btusb
I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/bluetooth/ath3k.c | 2 ++
drivers/bluetooth/btusb.c | 1 +
2 files changed, 3 insertions(+)
diff --git a/drivers/bluetooth/ath3k.c b/drivers
The quirk is needed to enable wifi
BugLink: https://bugs.launchpad.net/bugs/1397021
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/platform/x86/ideapad-laptop.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a/drivers/platform/x86/ideapad-laptop.c
b/drivers
=01 Prot=01 Driver=btusb
I: If#= 1 Alt= 0 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/bluetooth/ath3k.c | 2 ++
drivers/bluetooth/btusb.c | 1 +
2 files changed, 3 insertions(+)
diff --git a/drivers/bluetooth/ath3k.c b
>
> Hi,
>
> Some comments below. If it is not a problem that width values are
> outdated as soon as there are two or more fingers on the touchpad, I
> think the change is good.
>
> Regards,
> Mathias
>
> Am 24.04.2015 um 01:15 schrieb Dmitry Tunin:
>> Foc
Focaltech touchpads report finger width in packet[5] of absolute packet.
Range for width in raw format is 0x10 - 0x70. Second half-byte is always 0.
0xff is reported, when a large contact area is detected.
This can be handled in userspace.
Signed-off-by: Dmitry Tunin
---
drivers/input/mouse
I see that I did not change that here.
Width can be in state->width or fingers[finger]->width
I think latter is mere correct.It should be that way in this patch.
I moved ot back and forth and tested. Noticed no difference.
24.04.2015 13:44, Dmitry Tunin пишет:
>
>>
>> Hi
>
> Hi,
>
> Some comments below. If it is not a problem that width values are
> outdated as soon as there are two or more fingers on the touchpad, I
> think the change is good.
>
> Regards,
> Mathias
>
> Am 24.04.2015 um 01:15 schrieb Dmitry Tunin:
>>
Focaltech touchpads report finger width in packet[5] of absolute packet.
Range for width in raw format is 0x10 - 0x70. Second half-byte is always 0.
0xff is reported, when a large contact area is detected.
This can be handled in userspace.
Signed-off-by: Dmitry Tunin
---
drivers/input/mouse
Focaltech touchpads report finger width in packet[5] of absolute packet.
Range for width in raw format is 0x10 - 0x70. Second half-byte is always 0.
0xff is reported, when a large contact area is detected.
This can be handled in userspace.
---
drivers/input/mouse/focaltech.c | 16 ++--
Fixed commit message
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Focaltech touchpads report finger width in packet[5] of absolute packet.
Range for width in raw format is 0x10 - 0x70. Second half-byte is always 0.
0xff is reported, when a large contact area is detected.
This can be handled in userspace.
---
drivers/input/mouse/focaltech.c | 15 ++-
---
drivers/input/mouse/focaltech.c | 15 ++-
1 file changed, 14 insertions(+), 1 deletion(-)
diff --git a/drivers/input/mouse/focaltech.c b/drivers/input/mouse/focaltech.c
index 23d2594..513a7e1 100644
--- a/drivers/input/mouse/focaltech.c
+++ b/drivers/input/mouse/focaltech.c
@@ -90
Now I made it in a correct way. No need to count fingers.
Just send width after an abs packet is received.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.
> Focaltech touchpads report finger width in packet[5] of absolute packet.
> Range for width in raw format is 0x10 - 0x70. Second half-byte is always 0.
> 0xff is reported, when a large contact area is detected.
> This can be handled in userspace.
>
> Signed-off-by: Dmitry Tunin
Focaltech touchpads report finger width in packet[5] of absolute packet.
Range for width in raw format is 0x10 - 0x70. Second half-byte is always 0.
0xff is reported, when a large contact area is detected.
This can be handled in userspace.
Signed-off-by: Dmitry Tunin
---
drivers/input/mouse
Focaltech touchpads report finger width in packet[5] of absolute packet.
Range for width in raw format is 0x10 - 0x70. Second half-byte is always 0.
0xff is reported, when a large contact area is detected.
This can be handled in userspace.
Signed-off-by: Dmitry Tunin
---
drivers/input/mouse
> Focaltech touchpads report finger width in packet[5] of absolute packet.
> Range for width in raw format is 0x10 - 0x70. Second half-byte is always 0.
> 0xff is reported, when a large contact area is detected.
> This can be handled in userspace.
>
> Signed-off-by: Dmitry Tunin
Focaltech touchpads report finger width in packet[5] of absolute packet.
Range for width in raw format is 0x10 - 0x70. Second half-byte is always 0.
0xff is reported, when a large contact area is detected.
This can be handled in userspace.
Signed-off-by: Dmitry Tunin
---
drivers/input/mouse
> From: alxpl
>
> Add 04f2:aff1 to ath3k.c supported devices list and btusb.c blacklist, so
> that the device can load the ath3k firmware and re-enumerate itself as an
> AR3011 device.
>
>
> T: Bus=05 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
> D: Ver= 1.10 Cls=e0(wlcon) Sub=
> From: alxpl
>
>
> With a lot of help and pointers from Dmitry Tunin, I managed to put the patch
> together in the "appropriate" fashion, against bluetooth-next. He also
> suggested that I include the relevant information from my
> /sys/kernel/debug/usb/
> Lenovo G30-50 does not have a hardware wireless switch and wireless
> is always blocked.
>
> BugLink: https://bugs.launchpad.net/bugs/1397021
>
> Signed-off-by: Dmitry Tunin
> Cc: sta...@vger.kernel.org
> ---
> drivers/platform/x86/ideapad-laptop.c | 7 +++
>
Lenovo G30-50 does not have a hardware wireless switch and wireless
is always blocked.
BugLink: https://bugs.launchpad.net/bugs/1397021
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/platform/x86/ideapad-laptop.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a
The Thunderbird client after update to 31.3.0 adds extra Space symbols at some
lines for some reason.
Before the update it was OK, when properly set up not to wrap lines.
In my initial patch at 234 is an extra Space before Tab.
I will use git for good now.
--
To unsubscribe from this list: send
ub=01 Prot=01 Driver=btusb
> E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
> I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
> E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
> E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
>
&g
=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/bluetooth/ath3k.c | 2 ++
drivers/bluetooth/btusb.c | 1 +
2 files changed, 3
You are correct. It does not apply after it goes thru email.
But I tried to send it using git send-email to myself with same result.
This is mystics.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info
Any ideas what may be wrong? Is the tree URL correct or there is another
bluetooth-next branch I dot know about?
I just clean cloned it again and applied with no problem.
17.01.2015 21:59, Marcel Holtmann пишет:
Hi Dmitry,
please do not top post on this mailing list.
This patch is against
g
: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/bluetooth/ath3k.c | 2 ++
drivers/bluetooth/btusb.c | 1 +
2 files changed, 3 insertions(+)
your patch does not apply cleanly:
Applying: ath3k: Add
: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
---
drivers/bluetooth/ath3k.c | 2 ++
drivers
=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 33 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 33 Ivl=1ms
I: If#= 1 Alt= 5 #EPs= 2 Cls=e0(wlcon) Sub=01 Prot=01 Driver=btusb
E: Ad=83(I) Atr=01(Isoc) MxPS= 49 Ivl=1ms
E: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
Signed-off-by: Dmitry Tunin
Cc: sta...@vger.kernel.org
I did already. It is not that simple.
https://bugzilla.kernel.org/show_bug.cgi?id=70241#c86
18.12.2014 23:04, Matthew Garrett пишет:
Ah, http://cgit.freedesktop.org/~jani/drm/log/?h=didl nominally has
support for doing the right thing here - any chance you can try that
tree?
--
To unsubscribe
Len,
I completely agree that debugging and testing of a real solution would be a
problem.
And adding "acpi_osi=" is not too hard as a boot option.
In some cases it can be built-in, if it is a box solution.
So the patch is no good.
18.12.2014 21:09, Len Brown пишет:
NAK on addoing this acpi_o
But at least two devices work well with this quirk.
That must be some ASUS UEFI firmware fault, but still it is a workaround.
You can find some more information in those bugzilla reports.
https://bugzilla.kernel.org/show_bug.cgi?id=89401
https://bugzilla.kernel.org/show_bug.cgi?id=70241
18.12.20
I tried that too. No effect.
18.12.2014 17:26, Matthew Garrett пишет:
Ah, I see - can you try acpi_osi="!Windows 2013" ?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.o
No, It does not. That's first I tried.
18.12.2014 17:09, Matthew Garrett пишет:
On Thu, Dec 18, 2014 at 05:04:23PM +0300, Dmitry Tunin wrote:
Sry, wrong url b4
https://bugzilla.kernel.org/attachment.cgi?id=125091
Can you check whether acpi_osi="Windows 2012" also results in
Here is another one from X200MA
https://bugzilla.kernel.org/attachment.cgi?id=160161
18.12.2014 16:57, Matthew Garrett пишет:
Can you run acpidump and upload the ACPI tables somewhere?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to major
Sry, wrong url b4
https://bugzilla.kernel.org/attachment.cgi?id=125091
18.12.2014 16:57, Matthew Garrett пишет:
Can you run acpidump and upload the ACPI tables somewhere?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kern
It is already done.
https://bugzilla.kernel.org/attachment.cgi?id=160161
18.12.2014 16:57, Matthew Garrett пишет:
Can you run acpidump and upload the ACPI tables somewhere?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.ke
AM, Dmitry Tunin wrote:
Add "acpi_osi=" quirk for ASUS X200MA
More information can be found in UX302LA bugreport
https://bugzilla.kernel.org/show_bug.cgi?id=70241
X200MA is affected by th e same bug and the solution has been tested
I reported it to launchpad too
https://bugs.launchpad.
Josh,
I agree, that a better approach is to implement opregion in a right way.
But it will take some time. In the meantime this kind of quirks solve the
problem.
And it is quite safe.
18.12.2014 16:25, Josh Boyer пишет:
On Thu, Dec 18, 2014 at 7:16 AM, Dmitry Tunin wrote:
Add "acp
This patch is a workaround quirk to enable brightness keys.
BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=70241
Cc: sta...@vger.kernel.org
Signed-off-by: Dmitry Tunin
---
drivers/acpi/blacklist.c | 8
1 file changed, 8 insertions(+)
diff --git a/drivers/acpi/blacklist.c b
8
Cc: sta...@vger.kernel.org
Signed-off-by: Dmitry Tunin
---
drivers/acpi/blacklist.c | 20
1 file changed, 20 insertions(+)
diff --git a/drivers/acpi/blacklist.c b/drivers/acpi/blacklist.c
index 7556e7c..f78ed08 100644
--- a/drivers/acpi/blacklist.c
+++ b/drivers/acpi/b
This patch is only a temporary hack. This issue should be fixed by other ways.
See https://bugzilla.kernel.org/show_bug.cgi?id=70241#c70
07.12.2014 17:35, Dmitry Tunin пишет:
Add "acpi_osi=" quirk for ASUS X200MA
More information can be found in UX302LA bugreport
https://bugzilla.
Is anything wrong with this patch?
It was made against last mainline kernel at the moment.
If a patch against linux-next needed, I can make it.
Without this patch wireless is always blocked.
Regards,
Dmitry.
27.11.2014 19:39, Dmitry Tunin пишет:
Rfkill always shows wireless blocked unless
Add "acpi_osi=" quirk for ASUS X200MA
More information can be found in UX302LA bugreport
https://bugzilla.kernel.org/show_bug.cgi?id=70241
I reported it to launchpad too
https://bugs.launchpad.net/ubuntu/bug/1400068
Cc: sta...@vger.kernel.org
Signed-off-by: Dmitry Tunin
---
dr
Add "acpi_osi=" quirk for ASUS X200MA
More information can be found in UX302LA bugreport
https://bugzilla.kernel.org/show_bug.cgi?id=70241
I reported it to launchpad too
https://bugs.launchpad.net/ubuntu/bug/1400068
Cc:sta...@vger.kernel.org
Signed-off-by: Dmitry Tunin
---
dr
Wifi led does not follow wireless status, add quirk.
Cc: sta...@vger.kernel.org
Signed-off-by: Dmitry Tunin
---
drivers/platform/x86/asus-nb-wmi.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/platform/x86/asus-nb-wmi.c
b/drivers/platform/x86/asus-nb-wmi.c
index c1a6cd6
Rfkill always shows wireless blocked unless ideapad_laptop is blacklisted.
Add a quirk.
Cc: sta...@vger.kernel.org
BugLink:https://bugs.launchpad.net/bugs/1397021
Signed-off-by: Dmitry Tunin
---
drivers/platform/x86/ideapad-laptop.c | 7 +++
1 file changed, 7 insertions(+)
diff --git a
I do not blame anyone. I am not paid for submitting patches. I've done
some work to find a solution. You can treat my post as a bug report.
I know it as a very hard 'extra work' to edit my mail, or remove a
duplicate of a 3 line patch. But the whole thing is too much of an extra
work for me. I
...@vger.kernel.org
Signed-off-by: Dmitry Tunin
so you really need to make sure to send only one version. I now have two
patches labeled as v6 and I have no idea which one is recent and which one I am
suppose to apply.
I tried applying this one, but it failed. Patches need to be based against
bluetooth-next
: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
CC: sta...@vger.kernel.org
Signed-off-by: Dmitry Tunin
---
diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
index d85ced2..086240c 100644
--- a/drivers/bluetooth/ath3k.c
+++ b/drivers/bluetooth/ath3k.c
@@ -105,6 +105,7 @@ static const
: Ad=03(O) Atr=01(Isoc) MxPS= 49 Ivl=1ms
CC: sta...@vger.kernel.org
Signed-off-by: Dmitry Tunin
---
diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
index d85ced2..086240c 100644
--- a/drivers/bluetooth/ath3k.c
+++ b/drivers/bluetooth/ath3k.c
@@ -105,6 +105,7 @@ static const
Add support for bluetooth MCI WB335 (AR9565) Wi-Fi+bt module.
This bluetooth module requires loading patch and sysconfig by ath3k driver.
CC: sta...@vger.kernel.org
Signed-off-by: Dmitry Tunin
---
diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
index d85ced2..086240c 100644
Add support for bluetooth MCI WB335 (AR9565) Wi-Fi+bt module.
This bluetooth module requires loading patch and sysconfig by ath3k driver.
CC: sta...@vger.kernel.org
Signed-off-by: Dmitry Tunin
---
diff --git a/drivers/bluetooth/ath3k.c b/drivers/bluetooth/ath3k.c
index d85ced2..086240c 100644
1 - 100 of 108 matches
Mail list logo