Return-path: <linux-wireless-owner@vger.kernel.org>
Received: from an-out-0708.google.com ([209.85.132.251]:41928 "EHLO
	an-out-0708.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1755451AbXITPiz (ORCPT
	<rfc822;linux-wireless@vger.kernel.org>);
	Thu, 20 Sep 2007 11:38:55 -0400
Received: by an-out-0708.google.com with SMTP id d31so85962and
        for <linux-wireless@vger.kernel.org>; Thu, 20 Sep 2007 08:38:55 -0700 (PDT)
Message-ID: <43e72e890709200838j48d460a3pa72cce9c90d15b13@mail.gmail.com>
Date: Thu, 20 Sep 2007 11:38:54 -0400
From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: "Stephen Hemminger" <shemminger@linux-foundation.org>
Subject: Re: ath5k and network manager
Cc: "Michael Buesch" <mb@bu3sch.de>, linux-wireless@vger.kernel.org,
	"Jiri Slaby" <jirislaby@gmail.com>,
	"Tim Gardner" <tim.gardner@canonical.com>
In-Reply-To: <20070920083514.4a4f1b3f@freepuppy.rosehill>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
References: <20070919214007.1a6a9b4a@freepuppy.rosehill>
	 <43e72e890709200555r779aaa50i6bb8ab90195686bc@mail.gmail.com>
	 <200709201511.23400.mb@bu3sch.de>
	 <20070920083056.31f231b9@freepuppy.rosehill>
	 <43e72e890709200834xc6947f5g50a6cf0c5bd4d971@mail.gmail.com>
	 <20070920083514.4a4f1b3f@freepuppy.rosehill>
Sender: linux-wireless-owner@vger.kernel.org
List-ID: <linux-wireless.vger.kernel.org>

On 9/20/07, Stephen Hemminger <shemminger@linux-foundation.org> wrote:
> On Thu, 20 Sep 2007 11:34:29 -0400
> "Luis R. Rodriguez" <mcgrof@gmail.com> wrote:
>
> > On 9/20/07, Stephen Hemminger <shemminger@linux-foundation.org> wrote:
> > > On Thu, 20 Sep 2007 15:11:23 +0200
> > > Michael Buesch <mb@bu3sch.de> wrote:
> > >
> > > > On Thursday 20 September 2007, Luis R. Rodriguez wrote:
> > > > > On 9/20/07, Stephen Hemminger <shemminger@linux-foundation.org> wrote:
> > > > > > Network manager doesn't seem to detect ath5k. Perhaps it is because
> > > > > > it is name "ath0".  I think device should follow the convention of using
> > > > > > name "wifi0" rather than BSD convention of putting driver name in device name.
> > > > >
> > > > > I couldn't agree anymore. But my ath5k kicks out a wlan%d name as with
> > > > > any other mac80211 driver. Is yours coming out to ath%d ?
> > > > >
> > > > > ieee80211_register_hw():
> > > > >
> > > > >         /* add one default STA interface */
> > > > >         result = ieee80211_if_add(local->mdev, "wlan%d", NULL,
> > > > >                                   IEEE80211_IF_TYPE_STA);
> > > > >
> > > >
> > > >
> > > > Probably udev renames it.
> > >
> > > It was udev, don't know why Ubuntu was adding a rule for it (and getting wrong)
> > > value.
> > >
> >
> > CC' TIm
> >
> > Was it a rule by PCI ID? If so then perhaps its based on the old
> > madwifi rules of sticking to ath%d notation as well. This can be
> > removed for ath5k but not too sure how this works.
> >
>
> It was by PCI ID

Then I guess that rule should be removed from udev because of ath5k,
if we let the driver pick the name then we'd get ath%d for madwifi
driver and wlan%d for ath5k. Would help with troubleshooting too. Tim?
:-)

  Luis