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

--===============1173465880==
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature";
	boundary="=-fVaMy+XneIeat3nqWuR+"


--=-fVaMy+XneIeat3nqWuR+
Content-Type: text/plain
Content-Transfer-Encoding: quoted-printable

On Mi, 2005-08-31 at 16:32 +0300, Denis Vlasenko wrote:
>=20
> This could (should) be achieved with...
>=20
> > - being more resistant to possible future protocol and hardware changes=
 - if=20
> > Prism54 didn't rely on FullMAC that much, support for the 3886 and 3887=
 would=20
> > have been much more easy (probably as simple as cutting down the firmwa=
re=20
> > code and offloading operations to the host).
>            ^^^^^^^^^^^^^^^^^^^^^
> exactly this!
>=20
> Actually, what is the minimum needed from a wireless card?
>=20
> * ability to tx an arbitrary packet at given rate/modulation
>   (automatic retry and/or rate fallback is nice but not 100% reqd)
> * ability to autonomously tx very low level control stuff
>   like sending ACKs (it's time critical)
> * tune into given channel
> * rx packets
> * DMA packets to/from host via PCI / transfer data over USB / whatever
> * anything else?
>=20
> Beacons, association, even WEP and scanning - all can be done by host OS.
> This also will give us nice well debugged common 802.11 stack.
>=20
> Thus bare minimum firmware can be rather dumb (and thus easier to write/d=
ebug).
> Maybe we (wireless crowd, not just Prism54 project) should aim
> exactly to such "bare minimum fw" approach?

I disagree with this. I think the firmware should to as much as possible
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 have
a fully open source firmware we will be able to implement everything we
want.
I don't think building and minimum firmware is wrong, I'm sure it will
be very good for debugging (as you mentioned above), but I think a
"bigger" firmware should be used by a final driver for my above
mentioned reasons.

Maxi

--=-fVaMy+XneIeat3nqWuR+
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)

iD8DBQBDG2E0Oimwv528XGERAsWrAKCk4N5Iy6Jfw75ZH4u/mmOkCG747wCfWCv/
kM6JARRFIyMcB+g+dCbHZKU=
=rTxV
-----END PGP SIGNATURE-----

--=-fVaMy+XneIeat3nqWuR+--

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

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

--===============1173465880==--