getscanlist command redundant?

[Frank Huang]

Marcelo,

getscanlist will get same result as "iwlist ethx scan" except that
"iwlist ethX scan" will trigger scanning before result is returned.

getscantable could get more information (e.g. TSF) than getscanlist. The
major purpose is for Roaming and CCX, as what Ronak mentioned early.

Regards,

Frank
-----Original Message-----
From: libertas-dev-bounces at lists.infradead.org
[mailto:libertas-dev-bounces at lists.infradead.org] On Behalf Of Marcelo
Tosatti
Sent: Thursday, November 16, 2006 3:24 PM
To: Ronak Chokshi
Cc: Dan Williams; Marcelo Tosatti; Alan Cunningham;
libertas-dev at lists.infradead.org
Subject: Re: getscanlist command redundant?

On Thu, Nov 16, 2006 at 10:04:13AM -0800, Ronak Chokshi wrote:
> Dan and Marcelo,
> Your comments are pretty much accurate. extscan is used to scan for a
> particular SSID and getscanlist is actually is get the latest scan
> results from the scan buffers in the driver. Unlike, 'iwlist ethX
scan',
> issuing getscanlist does not really issue a scan - it just gets the
> latest scan results from the drivers.
> 
> As you can probably envision, these commands are used for roaming use
> cases. For example, application would use the getscanlist to get the
> latest set of probe responses or would use the extscan to actually
scan
> for one particular AP.

Ronak,

What is the functional difference between getscanlist and getscantable? 

They appear to provide the same information to me.

Thanks

_______________________________________________
libertas-dev mailing list
libertas-dev at lists.infradead.org
http://lists.infradead.org/mailman/listinfo/libertas-dev