[Prism54-devel] Prism54-devel digest, Vol 1 #47 - 13 msgs

prism54-devel-request@prism54.org prism54-devel-request@prism54.org
Sat, 20 Dec 2003 02:03:01 +0000


This is a multi-part message in MIME format.

------------=_3FE3AB61.80321BAA
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

---- Start SpamAssassin results
13.80 points, 5 required;
*  1.5 -- From: does not include a real name
* -0.5 -- BODY: Contains what looks like an email attribution
*  5.0 -- BODY: Spam is 100% natural?!
*  0.5 -- BODY: Offers a full refund
*  7.0 -- BODY: Online Pharmacy
* -0.3 -- BODY: Contains twice quoted reply
*  2.5 -- BODY: Message is 0% to 10% HTML
*  2.0 -- BODY: HTML included in message
* -0.5 -- BODY: Contains what looks like a patch from diff -u
* -0.5 -- BODY: Contains what looks like a quoted email text
* -0.5 -- Email came from some known mailing list software
* -2.9 -- Contains a PGP-signed message
*  0.5 -- Asks you to click below

---- End of SpamAssassin results



------------=_3FE3AB61.80321BAA
Content-Type: message/rfc822; x-spam-type=original
Content-Description: original message before SpamAssassin
Content-Disposition: inline
Content-Transfer-Encoding: 8bit

Received: from mcgrof.com (66.139.77.166)
  by wks1.stratum8.com with SMTP; 20 Dec 2003 01:52:28 -0000
Received: from localhost (localhost [127.0.0.1])
	by mcgrof.com (Postfix) with ESMTP
	id 8EA8C40C540; Sat, 20 Dec 2003 02:04:01 +0000 (UTC)
Date: Sat, 20 Dec 2003 02:03:01 +0000
Message-ID: <20031220020301.21976.40568.Mailman@localhost>
From: prism54-devel-request@prism54.org
Subject: Prism54-devel digest, Vol 1 #47 - 13 msgs
Reply-To: prism54-devel@prism54.org
X-Mailer: Mailman v2.0.11
MIME-version: 1.0
Content-type: text/plain
To: prism54-devel@prism54.org
Sender: prism54-devel-admin@prism54.org
Errors-To: prism54-devel-admin@prism54.org
X-BeenThere: prism54-devel@prism54.org
X-Mailman-Version: 2.0.11
Precedence: bulk
List-Help: <mailto:prism54-devel-request@prism54.org?subject=help>
List-Post: <mailto:prism54-devel@prism54.org>
List-Subscribe: <http://prism54.org/mailman/listinfo/prism54-devel>,
	<mailto:prism54-devel-request@prism54.org?subject=subscribe>
List-Id: Development of prism54 802.11 linux kernel driver <prism54-devel.prism54.org>
List-Unsubscribe: <http://prism54.org/mailman/listinfo/prism54-devel>,
	<mailto:prism54-devel-request@prism54.org?subject=unsubscribe>
List-Archive: <http://prism54.org/pipermail/prism54-devel/>

Send Prism54-devel mailing list submissions to
	prism54-devel@prism54.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://prism54.org/mailman/listinfo/prism54-devel
or, via email, send a message with subject or body 'help' to
	prism54-devel-request@prism54.org

You can reach the person managing the list at
	prism54-devel-admin@prism54.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Prism54-devel digest..."


Today's Topics:

   1. PSK-WPA setup in PrismGT AP mode (Anjan)
   2. Re: problems with iwlist scan (frank-prism54@mattzz.dyndns.org)
   3. Re: problems with iwlist scan (Brian Bothwell)
   4. Patch to control output power (iwconfig txpower) (kaleda)
   5. Re: problems with iwlist scan (frank-prism54@mattzz.dyndns.org)
   6. Re: problems with iwlist scan (frank-prism54@mattzz.dyndns.org)
   7. Re: problems with iwlist scan (Luis R. Rodriguez)
   8. Re: problems with iwlist scan (frank-prism54@mattzz.dyndns.org)
   9. Re: Re: Linux headers ISL3890 (Luis R. Rodriguez)
  10. Xanax, Valium at low low prices! Josefa Bender iq hxjue (Josefa Bender)
  11. Re: PSK-WPA setup in PrismGT AP mode (Rafiq Shaikh)
  12. speed up low carb weight |oss 6b  ejuw (Joesph Burns)
  13. 802.11g Testing mode command ?? (Barret,Lee)

