On Mon, 2009-11-23 at 12:29 +0100, Lennert Buytenhek wrote: > This has the problem that e.g. if someone creates a STA interface first, > and we load the STA firmware image in response to that, and then creates > an additional AP interface, we'd have reload the chip while there's > still an active interface (the original STA one), which seems somewhat > involved. Just rejecting the second add_interface() seems undesirable, > as then the outcome of two add_interface() calls will depend on their > order. > > (AP firmware supports both AP and STA interfaces, but e.g. it doesn't > do STA power save and such.) > > It'll also have some consequences if there are monitor interfaces, as > e.g. STA firmware allows fine-grained control over the receive filter, > while the AP firmware does not. Hah well in that case it won't really work because you really shouldn't change capabilities on the fly. I have no useful idea then, sorry. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
