Re: Asus RT-AC58U boardfile (was Re: [PATCH 2/2] ath10k: search DT for qcom, ath10k-calibration-variant)

2018-10-08 Thread Kalle Valo
Christian Lamparter writes: > Sven's boarddata for the OpenMesh A42 has been accepted. \o/ > So let's try to get the board data for the RT-AC58U merged. > > On Friday, December 8, 2017 10:50:12 AM CET Kalle Valo wrote: >> > I've attached the necessary bmi-board-id=16 and bmi-board-id=17 board

Re: [PATCH 2/2] ath10k: search DT for qcom, ath10k-calibration-variant

2018-04-20 Thread Christian Lamparter
On Donnerstag, 19. April 2018 16:56:36 CEST Kalle Valo wrote: > [...] > I have added them now, please check: > > https://github.com/kvalo/ath10k-firmware/commit/a47bcf1e58c4d8914af0951a80fd8861368b700d Yes, The RT-AC58U is now working much better. The updated RT-AC58U board-data is here:

Asus RT-AC58U boardfile (was Re: [PATCH 2/2] ath10k: search DT for qcom, ath10k-calibration-variant)

2018-01-29 Thread Christian Lamparter
Sven's boarddata for the OpenMesh A42 has been accepted. \o/ So let's try to get the board data for the RT-AC58U merged. On Friday, December 8, 2017 10:50:12 AM CET Kalle Valo wrote: > > I've attached the necessary bmi-board-id=16 and bmi-board-id=17 board > > files to this mail as well. So, all

Re: [PATCH 2/2] ath10k: search DT for qcom, ath10k-calibration-variant

2017-12-08 Thread Kalle Valo
Christian Lamparter writes: > On Friday, March 10, 2017 9:06:15 AM CET Sven Eckelmann wrote: >> Board Data File (BDF) is loaded upon driver boot-up procedure. The right >> board data file is identified on QCA4019 using bus, bmi-chip-id and >> bmi-board-id. >> >> The

Re: [PATCH 2/2] ath10k: search DT for qcom, ath10k-calibration-variant

2017-12-08 Thread Kalle Valo
Sven Eckelmann writes: > Board Data File (BDF) is loaded upon driver boot-up procedure. The right > board data file is identified on QCA4019 using bus, bmi-chip-id and > bmi-board-id. > > The problem, however, can occur when the (default) board data file cannot >

Re: [PATCH 2/2] ath10k: search DT for qcom, ath10k-calibration-variant

2017-10-27 Thread Kalle Valo
Sven Eckelmann writes: > On Freitag, 10. März 2017 19:20:54 CEST Christian Lamparter wrote: > [...] >> @Aeolus Yang / Kalle / QCA: Would it be possible to assign a variant string >> to >> the Asus RT-AC58U? >> >> I've attached the necessary bmi-board-id=16 and

Re: [PATCH 2/2] ath10k: search DT for qcom, ath10k-calibration-variant

2017-08-21 Thread Sven Eckelmann
On Freitag, 10. März 2017 19:20:54 CEST Christian Lamparter wrote: [...] > @Aeolus Yang / Kalle / QCA: Would it be possible to assign a variant string to > the Asus RT-AC58U? > > I've attached the necessary bmi-board-id=16 and bmi-board-id=17 board > files to this mail as well. So, all that

Re: [PATCH 2/2] ath10k: search DT for qcom, ath10k-calibration-variant

2017-03-15 Thread Sven Eckelmann
On Freitag, 10. März 2017 19:20:54 CET Christian Lamparter wrote: [...] > @Aeolus Yang / Kalle / QCA: Would it be possible to assign a variant string to > the Asus RT-AC58U? > > I've attached the necessary bmi-board-id=16 and bmi-board-id=17 board > files to this mail as well. So, all that needs

Re: [PATCH 2/2] ath10k: search DT for qcom, ath10k-calibration-variant

2017-03-10 Thread Christian Lamparter
On Friday, March 10, 2017 9:06:15 AM CET Sven Eckelmann wrote: > Board Data File (BDF) is loaded upon driver boot-up procedure. The right > board data file is identified on QCA4019 using bus, bmi-chip-id and > bmi-board-id. > > The problem, however, can occur when the (default) board data file

[PATCH 2/2] ath10k: search DT for qcom,ath10k-calibration-variant

2017-03-10 Thread Sven Eckelmann
Board Data File (BDF) is loaded upon driver boot-up procedure. The right board data file is identified on QCA4019 using bus, bmi-chip-id and bmi-board-id. The problem, however, can occur when the (default) board data file cannot fulfill with the vendor requirements and it is necessary to use a