--__--__--

Message: 1
Date: Fri, 19 Dec 2003 14:41:31 +0530
From: Anjan <anjan@alumnux.com>
To: prism54-devel@prism54.org
Subject: [Prism54-devel] PSK-WPA setup in PrismGT AP mode

Hi
   Anyone out there can help me setup WAP support in PrismGT. Actually I 
require to setup PrismGT AP in PSK-WPA mode for my SOHO.
   What OIDs should I use and how do I use them to setup PSK (Pre Shared 
Key) mode and TKIP encryption key, required for WPA SOHO setup.
   An early reply would be appreciated.

- Anjan




--__--__--

Message: 2
Date: Fri, 19 Dec 2003 12:28:46 +0100
From: frank-prism54@mattzz.dyndns.org
To: prism54-devel@prism54.org
Subject: Re: [Prism54-devel] problems with iwlist scan

On Thu, Dec 18, 2003 at 04:18:32PM -0800, Brian Bothwell wrote:
> Try: iwlist eth0 scanning

This did not help. 'scan' is the shortcut for 'scanning' isn't it?

I kept iwlist the same and exchanged only the prism54.o module.

Either the sequence(order) of commands is wrong or the
latest cvs driver is broken.

best regards
  Frank


--__--__--

Message: 3
Date: Fri, 19 Dec 2003 04:53:36 -0800
From: Brian Bothwell <sysrage@sysrage.net>
To: prism54-devel@prism54.org
Subject: Re: [Prism54-devel] problems with iwlist scan

--Signature=_Fri__19_Dec_2003_04_53_36_-0800_giv9pU5AECGd07oP
Content-Type: text/plain; charset=US-ASCII
Content-Disposition: inline
Content-Transfer-Encoding: 7bit

Sorry, i thought the command was changed from scan to scanning because one build of the driver I used only worked when i used scanning.

I just compiled stable 2.6.0 with the latest CVS version of the prism54 driver yesterday (Dec. 18) and they both work perfectly for me. The recent changes to the driver are great. Allow mode changes (between monitor and managed) to work perfectly. Previously it would crash the driver or the entire kernel for me.

Not sure what your problem is, sorry. However on a total random train of thought. In my dmesg output, I see the follwing:

eth0: islpci_open()
eth0: resetting device...
eth0: uploading firmware...
cs: IO port probe 0x0c00-0x0cff: clean.
cs: IO port probe 0x0100-0x04ff: excluding 0x3f8-0x3ff
cs: IO port probe 0x0a00-0x0aff: clean.
eth0: firmware uploaded done, now triggering reset...
eth0: prism54_mib_init()
spurious 8259A interrupt: IRQ7.
eth0: done with prism54_mib_init()! -- Client Managed mode

I don't see any prism54_mib_init() in what you pasted. I'm not sure if that only happens when setting the mode of the driver. My initialization script does the following:

ifconfig eth0 up
iwconfig eth0 essid "myid"
iwconfig eth0 key firstkey
iwconfig eth0 key [2] secondkey
iwconfig eth0 key [3] thirdkey
iwconfig eth0 key [4] fourthkey
dhcpcd eth0

I assume setting the essid automatically sets the mode to managed. None of this probably helps at all. Sorry. Wish I could help more.

On Fri, 19 Dec 2003 12:28:46 +0100
frank-prism54@mattzz.dyndns.org wrote:

> On Thu, Dec 18, 2003 at 04:18:32PM -0800, Brian Bothwell wrote:
> > Try: iwlist eth0 scanning
> 
> This did not help. 'scan' is the shortcut for 'scanning' isn't it?
> 
> I kept iwlist the same and exchanged only the prism54.o module.
> 
> Either the sequence(order) of commands is wrong or the
> latest cvs driver is broken.
> 
> best regards
>   Frank
> 
> _______________________________________________
> Prism54-devel mailing list
> Prism54-devel@prism54.org
> http://prism54.org/mailman/listinfo/prism54-devel
> 

--Signature=_Fri__19_Dec_2003_04_53_36_-0800_giv9pU5AECGd07oP
Content-Type: application/pgp-signature

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

