On 3 April 2018 at 13:24, Arend van Spriel <arend.vanspriel@xxxxxxxxxxxx> wrote: > On 4/3/2018 12:17 PM, Rafał Miłecki wrote: >> >> On 3 April 2018 at 10:22, Arend van Spriel <arend.vanspriel@xxxxxxxxxxxx> >> wrote: > > > [...] > >>> >>> >>> My first reaction to this email needed to some cooldown time, but managed >>> to >>> swallow it. >> >> >> I'm sorry you keep reacting to my e-mails/patches that way. I can't >> see how my e-mail was offensive in any way. I assure I didn't mean it >> to be. > > > I can not really say what it is. Anyway it is my fault and have to work on > it. > > [...] > >>> I actually had a couple of issues with the patch and did not >>> want to waste Dan's time when there was a patch ready. I did not want to >>> add >>> another device because we are still in the process of releasing the >>> firmware >>> for it. Fiddling with radar detection causing the delay of that. >> >> >> It's something that I think was never a problem in the past. There is >> e.g. support for 4366c0 support in the brcmfmac without >> brcmfmac4366c-pcie.bin officially released. > > > My rule of thumb is to get the firmware released before/when the driver > patch hits mainline. However, sometimes it blows up in my face. Like with > the 4366c0. We had to add a new feature to the firmware to get an ok, which > caused the delay. Hopefully, I can get it out soon. Sounds great, thanks, I keep by fingers crossed :) -- Rafał
