As I was discussing with johill earlier we should probably lay down the overal layout of what our communication path will look like down the road between userspace, userspace MLME, cfg8021, nl80211 and drivers both FullMAC and SoftMAC, This conversation spawned over implementing the next console userspace configuration utility, iw. This is necessary so we don't write userspace utilities we later have to replace or simply start with bad design from the beginning. I think it will also help set our pace on what items we need to prioritize in the short term for kernel releases and also on the long run. What really puzzles me right now is the communication path between userspace and the userspace MLME, and even if this communication should exist. I've edited some draft stuff about this and communication paths. I'd like to ask those of you working on this to please help fix and update it. For now I've stashed here: http://linuxwireless.org/en/developers/todo_list#userspacemlme Other items which we should consider: * Should umlme be optional or is this desired mandatory down the road? * How long should we wait to swich to a umlme? Luis - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