iD8DBQE/4vTSXFoaje2SLvERAqRIAJ9rhensyptF9eDXV+F0Je7FdRqeMgCfXX5d
3nTAxTDNuGJEr6qo60XRAa4=
=/Utb
-----END PGP SIGNATURE-----

--Signature=_Fri__19_Dec_2003_04_53_36_-0800_giv9pU5AECGd07oP--

--__--__--

Message: 4
From: kaleda <gadeanta@soften.ktu.lt>
To: prism54 <prism54-devel@prism54.org>
Date: Fri, 19 Dec 2003 15:25:25 +0200
Subject: [Prism54-devel] Patch to control output power (iwconfig txpower)

Made a patch to manage output power.
Currently only fixed value is supported
(I think the main in AP mode).
Still don't know a way to turn off the radio (anyone knows it) ?

Kaleda

diff -uNr prism54.orig/ksrc/isl_ioctl.c prism54/ksrc/isl_ioctl.c
--- prism54.orig/ksrc/isl_ioctl.c	2003-12-17 08:16:38.000000000 +0200
+++ prism54/ksrc/isl_ioctl.c	2003-12-19 14:04:28.000000000 +0200
@@ -880,6 +880,9 @@
 	range->max_retry = 65535;
 	range->min_r_time = 1024;
 	range->max_r_time = 65535 * 1024;
+	
+	/* txpower is supported in dBm's */
+	range->txpower_capa = IW_TXPOW_DBM;
 
 	/* Request the device for the supported frequencies
 	 * not really revelant since some devices will report the 5 GHz band
@@ -1638,6 +1641,47 @@
 	return 0;
 }
 
+
+int prism54_get_txpower(struct net_device *ndev, struct iw_request_info
*info,
+		struct iw_param *vwrq, char *extra)
+{
+	islpci_private *priv = ndev->priv;
+	u32 u;
+	memset(vwrq, 0, sizeof(struct iw_param));
+	MGT_GET_REQUEST_U32(priv, OID_INL_OUTPUTPOWER, &u, fixedtxpower);
+	// intersil firmware operates in 0.25 dBm (1/4 dBm)
+	vwrq->value = u / 4;
+	vwrq->fixed = 1;	// fixed value is set
+	// radio is not turned of
+	// btw: how is possible to turn off only the radio ?
+	vwrq->disabled = 0; 
+	return 0;
+}	//	isl_ioctl_gettxpow
+
+int prism54_set_txpower(struct net_device *ndev, struct iw_request_info
*info,
+		struct iw_param *vwrq, char *extra)
+{
+	islpci_private *priv = ndev->priv;
+	// intersil firmware operates in 0.25 dBm (1/4)
+	u32 u = vwrq->value;
+	u *= 4;
+	if (vwrq->disabled) {
+		// don't know how to disable radio
+		printk(KERN_DEBUG "%s: %s() disabling radio is not yet supported.\n",
priv->ndev->name, __FUNCTION__);
+		return -ENOTSUPP;
+	} else if (vwrq->fixed)	{
+		// currently only fixed value is supported
+		MGT_SET_REQUEST_U32(priv, OID_INL_OUTPUTPOWER , u, fixedtxpower);
+		return 0;
+	} else {
+		printk(KERN_DEBUG "%s: %s() auto power will be implemented later.\n",
+				priv->ndev->name, __FUNCTION__);
+		return -ENOTSUPP;
+	}
+}	//	isl_ioctl_settxpow
+
+
+
 int
 prism54_reset(struct net_device *ndev, struct iw_request_info *info,
 	      __u32 *uwrq, char *extra)
diff -uNr prism54.orig/ksrc/isl_ioctl.h prism54/ksrc/isl_ioctl.h
--- prism54.orig/ksrc/isl_ioctl.h	2003-12-17 08:16:38.000000000 +0200
+++ prism54/ksrc/isl_ioctl.h	2003-12-19 10:36:12.000000000 +0200
@@ -94,6 +94,10 @@
 		       struct iw_point *, char *);
 int prism54_get_encode(struct net_device *, struct iw_request_info *,
 		       struct iw_point *, char *);
+int prism54_set_txpower(struct net_device *, struct iw_request_info *,
+		     struct iw_param *, char *);
+int prism54_get_txpower(struct net_device *, struct iw_request_info *,
+		     struct iw_param *, char *);
 
 int prism54_reset(struct net_device *, struct iw_request_info *,
 		  __u32 *, char *);
@@ -189,8 +193,8 @@
 	(iw_handler) prism54_get_rts,	/* SIOCGIWRTS */
 	(iw_handler) prism54_set_frag,	/* SIOCSIWFRAG */
 	(iw_handler) prism54_get_frag,	/* SIOCGIWFRAG */
