linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Johannes Berg <johannes@sipsolutions.net>,
	linux-wireless@vger.kernel.org
Subject: Re: [PATCH] iw: add kernel version checks for pending upstream kernel features
Date: Thu, 18 Sep 2008 11:13:33 -0400	[thread overview]
Message-ID: <1221750813.5565.12.camel@dv> (raw)
In-Reply-To: <1221748533-11000-1-git-send-email-linville@tuxdriver.com>

On Thu, 2008-09-18 at 10:35 -0400, John W. Linville wrote:
> Add checks for kernel version to enable features in the iw tool.  This
> allows packagers to get pre-package the tool without requiring precise
> timing to stage the tool into their distributions.

I'm afraid it's not a good approach.  Suppose a distro takes this
version of iw and Linux 2.6.27.  Later it issues an update for the
kernel that updates it to 2.6.28.  Userspace tools don't normally depend
on the specific version of the kernel, and that's a good thing.  But in
this case, it means that iw won't be recompiled and updated unless the
distro has some mechanism in place to detect such need.  Since the
kernel version detection is done on the compiler level, I suspect such
need won't be detected.

The end result is that iw won't be able to access all functionality of
the kernel.

I believe userspace tools should always do the best effort to support
all functionality they can support, but fail gracefully if any kernel
functionality is not available.

Keeping a local version of nl80211.h in iw sources seems the most
sensible solution to me.  It has its downsides, but the upside is that
there is a clear separation between the userspace and the kernel code.

I know something about Fedora packaging and I assisted developers of
other userspace tools with similar issues.  Of course, opinions of the
actual package maintainers would have more weight.

-- 
Regards,
Pavel Roskin

  reply	other threads:[~2008-09-18 15:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-18 14:35 [PATCH] iw: add kernel version checks for pending upstream kernel features John W. Linville
2008-09-18 15:13 ` Pavel Roskin [this message]
2008-09-18 15:41 ` Johannes Berg
2008-09-18 16:10   ` Pavel Roskin
2008-09-18 17:26   ` Marcel Holtmann
2008-09-18 17:28     ` Johannes Berg
2008-09-18 20:43       ` Marcel Holtmann
2008-09-18 19:19     ` Pavel Roskin
2008-09-19  1:25   ` John W. Linville

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=1221750813.5565.12.camel@dv \
    --to=proski@gnu.org \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.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).