Ping. On 22/Jun/2016 17:54, Ismael Luceno wrote: > On 22/Jun/2016 21:07, Arend van Spriel wrote: > > On 22-06-16 20:36, Ismael Luceno wrote: > > > On 21/Jun/2016 21:02, Arend van Spriel wrote: > > >> On 21-06-16 02:18, Ismael Luceno wrote: > > >>> Signed-off-by: Ismael Luceno <ismael@xxxxxxxxxxx> > > >> > > >> A bit more description would be nice. I am actually wondering why you > > >> would be adding this. If I am not mistaken the AE1200 can not be handled > > >> by brcmfmac. Otherwise I am interested in a kernel log showing the > > >> device probe sequence with brcmfmac loaded with parameter debug=0x1416. > > > > > > Log attached. > > > > > > I was surprised it works without any tweaking. > > > > Nice. What kernel version are you running on. > > Commit c3695331f3a326a468bd6a5b6f05b481b399726b. > > > Can you also dump a debugfs file, > > ie. /sys/kernel/debug/brcmfmac/*/revinfo. > > vendorid: 0x14e4 > deviceid: 0x4347 > radiorev: 114.5.112 > chipnum: 43235 (a8e3) > chiprev: 3 > chippkg: 4 > corerev: 24 > boardid: 0x0571 > boardvendor: 0x14e4 > boardrev: P523 > driverrev: 5.90.188.22 > ucoderev: 0 > bus: 0 > phytype: 4 > phyrev: 9 > anarev: 0 > nvramrev: 00000000 > > > > I want to know what chip id and revision is reported. I have tried an > > AE1200 in the past, but it had a chip revision that had insufficient > > memory to run fullmac firmware. > > That's going to be confusing for anyone having the hardware :(. > > > Is there FCC registration number on it? > > Yes: Q87-AE1200
