Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Tue, 15 Nov 2022 08:20:44 +0200 (EET)
From:   Mika Laitio <lamikr@pilppa.org>
To:     Swyter <swyterzone@gmail.com>
cc:     Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
        Jack <ostroffjh@users.sourceforge.net>,
        linux-bluetooth@vger.kernel.org,
        Paul Menzel <pmenzel@molgen.mpg.de>,
        Marcel Holtmann <marcel@holtmann.org>,
        Hans de Goede <hdegoede@redhat.com>
Subject: Re: [Regression] Cambridge Silicon Radio, Ltd Bluetooth Dongle
In-Reply-To: <7ea187e5-7c70-db36-1fa8-148507b2e7c5@gmail.com>
Message-ID: <e382d911-90bc-de3f-9f3-6143ed8a9b75@pilppa.org>
References: <76cd4547-a68d-9d52-1d87-8299e29406ff@gmail.com> <LWPL3AC7.RRTERTU2.B5FO44IX@4YQH7VT3.DY2DZPQX.S6LIZ6VV> <CABBYNZKDEjYOW+b1snUsvBgidW37+tPbsidq0pXaOqWKvRC8uQ@mail.gmail.com> <7ea187e5-7c70-db36-1fa8-148507b2e7c5@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII; format=flowed
Precedence: bulk

> Thanks to this last-effort parameter we can cover that last mile
> without people having to recompile custom versions of btusb.
>
> My dongle doesn't work? Easy, add this here. Most people won't
> have to bother with this, but that final ~3% would be screwed.

So what is the parameter needed for now? Might help users coming to this 
bug and finding this thread.

Mika