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

--===============1580736800==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-dNdCldxCoMua3EbYk2XP"


--=-dNdCldxCoMua3EbYk2XP
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Mo, 2005-09-05 at 08:13 +0300, Denis Vlasenko wrote:
> On Monday 05 September 2005 00:03, Maximilian Engelhardt wrote:
> >
> > I disagree with this. I think the firmware should to as much as possibl=
e
> > to avoid CPU load. On the one hand this gives greater performance, on
> > the other hand it can perhaps save some power on laptops. And if we hav=
e
> > a fully open source firmware we will be able to implement everything we
> > want.
>=20
> I agree that WEP/AES in firmware for bulk data may make some difference
> and may make sense, other things would not.
>=20
> 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.
>=20
> After all, people had difficulties detecting impact of HZ=3D1000
> versus HZ=3D100, 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.
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.

Maxi

--=-dNdCldxCoMua3EbYk2XP
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: This is a digitally signed message part

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBDHfrlOimwv528XGERAu9LAJ995UNeQ/dUl/WuC0t0lXcLKnBGIwCgs3lY
99bIo1aby0ok/AS4K3Zwbc0=
=MF58
-----END PGP SIGNATURE-----

--=-dNdCldxCoMua3EbYk2XP--

--===============1580736800==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Prism54-devel mailing list
[email protected]
http://prism54.org/mailman/listinfo/prism54-devel

--===============1580736800==--