-	(iw_handler) NULL,	/* SIOCSIWTXPOW */
-	(iw_handler) NULL,	/* SIOCGIWTXPOW */
+	(iw_handler) prism54_set_txpower,	/* SIOCSIWTXPOW */
+	(iw_handler) prism54_get_txpower,	/* SIOCGIWTXPOW */
 	(iw_handler) prism54_set_retry,	/* SIOCSIWRETRY */
 	(iw_handler) prism54_get_retry,	/* SIOCGIWRETRY */
 	(iw_handler) prism54_set_encode,	/* SIOCSIWENCODE */
diff -uNr prism54.orig/ksrc/islpci_dev.h prism54/ksrc/islpci_dev.h
--- prism54.orig/ksrc/islpci_dev.h	2003-12-17 08:16:39.000000000 +0200
+++ prism54/ksrc/islpci_dev.h	2003-12-19 10:19:55.000000000 +0200
@@ -85,6 +85,7 @@
 	volatile u32 shortretries;
 	volatile u32 longretries;
 	volatile u32 maxtxlifetime;
+	volatile u32 fixedtxpower;
 
 	struct semaphore sem;
 };
diff -uNr prism54.orig/ksrc/islpci_mgt.h prism54/ksrc/islpci_mgt.h
--- prism54.orig/ksrc/islpci_mgt.h	2003-12-17 08:16:39.000000000 +0200
+++ prism54/ksrc/islpci_mgt.h	2003-12-19 13:59:17.000000000 +0200
@@ -79,6 +79,8 @@
 #define OID_INL_COMPONENT_ID                    0xFF020007
 #define OID_INL_CONFIG                          0xFF020008
 #define OID_INL_DOT11D_CONFORMANCE              0xFF02000C
+#define	OID_INL_OUTPUTPOWER 					0xFF02000F
+
 
 /* The dot11d conformance level configures the 802.11d conformance
levels.
  * The following conformance levels exist:*/


--__--__--

Message: 5
Date: Fri, 19 Dec 2003 15:01:25 +0100
From: frank-prism54@mattzz.dyndns.org
To: prism54-devel@prism54.org
Subject: Re: [Prism54-devel] problems with iwlist scan

On Fri, Dec 19, 2003 at 04:53:36AM -0800, Brian Bothwell wrote:

> Sorry, i thought the command was changed from scan to scanning
> because one build of the driver I used only worked when i used
> scanning.
> I just compiled stable 2.6.0 with the latest CVS version of the
> prism54 driver yesterday (Dec. 18) and they both work perfectly for
> me. The recent changes to the driver are great. Allow mode changes
> (between monitor and managed) to work perfectly. Previously it would
> crash the driver or the entire kernel for me.

Brian,

Thank you for your support! I tried now 2.6.0-test11 too, but still no
sign of life with latest CVS. The messages now:

$ modprobe prism54


Dec 19 14:37:48 fantasio kernel: Loaded prism54 driver, version 1.0.2.2

$ ifconfig eth1 up

Dec 19 14:39:25 fantasio kernel: eth1: islpci_open()
Dec 19 14:39:25 fantasio kernel: eth1: resetting device...
Dec 19 14:39:25 fantasio kernel: eth1: uploading firmware...

and on stdout:

SIOCSIFFLAGS: Resource temporarily unavailable

I was not able to try 2.6.0-test11 with the cvs version of end
november as I could not remove the module. I found no switch enabling
this?

$ rmmod prism54
FATAL: Kernel does not have unload support.



Brian, what kind of card are you using? Is it PCI(SMC2802W) too?

best regards
  Frank








--__--__--

Message: 6
Date: Fri, 19 Dec 2003 15:13:00 +0100
From: frank-prism54@mattzz.dyndns.org
To: prism54-devel@prism54.org
Subject: Re: [Prism54-devel] problems with iwlist scan

