linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Anna Neal <anna@cozybit.com>,
	linux-wireless@vger.kernel.org, libertas-dev@lists.infradead.org,
	Jeff Garzik <jeff@garzik.org>
Subject: Re: [RFC] libertas: iwpriv commands to configure fine grained wake-on-(w)lan
Date: Fri, 31 Oct 2008 15:35:04 -0400	[thread overview]
Message-ID: <20081031193504.GF4310@tuxdriver.com> (raw)
In-Reply-To: <1224620028.15561.10.camel@localhost.localdomain>

On Tue, Oct 21, 2008 at 04:13:47PM -0400, Dan Williams wrote:
> On Mon, 2008-10-20 at 16:49 -0700, Anna Neal wrote:
> > View README for new API.
> > 
> > This patch implements the userspace interface for fine-grained configuration of
> > wake-on-(w)lan.  We are aware that iwpriv's are discouraged, but this is a
> > vendor-specific feature that's currently being used in the OLPC project.
> > 
> > We are aware that all iwprivs were removed from this driver.  These used the old
> > API for iwprivs.  We've implemented this iwpriv as a private handler which relies
> > on wireless extensions to do bounds checking and copying to/from user memory.
> > Specific suggestions on how to make this more palatable for upstream inclusion
> > are welcome.  If iwprivs are completely unacceptable then this can serve as a
> > public reference for interfacing with these features.
> 
> IMHO we should be adding the functionality where's it's needed, which is
> that ethtool, which doesn't have a verbose enough syntax for it's WOL
> support.  If ethtool's existing WOL got fixed up to support these
> use-cases, then we wouldn't need iwpriv commands, we wouldn't have
> duplicate functionality running around, and everyone gets a pony.  Lets
> kick off that discussion...
> 
> Jeff: could something like this syntax be added to ethtool, or maybe
> discreet commands instead of one?  Thoughts?

Did anything come out of this discussion?  I'd prefer not to add new
iwpriv stuff...

John
-- 
John W. Linville		Linux should be at the core
linville@tuxdriver.com			of your literate lifestyle.

  reply	other threads:[~2008-10-31 19:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-20 23:49 [RFC] libertas: iwpriv commands to configure fine grained wake-on-(w)lan Anna Neal
2008-10-21 20:13 ` Dan Williams
2008-10-31 19:35   ` John W. Linville [this message]
2008-10-24 21:04 ` Dan Williams
2008-10-27 19:58   ` Javier Cardona

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=20081031193504.GF4310@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=anna@cozybit.com \
    --cc=dcbw@redhat.com \
    --cc=jeff@garzik.org \
    --cc=libertas-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    /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).