Hi,
getting back to this old thread, here's the discussion:
https://patchwork.kernel.org/patch/9615183/
https://patchwork.kernel.org/patch/9615185/
Sven Eckelmann writes:
> On Dienstag, 21. März 2017 21:56:54 CET Rob Herring wrote:
> [...]
>> Is this always the
On Dienstag, 21. März 2017 21:56:54 CET Rob Herring wrote:
[...]
> Is this always the case? There's never some variation beyond the
> reference design that a BDF difference can't handle?
I have no knowledge about anything which isn't handled directly by the BDF
variants. But maybe Kalle can
On Tue, Mar 21, 2017 at 9:33 AM, Sven Eckelmann
wrote:
> On Dienstag, 21. März 2017 08:00:34 CET Rob Herring wrote:
> [...]
>> > It would then up with something like this as compatibility string:
>> >
>> > * qcom,ipq4019-wifi-asus-rt-ac58u
>> > *
On Dienstag, 21. März 2017 08:00:34 CET Rob Herring wrote:
[...]
> > It would then up with something like this as compatibility string:
> >
> > * qcom,ipq4019-wifi-asus-rt-ac58u
> > * qcom,ipq4019-wifi-fritzbox-4040
> > * qcom,ipq4019-wifi-netgear-whatever
> > *
On Mon, Mar 20, 2017 at 11:28 AM, Sven Eckelmann
wrote:
> On Montag, 20. März 2017 10:07:33 CET Rob Herring wrote:
>> On Fri, Mar 10, 2017 at 09:06:14AM +0100, Sven Eckelmann wrote:
>> > The bus + bmi-chip-id + bmi-board-id is not enough to identify the correct
>> >
On Montag, 20. März 2017 09:42:05 CET Adrian Chadd wrote:
> Vendors using ath10k will like this. I mean, I'm using ath10k, and I
> really like this moving forward. This will make life so much easier in
> the long run.
>
> Everyone else isn't using board-2.bin; they're just copying
>
Vendors using ath10k will like this. I mean, I'm using ath10k, and I
really like this moving forward. This will make life so much easier in
the long run.
Everyone else isn't using board-2.bin; they're just copying
calibration/board data files over so the reference driver can assemble
a board data
On Montag, 20. März 2017 10:07:33 CET Rob Herring wrote:
> On Fri, Mar 10, 2017 at 09:06:14AM +0100, Sven Eckelmann wrote:
> > The bus + bmi-chip-id + bmi-board-id is not enough to identify the correct
> > board data file on QCA4019 based devices. Multiple different boards share
> > the same
On Fri, Mar 10, 2017 at 09:06:14AM +0100, Sven Eckelmann wrote:
> The bus + bmi-chip-id + bmi-board-id is not enough to identify the correct
> board data file on QCA4019 based devices. Multiple different boards share
> the same values. Only the original reference designs can currently be
>
The bus + bmi-chip-id + bmi-board-id is not enough to identify the correct
board data file on QCA4019 based devices. Multiple different boards share
the same values. Only the original reference designs can currently be
identified and loaded from the board-2.bin. But these will not result in
the
10 matches
Mail list logo