> From: linux-wireless-owner@xxxxxxxxxxxxxxx [mailto:linux-wireless- > owner@xxxxxxxxxxxxxxx] On Behalf Of Amitkumar Karwar > Sent: Wednesday, August 03, 2016 4:51 PM > To: Kalle Valo > Cc: linux-wireless@xxxxxxxxxxxxxxx > Subject: RE: [PATCH] mwifiex: handle edmac vendor command > > Hi Kalle, > > > From: Kalle Valo [mailto:kvalo@xxxxxxxxxxxxxx] > > Sent: Tuesday, May 24, 2016 1:53 AM > > To: Amitkumar Karwar > > Cc: linux-wireless@xxxxxxxxxxxxxxx > > Subject: Re: [PATCH] mwifiex: handle edmac vendor command > > > > Amitkumar Karwar <akarwar@xxxxxxxxxxx> writes: > > > > > Hi Kalle, > > > > > >> From: Amitkumar Karwar [mailto:akarwar@xxxxxxxxxxx] > > >> Sent: Friday, April 29, 2016 9:28 PM > > >> To: linux-wireless@xxxxxxxxxxxxxxx > > >> Cc: Jeff CF Chen; Amitkumar Karwar > > >> Subject: [PATCH] mwifiex: handle edmac vendor command > > >> > > >> From: chunfan chen <jeffc@xxxxxxxxxxx> > > >> > > >> Userspace can configure edmac values through a custom vendor > command. > > >> They will be used by hardware for adaptivity. > > >> > > >> Signed-off-by: chunfan chen <jeffc@xxxxxxxxxxx> > > >> Signed-off-by: Amitkumar Karwar <akarwar@xxxxxxxxxxx> > > > > [deleted over 200 lines of unnecessary quotes] > > > > > This patch seems to have deferred. We basically want a way to > > > download a vendor specific configuration to our firmware. Do you > > > have any suggestions on how can achieve this in better way? > > > > > > I can see below iw command suits our requirement. > > > > > > iw dev <devname> vendor send <oui> <subcmd> <filename|-|hex data> > > > > > > Please guide. > > > > It was deferred because use of the nl80211 vendor interface (which I > > don't think belong to upstream drivers). I'll take a look at this > > patch in detail after the merge window. > > > > Did you get a chance to check this patch? > Please let me know if you have any suggestions. > Any suggestions for a mechanism to download vendor specific command to firmware? Regards, Amitkumar Karwar
