linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: "Stefanik Gábor" <netrolller.3d@gmail.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	David Woodhouse <dwmw2@infradead.org>,
	Brian Cavagnolo <brian@cozybit.com>,
	devel@laptop.org, libertas-dev@lists.infradead.org,
	linux-wireless@vger.kernel.org,
	Andres Salomon <dilinger@queued.net>,
	Javier Cardona <javier@cozybit.com>,
	Ricardo Carrano <carrano@ricardocarrano.com>
Subject: Re: [PATCH stable] libertas: Extend CMD_MESH_CONFIG to get and set persistent mesh default params.
Date: Tue, 13 May 2008 11:54:38 -0400	[thread overview]
Message-ID: <1210694078.24737.12.camel@localhost.localdomain> (raw)
In-Reply-To: <69e28c910805160851v7be6ccd0qc5f8538748941e80@mail.gmail.com>

On Fri, 2008-05-16 at 17:51 +0200, Stefanik G=C3=A1bor wrote:
> On Fri, May 16, 2008 at 4:50 PM, Johannes Berg
> <johannes@sipsolutions.net> wrote:
> > On Fri, 2008-05-16 at 15:09 +0100, David Woodhouse wrote:
> >> On Thu, 2008-05-15 at 11:01 -0700, Brian Cavagnolo wrote:
> >> > This patch is based on a patch from Shailendra Govardhan.  It in=
troduces
> >> > several new iwprivs: {get,set}_bootflag {get,set}_boottime {get,=
set}_def_chan
> >> > {get,set}_def_protid {get,set}_def_metid {get,set}_def_meshcap
> >> > {get,set}_def_meshid.  These commands are only supported on Marv=
ell hardware
> >> > that implements persistent defaults, such as the OLPC Active Ant=
enna.
> >> > Accordingly, this patch may not be suitable for upstream merging=
=2E
> >
> >> But this is the _one_ thing which might actually be OK to do with =
a
> >> private ioctl, since it's very hardware-specific. Unlike like all =
the
> >> mesh-mangling stuff where we really ought to be compatible with o1=
1s.
> >>
> >> So maybe, just maybe, we _can_ do this with iwpriv and push that
> >> upstream.
> >
> > Maybe we do, after all, need an iwpriv equivalent in cfg80211/nl802=
11 so
> > that we can kill wext at some point.
> >
> > Or maybe this should be in sysfs or so?
> >
> > johannes
> >
>=20
> Or maybe in configfs? That's a better place for configuration options=
=2E
> (BTW rt2x00 uses debugfs as an iwpriv replacement, so that's another
> possibility.)

I keep proposing debugfs too, but in some cases the commands aren't jus=
t
for poking around with stuff.  configfs is probably a better answer to
tweakables that aren't just ricer-geekporn.

Dan

--
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2008-05-16 15:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <482c8eb8.0b97600a.08e2.ffff8ee3@mx.google.com>
2008-05-16 14:09 ` [PATCH stable] libertas: Extend CMD_MESH_CONFIG to get and set persistent mesh default params David Woodhouse
2008-05-16 14:50   ` Johannes Berg
2008-05-16 15:51     ` Stefanik Gábor
2008-05-13 15:54       ` Dan Williams [this message]

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=1210694078.24737.12.camel@localhost.localdomain \
    --to=dcbw@redhat.com \
    --cc=brian@cozybit.com \
    --cc=carrano@ricardocarrano.com \
    --cc=devel@laptop.org \
    --cc=dilinger@queued.net \
    --cc=dwmw2@infradead.org \
    --cc=javier@cozybit.com \
    --cc=johannes@sipsolutions.net \
    --cc=libertas-dev@lists.infradead.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=netrolller.3d@gmail.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).