From owner-freebsd-wireless@FreeBSD.ORG  Wed May 22 19:40:45 2013
Return-Path: <owner-freebsd-wireless@FreeBSD.ORG>
Delivered-To: freebsd-wireless@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by hub.freebsd.org (Postfix) with ESMTP id F1B10FB1
 for <freebsd-wireless@freebsd.org>; Wed, 22 May 2013 19:40:45 +0000 (UTC)
 (envelope-from johannes@sipsolutions.net)
Received: from sipsolutions.net (s3.sipsolutions.net [144.76.43.152])
 by mx1.freebsd.org (Postfix) with ESMTP id B66A060F
 for <freebsd-wireless@freebsd.org>; Wed, 22 May 2013 19:40:45 +0000 (UTC)
Received: by sipsolutions.net with esmtpsa
 (TLS1.0:DHE_RSA_CAMELLIA_256_CBC_SHA1:256) (Exim 4.80)
 (envelope-from <johannes@sipsolutions.net>)
 id 1UfEtw-0003Fa-OT; Wed, 22 May 2013 21:40:44 +0200
Message-ID: <1369251640.8207.31.camel@jlt4.sipsolutions.net>
Subject: Re: Intel 100/6205/6300 wireless driver
From: Johannes Berg <johannes@sipsolutions.net>
To: Adrian Chadd <adrian.chadd@gmail.com>
Date: Wed, 22 May 2013 21:40:40 +0200
In-Reply-To: <CAJ-VmokzX_VBXa-OBZ=GdTRy4r+aTzfxbi45rqgphfZGqROO4w@mail.gmail.com>
 (sfid-20130522_213651_917682_1B6649BC)
References: <1369237710.8207.22.camel@jlt4.sipsolutions.net>
 <CAJ-Vmon47nvpMFrrt6fRh9Vu+sejdj9o8JQKOJOgPVVjhBi+1w@mail.gmail.com>
 <CAJ-VmokzX_VBXa-OBZ=GdTRy4r+aTzfxbi45rqgphfZGqROO4w@mail.gmail.com>
 (sfid-20130522_213651_917682_1B6649BC)
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.6.3-1 
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Cc: freebsd-wireless@freebsd.org
X-BeenThere: freebsd-wireless@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: "Discussions of 802.11 stack,
 tools device driver development." <freebsd-wireless.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-wireless>
List-Post: <mailto:freebsd-wireless@freebsd.org>
List-Help: <mailto:freebsd-wireless-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-wireless>, 
 <mailto:freebsd-wireless-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 22 May 2013 19:40:46 -0000

On Wed, 2013-05-22 at 12:36 -0700, Adrian Chadd wrote:
> On 22 May 2013 12:31, Adrian Chadd <adrian.chadd@gmail.com> wrote:
> > Hiya!
> >
> > I'm just working out the build kinks. The driver built fine; but the
> > firmware images are a bit .. special.
> 
> .. in fact, most of thse images aren't really named after the same
> kind of names I see in the linux-firmware tree.
> 
> Would you be able to help me map the firmware image directory
> filenames to linux-firmware names?

Well for "/lib/firmware" names, or linux-firmware.git tree names,
they're just iwlwifi-<hwcode>-<API>.ucode. So if you download the
iwlwifi-6000g2b-ucode-17.168.5.2.tgz file from intellinuxwireless.org,
you'll get a tar file containing iwlwifi-6000g2b-5.ucode, with that
specific version, but the (Linux) driver only cares about the API level
for compatibility, so nothing else is part of the filename.

In linux-firmware.git we try to just keep the latest version(s) of each
API level.

johannes