Uh sorry, I forgot to mount sysfs as stated in the doc. So now it
looks like:

$ ifconfig eth1 up

Dec 19 15:02:28 fantasio kernel: eth1: islpci_open()
Dec 19 15:02:28 fantasio kernel: eth1: resetting device...
Dec 19 15:02:28 fantasio kernel: eth1: uploading firmware...
Dec 19 15:02:29 fantasio kernel: eth1: firmware uploaded done, now triggering reset...


$ iwlist eth1 scanning

eth1      Failed to read scan data : Invalid argument


But I still do not see a message like

 prism54_mib_init()


regards
  Frank




--__--__--

Message: 7
Date: Fri, 19 Dec 2003 10:54:53 -0500 (EST)
From: "Luis R. Rodriguez" <mcgrof@ruslug.rutgers.edu>
To: frank-prism54@mattzz.dyndns.org
Cc: prism54-devel@prism54.org
Subject: Re: [Prism54-devel] problems with iwlist scan


> But I still do not see a message like
>
>  prism54_mib_init()

That in essence is the problem.

ifconfig eth1 down && dmesg -c
rmmod prism54 && dmesg -c
modprobe prism54 && dmesg -c
ifconfig eth1 up && dmesg -c
iwlist eth1 scanning && dmesg -c

See if you see it when following those steps

	Luis


--__--__--

Message: 8
Date: Fri, 19 Dec 2003 17:44:33 +0100
From: frank-prism54@mattzz.dyndns.org
To: "Luis R. Rodriguez" <mcgrof@ruslug.rutgers.edu>
Cc: prism54-devel@prism54.org
Subject: Re: [Prism54-devel] problems with iwlist scan

On Fri, Dec 19, 2003 at 10:54:53AM -0500, Luis R. Rodriguez wrote:
> 
> > But I still do not see a message like
> >
> >  prism54_mib_init()
> 
> That in essence is the problem.
> 
> ifconfig eth1 down && dmesg -c
> rmmod prism54 && dmesg -c
> modprobe prism54 && dmesg -c
> ifconfig eth1 up && dmesg -c
> iwlist eth1 scanning && dmesg -c
> 
> See if you see it when following those steps
> 
> 	Luis
> 
Luis,

I saw now a message:
 hotplug reports a wrong irq. Working around

and I found a new part in the code which reassigns the irq under
certain conditions. I commented this out and it works again.

fantasio:~/prism54-ng/ksrc$ cvs diff -u islpci_hotplug.c
Index: islpci_hotplug.c
===================================================================
RCS file: /var/lib/cvs/prism54-ng/ksrc/islpci_hotplug.c,v
retrieving revision 1.44
diff -u -r1.44 islpci_hotplug.c
--- islpci_hotplug.c    16 Dec 2003 20:16:49 -0000      1.44
+++ islpci_hotplug.c    19 Dec 2003 16:40:40 -0000
@@ -142,12 +142,12 @@
        }
 
        /* The irq reported by the hotplug system is sometimes wrong */
-       pci_read_config_byte(pdev, PCI_INTERRUPT_LINE, &irq);
-       if (pdev->irq != irq){
-               printk(KERN_ERR "%s: hotplug reports a wrong irq. Working around !\n",
-                              DRV_NAME);
-               pdev->irq = irq;
-       }
+       //      pci_read_config_byte(pdev, PCI_INTERRUPT_LINE, &irq);
+       //if (pdev->irq != irq){
+       //      printk(KERN_ERR "%s: hotplug reports a wrong irq. Working around !\n",
+       //                     DRV_NAME);
+       //      pdev->irq = irq;
+       //}

If you want to know what is strange in my system, please ask some
detailed questions. I do not know much about ACPI and such.

best regards
  Frank

--__--__--

Message: 9
Date: Fri, 19 Dec 2003 12:07:27 -0500 (EST)
From: "Luis R. Rodriguez" <mcgrof@ruslug.rutgers.edu>
To: Rients Brandsma <RBRANDSMA@globespanvirata.com>
Cc: Tim de Waal <TWAAL@globespanvirata.com>,
	<prism54-devel@prism54.org>
