On Tue, 2007-06-12 at 13:36 +0200, Jiri Benc wrote: > Johannes probably meant a binary blob prepared by user space. That still > complies to the one value per file rule. Right, but that is not easy to use (i.e with `echo` or `cat`) without writting a user space program. > > The DLS is easier because it only has one parameter (peer mac address) > > now. I programed it the same way as tspec. So when we find to need more > > parameters for DLS setup, we can add another debugfs file for the new > > parameter instead of combining multiple parameters in one file. > > > > I'd agree I didn't pay a lot of attentions to the debugfs interface > > design since I thought it was used for occasional debug only. Please > > tell me what which do you prefer: one value per file or multiple values > > per file so that we can do one shot parameter passing? So I don't need > > to switch them back and forth. > > Depends on how long you want to keep this debugfs interface. If it's just a > few months matter and it's never going to hit vanilla, it's probably not > worth the effort to rewrite it. I'm working with Johannes with the API define. When this is done, hopfully we can remove the debugfs stuff. Thanks, -yi - 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
