about .dump_station() callback

I am looking in get_station() and consequently dump_station() callback for our brcmfmac driver. The latter is called with index. Can I expect this to be starting at 0 and iterate through or can it be requested in any order.

Quoted 4 lines · Arend van Spriel

I am looking in get_station() and consequently dump_station() callback for our brcmfmac driver. The latter is called with index. Can I expect this to be starting at 0 and iterate through or can it be requested in any order.

You can expect that, yes.

If it would help, we could instead give the driver one or two pointers to unsigned long values that start out as 0 and can be controlled entirely by the driver?

Thanks. Guess it is nl80211.c assuring that. I should have checked that first. See that I have to return -ENOENT when iteration is done.

Quoted 3 lines

If it would help, we could instead give the driver one or two pointers to unsigned long values that start out as 0 and can be controlled entirely by the driver?

Not sure if I understand this. What would those pointers represent?

Quoted 2 lines · Arend van Spriel

Thanks. Guess it is nl80211.c assuring that. I should have checked that first. See that I have to return -ENOENT when iteration is done.

Right.

Quoted 4 lines

Quoted 3 lines

If it would help, we could instead give the driver one or two pointers to unsigned long values that start out as 0 and can be controlled entirely by the driver?

Quoted 1 line

Not sure if I understand this. What would those pointers represent?

Well, you could put in there whatever you like :)

Though realistically I wouldn't expect you to put anything other than the sta_idx that you currently get.