[Prism54-devel] Prism Nitro Support

[Luis R. Rodriguez]

--QnBU6tTI9sljzm9u
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Wed, Mar 03, 2004 at 04:51:19PM +0800, Rodel Miguel wrote:
> Hi!
>=20
> I would like to ask if my solution would suffice prism nitro support whil=
e frameburst is not yet integrated with wireless tools.  I just inserted th=
e following line in isl_ioctl.c specifically in  prism54_mib_init function:
>=20
> 	/* set prism nitro support - rodel */
>         MGT_SET_REQUEST_U32_NOCACHE(priv, DOT11_OID_MAXFRAMEBURST, init_b=
urst);
>=20
>         /* set card profile - rodel */
>         MGT_SET_REQUEST_U32_NOCACHE(priv, DOT11_OID_PROFILES, init_profil=
e);

If that's how you add "Prism Nitro" support then yes, that
would be a proper place to put it to start it @ init time.=20

Questions:

0. what is "prism nitro" ?
1. what's initial value are you using for init_burst and why?
2. what is the units of DOT11_OID_MAXFRAMEBURST?
3. why are you setting the profile afterwards?
4. was this a feature available for all versions of the firmware?
5. is frameburst just an 802.11g feature? Ie, if set would a STA ASSOC well
with 802.11b APs, and if set on the AP would it allow for non "frame
burst" capable STAs to ASSOC?

> would the card be set to the specified frameburst whenever the driver is =
loaded?   =20

Yes.

> Thank you very much.

Thank you.

	Luis
=09
--=20
GnuPG Key fingerprint =3D 113F B290 C6D2 0251 4D84  A34A 6ADD 4937 E20A 525E

--QnBU6tTI9sljzm9u
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFAR74fat1JN+IKUl4RAhdaAKCqnEbfW2OtLBFBFhQpFRKp3+lL4QCghuDW
k165Zbn2/t0iWQUdf36i2tk=
=ZQ59
-----END PGP SIGNATURE-----

--QnBU6tTI9sljzm9u--