linux-kernel - [REGRESSION] And a drity fix for 0cf3:3004 QCA Rome device

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <CANoib0FoY86caY-zABHssXq_G8zmt3zJemvYrTyvQ1R58xseoQ@mail.gmail.com>
Date:   Sun, 13 May 2018 16:08:07 +0300
From:   Dmitry Tunin <hanipouspilot@...il.com>
To:     Marcel Holtmann <marcel@...tmann.org>,
        linux-bluetooth <linux-bluetooth@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: [REGRESSION] And a drity fix for 0cf3:3004 QCA Rome device

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 anyway it should be made cleaner. The device is still listed in
ath3k.o as an AR3012.

Regards,

Dmitry.