linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@iki.fi>
To: Dan Williams <dcbw@redhat.com>
Cc: Marcel Holtmann <marcel@holtmann.org>,
	Bob Copeland <me@bobcopeland.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org, mabbaswireless@gmail.com
Subject: Re: [PATCH v2 0/3] mac80211 suspend/resume
Date: Fri, 09 Jan 2009 09:55:02 +0200	[thread overview]
Message-ID: <87skns29t5.fsf@litku.valot.fi> (raw)
In-Reply-To: <1231432778.21643.40.camel@localhost.localdomain> (Dan Williams's message of "Thu\, 08 Jan 2009 11\:39\:38 -0500")

Dan Williams <dcbw@redhat.com> writes:

>> Having the suspend scripts to tell NM to disconnect is just not a good
>> solution and especially in the embedded world this is a broken design
>> concept.
>
> Right; the missing piece is pushing the necessary roaming support down
> to the supplicant and letting it make the decisions about what to
> connect to.  There's a few things that I need from the supplicant before
> I can simply push the entire config set down from NM and let it go wild:
>
> 1) A 'frequency' config item that works in infrastructure mode too,
> ignoring any AP not matching that frequency

Just out of curiosity, why this feature is needed? I can understand
hard-coding bssid, but I don't understand the use for hard-coding the
frequency.

-- 
Kalle Valo

  reply	other threads:[~2009-01-09  7:55 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-15  3:50 [PATCH v2 0/3] mac80211 suspend/resume Bob Copeland
2008-12-15 10:14 ` Johannes Berg
2008-12-15 15:22   ` Dan Williams
2008-12-15  9:28     ` Luis R. Rodriguez
2008-12-17 18:21     ` Bob Copeland
2008-12-23 20:30       ` Johannes Berg
2008-12-24  5:49         ` Bob Copeland
2008-12-24  7:16           ` Marcel Holtmann
2009-01-06 16:45             ` Dan Williams
2009-01-06 17:07               ` Bob Copeland
2009-01-06 17:14                 ` Johannes Berg
2009-01-06 17:35                   ` Bob Copeland
2009-01-06 17:43                     ` Johannes Berg
2009-01-06 18:01                       ` Bob Copeland
2009-01-06 18:16                         ` Johannes Berg
2009-01-06 17:12               ` Marcel Holtmann
2009-01-06 18:52                 ` Dan Williams
2009-01-06 19:36                   ` Marcel Holtmann
2009-01-06 20:05                     ` Johannes Berg
2009-01-09 23:53                       ` Tomas Winkler
2009-01-10  9:27                         ` Johannes Berg
2009-01-11 11:11                           ` Tomas Winkler
2009-01-11 14:40                             ` Bob Copeland
2009-01-08 16:39                     ` Dan Williams
2009-01-09  7:55                       ` Kalle Valo [this message]
2009-01-09 16:35                         ` Dan Williams
2009-01-09 16:44                           ` Kalle Valo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87skns29t5.fsf@litku.valot.fi \
    --to=kalle.valo@iki.fi \
    --cc=dcbw@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mabbaswireless@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=me@bobcopeland.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).