Subject: Re: [Prism54-devel] Re: Linux headers ISL3890


Hello Rients,

we have been progressing really well and are looking into concentrating
on a stable release to be included into the Linux Stock Kernel. In order
to do so we really need bloboid.h's license changed to a Free License one.
Following the tradition that was used for the LDDK, this would be GPL.

It seems our list has been with corporate support for the LDDK too. Since
we don't haven't had NDA clearance to get the RM034 we are falling short
in assisting users/developers. I'm sure there are also more OIDs which we
can probably make good use of. Being this the case, would it be possible
for our deverloper circle to get NDA clearance for the RM034? We
currently consist of three main developers. Getting clearance to be
allowed to receive the latest firmware and to redistribute it would also
be great.

A simple reply would be more than appreciated,

Regards, and Happy Holidays,

	Luis

On Wed, 29 Oct 2003, Luis R. Rodriguez wrote:

>
> Hello Rients,
>
> (I'm CC'ing our development team)
>
> Not sure if you have checked our most recent work but we are progressing a
> lot. Here is our latest patch:
>
> http://prism54.org/patches/patch-2.4.23-pre8-prism54-1.0.2.2.bz2
>
> Our new project page:
> http://prism54.org
>
> We were wondering if you have any update on this. It's been a while
> since we requested the license change. Last time we talked you had infomed
> me that my assumptions on that the License on those two files were
> incorrect was in fact accurate and that they would be updated. All the other License
> headers on *all* the other files were GPL'd.
>
> We would also like permission to redistribute the firmware. We
> realize we may not obtain them as GPL but this is understood among
> us. Having permission to redistribute the RM034 spec among developers would also be
> a great contribution. Your assistance won't go unnoticed, I assure you.
>
> With best regards,
> 	Luis R. Rodriguez
>
> On Tue, 7 Oct 2003, Rients Brandsma wrote:
>
> > Luis,
> >
> >
> >
> > I was forwarded your question with respect to the header
> >
> > files contained in the Linux DDK.
> >
> >
> >
> > We are aware of the fact that the current header files delivered in the
> > Linux DDK
> >
> > have a wrong and outdated copyright statement. We are currently in the
> > process
> >
> > to change these, and are waiting for final review and guidance from our
> > legal department.
> >
> >
> >
> > I am confident this will be solved soon.
> >
> >
> >
> >
> >
> > Regards,
> >
> > Rients Brandsma - Senior Product Manager
> >
> > Email: rbrandsma@globespanvirata.com
> >
> > Tel: +31-30-2259832 -  Mob: +31-653333885
> >
> >
> >
> > Globespan B.V. - Rembrandtlaan 1a
> >
> > 3723 BG Bilthoven - The Netherlands
> >
> >
>
> _______________________________________________
> Prism54-devel mailing list
> Prism54-devel@prism54.org
> http://prism54.org/mailman/listinfo/prism54-devel
>


--__--__--

Message: 10
From: "Josefa Bender" <bktzuge91a@yahoo.com>
Reply-To: "Josefa Bender" <bktzuge91a@yahoo.com>
To: <prism54-devel-request@prism54.org>, <prism54-devel@prism54.org>,
	<prism54-users-request@prism54.org>, <prism54-users@prism54.org>
Date: Fri, 19 Dec 03 13:55:04 GMT
Subject: [Prism54-devel] Xanax, Valium at low low prices! Josefa Bender iq hxjue


--._D2A51._FB.5.E3
Content-Type: text/plain;
Content-Transfer-Encoding: quoted-printable

NEW! ONLINE PHARMACY FOR YOUR PAIN RELIEF

We offer:

- Xanax
- Valium
- Somo
 
and many more...

We Ship Worldwide! To All Countries.

Click Here!
http://www.rx-world.biz/r116/htm/index.htm




See you soon!!




bye
http://www.yourremedy.biz/r/r.htm
















pqscnlvqbjlh yg jdlzfkwkfdsl
rgfplf

--._D2A51._FB.5.E3--


--__--__--

Message: 11
Date: Fri, 19 Dec 2003 11:07:15 -0800
From: Rafiq Shaikh <rafiq.shaikh@analog.com>
To: Anjan <anjan@alumnux.com>
Cc: prism54-devel@prism54.org
Subject: Re: [Prism54-devel] PSK-WPA setup in PrismGT AP mode

