On Thu, 2006-12-14 at 21:35 -0800, Simon Barber wrote:
> This is all part of the client MLME - it would be much better to add
> this functionality to wpa_supplicant, rather than adding it to the
> kernel. Nothing here needs to be in the kernel for any reason.
Theoretically, the whole network stack
This is all part of the client MLME - it would be much better to add
this functionality to wpa_supplicant, rather than adding it to the
kernel. Nothing here needs to be in the kernel for any reason.
The client MLME functions that are in the kernel were put in there for
test and debugging convenien
On Thu, 2006-12-14 at 12:23 +0100, Jiri Benc wrote:
> So... what about implementing that into cfg80211? :-)
>
> I'm not inclined towards this patch (even if you address Stephen's
> comment).
OK. This is only for my testing (or maybe someone else wants to try the
code). I'm not asking to merge it
On Thu, 2006-12-14 at 12:23 +0100, Jiri Benc wrote:
> On Thu, 14 Dec 2006 12:03:02 +0800, Zhu Yi wrote:
> > The sysfs interface here is only a proof of concept. It provides a way for
> > the userspace applications to use the advanced QoS features supported by
> > d80211 stack. The finial solution s
On Thu, 14 Dec 2006 12:03:02 +0800, Zhu Yi wrote:
> The sysfs interface here is only a proof of concept. It provides a way for
> the userspace applications to use the advanced QoS features supported by
> d80211 stack. The finial solution should be switched to cfg80211.
So... what about implementin
O
> +static ssize_t store_tspec(struct class_device *dev, const char *buf,
> +size_t len)
> +{
> + if (sscanf(buf, "%hu %hu %u %u %u %u %u %u %u %u %u %u %u %hu %hu",
> +&_tspec.nominal_msdu_size,
> +&_tspec.max_msdu_size,
> +
