Re: Re: [Prism54-devel] Prism54 development update

> > Do you seriously expect using CPU for sending 10 beacons per second
> > will even be visible in you favorite system load meter?
> > Maybe on 100MHz PentiumI it (barely) will be, but on anything
> > more sane it would not.
> > 
> > After all, people had difficulties detecting impact of HZ=1000
> > versus HZ=100, and that's nearly thousand additional interrupts
> > per second. Here we talk about tens of interrupts per sec.
> 
> OK, perhaps it will note make much difference on an (modern) laptop, but
> there are also users running prism54 on an embedded device.
> 
> Also it would be nice to run prism54 as AP without additional software,
> but only if it runs as a full-featured ap and not not some mixture of
> either limited firmware ap or full featured software ap. In this case I
> think a software ap only would be the only good solution.
> 
> Perhaps it also depends on the development of the ieee80211 stack now in
> next mainline kernel and what things can/must be done to integrate
> prism54 with this stack the best way. But I still think that at least
> everything, that can be done in firmware without any feature loss or
> limit should be done in firmware.

s/firmware/firmwares of prism54,acx,atheros,ralink,etc,etc/

It's bug^Wcode duplication.

> Other things will surely need additional discussion how far it makes
> sense or not to integrate them in the firmware, but that's too far away
> at the moment to discuss it the way it should be.
--
vda