From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Shahar Or <mightyiampresence@gmail.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"ath5k-devel@lists.ath5k.org" <ath5k-devel@lists.ath5k.org>,
"John W. Linville" <linville@tuxdriver.com>
Subject: Re: [ath5k-devel] [PATCH] ath5k: add support for Dell Vostro A860 LED
Date: Fri, 18 Dec 2009 08:23:09 -0800 [thread overview]
Message-ID: <20091218162309.GD6231@tux> (raw)
In-Reply-To: <43e72e890912180737s382c24c5q8720f1e3138fefb@mail.gmail.com>
On Fri, Dec 18, 2009 at 07:37:24AM -0800, Luis Rodriguez wrote:
> On Fri, Dec 18, 2009 at 3:42 AM, Shahar Or <mightyiampresence@gmail.com> wrote:
> > On Tue, Dec 8, 2009 at 6:30 PM, Luis R. Rodriguez
> > <lrodriguez@atheros.com> wrote:
> >>>> IIRC this is all mapped in the INF file, I thought I had released an
> >>>> INF file under the ISC license but it seems that's not the case, I can
> >>>> try to do that if it helps. Anyway, if we can move this sort of map to
> >>>> userspace it'd be neat as you'd just need a userspace file update.
> >>>> Only thing is how to do this in a generic way for all wireless drivers
> >>>> and if this is indeed useful for other drivers.
> >>>
> >>> Export something through sysfs and use a udev rule?
> >>
> >> True. Is sysfs the preferred fs nowadays, what about configfs? Or
> >> maybe even udev rule --> nl80211 ?
> >
> > If we have all the IDs from the INF file, then why do we need this in
> > userspace? Is the list growing?
>
> No, but for other newer hardware/drivers it can likely grow, so my
> comment was more of a generic driver approach to this.
Actually AR2425 still sells it seems, so yeah I guess it can grow even
for ath5k.
Luis
next prev parent reply other threads:[~2009-12-18 16:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-03 13:07 [PATCH] ath5k: add support for Dell Vostro A860 LED Shahar Or
2009-12-04 19:23 ` John W. Linville
2009-12-07 10:05 ` Shahar Or
2009-12-07 21:59 ` John W. Linville
2009-12-08 14:57 ` [ath5k-devel] " Bob Copeland
2009-12-08 16:01 ` Luis R. Rodriguez
2009-12-08 16:06 ` John W. Linville
2009-12-08 16:30 ` Luis R. Rodriguez
2009-12-18 11:42 ` Shahar Or
2009-12-18 15:37 ` Luis R. Rodriguez
2009-12-18 16:23 ` Luis R. Rodriguez [this message]
2009-12-18 17:03 ` Shahar Or
2009-12-18 17:19 ` Luis R. Rodriguez
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=20091218162309.GD6231@tux \
--to=lrodriguez@atheros.com \
--cc=ath5k-devel@lists.ath5k.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mightyiampresence@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).