Hi  Anjan,

I think following oids will be used for WPA support on PRISM-GT.
OID_ATTACHMENT
OID_EAPUNAUTHSTA
OID_EAPAUTHSTA
OID_STAKEY
OID_STASC
OID_MICFAILURE
Anyone out there who has already implemented WPA please correct me if I 
am wrong.

Regards,
-Rafiq.


Anjan wrote:

> Hi
>   Anyone out there can help me setup WAP support in PrismGT. Actually 
> I require to setup PrismGT AP in PSK-WPA mode for my SOHO.
>   What OIDs should I use and how do I use them to setup PSK (Pre 
> Shared Key) mode and TKIP encryption key, required for WPA SOHO setup.
>   An early reply would be appreciated.
>
> - Anjan
>
>
>
> _______________________________________________
> Prism54-devel mailing list
> Prism54-devel@prism54.org
> http://prism54.org/mailman/listinfo/prism54-devel
>
>


--__--__--

Message: 12
From: "Joesph Burns" <h12zstxs@postmaster.co.uk>
Reply-To: "Joesph Burns" <h12zstxs@postmaster.co.uk>
To: <prism54-devel@prism54.org>, <anonymous@prism54.org>
Date: Sat, 20 Dec 03 20:35:10 GMT
Subject: [Prism54-devel] speed up low carb weight |oss 6b  ejuw


--748AF_._BFB61901AF30
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable

<html>
<body>
<br>
Sick of fad diets? Get the solution that millions of others have,
procitravin. Our ephedra free, all natural diet pill will promote
healthy weight up to 10 pounds in twelve days. If it doesn't work you'll
get a full refund.
<P><a href=3D"http://www.procitravin.com/index15.html"><img border=3D"0" s=
rc=3D"http://www.procitravin.com/graphics/mailer_citravin2.jpg"></a><P>
<a href=3D"http://www.procitravin.com/index15.html">http://www.procitravin=
com/index15.html</a><P>
<P>gztroop
</body>
</html>lncs cegwsd ao p
zdof

--748AF_._BFB61901AF30--


--__--__--

Message: 13
From: "Barret,Lee" <zhuwei@ms21.hinet.net>
To: <prism54-devel@prism54.org>
Subject: [Prism54-devel] 802.11g Testing mode command ??
Date: Sat, 20 Dec 2003 09:51:41 +0800

Hi,
    Anyone out there can help me to control TRANSMISSION. i need this
command to measure RF side.
Here is the test mode command in 802.11b (prism 2.5, RM025), this command
can to contorl mac-layer
sending continuous stream.
[TME:CONTINUOUS TRANSMIT (in prism2.5 RM025)
The firmware starts sending a continuous stream to facilitate manufacturing
adjustments of the
modem. The transmission of the continuous preamble must be stopped with the
Stop command.
Command: 0e38
Parameter: Repetitive Transmission Data (MPDU) Pattern
This command provides a mechanism for placing the radio into a continuous
transmission state.
When invoking the command in Testware the 16-bit parameter supplied is used
as a repetitive data
pattern during transmission (i.e., a parameter of a010 would result in an
MPDU that looks like
10100000000100001010000000010000...). This command must be terminated by the
Stop Test
command (0f38 without parameters). If a new transmit sequence is desired,
you must terminate
the current Continuous TX (0f38) and then invoke again with the new transmit
sequence
parameter.]

IF Prism-GT had the same command was to contorl transmission, Can you tell
me?

Best regards.



--__--__--

_______________________________________________
Prism54-devel mailing list
Prism54-devel@prism54.org
http://prism54.org/mailman/listinfo/prism54-devel


End of Prism54-devel Digest

------------=_3FE3AB61.80321BAA--


*** Qmail-Scanner Quarantine Envelope Details Begin ***
X-Qmail-Scanner-Mail-From: "prism54-devel-admin@prism54.org" via fw
X-Qmail-Scanner-Rcpt-To: "yh_lin@sdesigns.com"
X-Qmail-Scanner: 1.20rc1 (spamassassin: 2.55.  SPAM Found. Processed in 3.919793 secs)
Quarantine-Description: SpamAssassin thinks this message is spam
*** Qmail-Scanner Envelope Details End ***