On Mon, 2008-12-08 at 13:22 -0800, Inaky Perez-Gonzalez wrote: > I am paying attention to what you say :) :) > I don't want to have this iwpriv like thing for ever; remember that is an stop > gap for the time being as (a) we have no other reference hardware and (b) > our user space is still evolving. > > We already started discussing in the wimax list (with Juuso, from Nokia) how > a NAP-based API should look. My plan is to start working on it in the New > Year, after I come back from vacation. Good to hear. I'm a bit worried about the pain of removing an API again on such short notice, but I guess you'll have to deal with that. Unless you'd want to wait until you've figured it out, it's only another kernel release without wimax that way... ;) > > identical to netlink attributes, but just a bit different: > > > + * This is the control protocol used by the host to control the i2400m > > > + * device (scan, connect, disconnect...). This is sent to / received > > > + * as control frames. These frames consist of a header and zero or > > > + * more TLVs with information. We call each control frame a "message". > > > > Or isn't that what is contained in the WIMAX_GNL_MSG_DATA attribute? You > > can nest netlink attributes, that would already make it a whole lot more > > regular, rather than defining your own sub-protocol. > > It is, but that is host-to-device (or better, host-to-firmware protocol), the > device's specific protocol. I have no say on how it is. It is quite similar, > in any case, as it is TLV based. > > When the kernel level API is in place, a command sent over generic netlink > will be translated by the driver into a protocol-specific message and sent > to the device. Sounds great. johannes -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part Url : http://lists.moblin.org/pipermail/wimax/attachments/20081209/e6fa7afa/attachment.bin
