linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Henry Ptasinski (local)" <hp@broadcom.com>
To: "Greg KH" <greg@kroah.com>
Cc: "Henry Ptasinski" <henryp@broadcom.com>,
	"Nohee Ko" <noheek@broadcom.com>,
	"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
	"Brett Rudley" <brudley@broadcom.com>,
	"Venkat Rao" <vrao@broadcom.com>,
	"grundler@google.com" <grundler@google.com>,
	linux-wireless@vger.kernel.org, dwmw2@infradead.org
Subject: Re: [PATCH] staging:brcm80211:brcmfmac:change firmware/config file name
Date: Wed, 20 Oct 2010 11:04:14 -0700	[thread overview]
Message-ID: <20101020180414.GB12658@broadcom.com> (raw)
In-Reply-To: <20101020010320.GA370@kroah.com>

On Tue, Oct 19, 2010 at 06:03:20PM -0700, Greg KH wrote:
> On Tue, Oct 19, 2010 at 05:55:46PM -0700, Henry Ptasinski wrote:
> > On Tue, Oct 19, 2010 at 05:47:43PM -0700, Greg KH wrote:
> > > On Tue, Oct 19, 2010 at 04:45:26PM -0700, Nohee Ko wrote:
> > > > >>
> > > > Have you made the same changes in the linux-firmware source tree as
> > > > well?  Without changing it there, this could get messy.
> > > > <<
> > > > 
> > > > No not yet. But we are planning sooner or later.
> > > 
> > > Please do it sooner.
> > > 
> > > I'll wait for that to happen before committing this patch.
> > 
> > There's no specific changes needed in the linux-firmware repo to work with this
> > driver change.  There is a bugfix version of the firmware that we're getting
> > ready to send up, which is the motivation for this change, but the change
> > will work properly with the firmware that's in the repo today.
> 
> How, you just renamed the file you look for in the driver, right?
> 
> > All this change does is replace the hard-coded full firmware filename used in
> > the driver with the basename-apiversion construction as documented in
> > 
> > 	http://www.linuxwireless.org/en/developers/Documentation/firmware-versioning
> > 
> > plus add some info to the README to help users get the firmware properly
> > installed.
> > 
> > Users will need to create the symlinks as described in the README to use these
> > driver changes.
> 
> Yes, so you just broke their working setup, right?
> 
> So, please get linux-firmware fixed to add the proper symlinks, and then
> I can apply the patch, and say "go upgrade your linux-firmware package",
> which is almost acceptable.

Ah, I didn't catch that the symlink should be in the linux-firmware repo.  We
didn't do that for the brcm80211 driver firmware either, and nobody pointed it
out.

But I don't see any symlinks in the linux-firmware repo.  Is anybody else using
the "best practices" as documented?  Or should we just punt the codeversion
part of the filenames and the symlinks, and just use basename-apiversion?

Thanks,
- Henry



  parent reply	other threads:[~2010-10-20 18:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4CBE23F4.4020104@broadcom.com>
     [not found] ` <20101019233520.GA12510@kroah.com>
     [not found]   ` <FD96C117992C584DBC47231B1EB6F5568206D859DC@SJEXCHCCR02.corp.ad.broadcom.com>
     [not found]     ` <20101020004743.GB31965@kroah.com>
     [not found]       ` <20101020005546.GL10832@broadcom.com>
     [not found]         ` <20101020010320.GA370@kroah.com>
2010-10-20  2:18           ` [PATCH] staging:brcm80211:brcmfmac:change firmware/config file name Henry Ptasinski
2010-10-20  3:10             ` Greg KH
2010-10-20 11:49             ` Rafał Miłecki
2010-10-20 18:04           ` Henry Ptasinski (local) [this message]
2010-10-21 17:08           ` [PATCH] linux-firmware: brcm: Removed codeversion from firmware filenames Henry Ptasinski
2010-11-01 14:28             ` David Woodhouse
2010-12-08 20:50               ` [PATCH v2] " Henry Ptasinski
2010-12-08 22:07                 ` Rafał Miłecki
2010-12-08 22:23                   ` Greg KH
2010-12-08 23:35                     ` Henry Ptasinski
2010-12-09  0:28                       ` Rafał Miłecki
2010-12-09  1:30                         ` Henry Ptasinski
2010-12-09  9:01                           ` Rafał Miłecki
2010-10-21 17:10           ` Subject: [PATCH] staging: brcm80211: brcmfmac: " Henry Ptasinski
2010-10-21 18:26             ` Greg KH
2010-10-21 18:37               ` Subject: [PATCH v2] " Henry Ptasinski

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=20101020180414.GB12658@broadcom.com \
    --to=hp@broadcom.com \
    --cc=brudley@broadcom.com \
    --cc=devel@linuxdriverproject.org \
    --cc=dwmw2@infradead.org \
    --cc=greg@kroah.com \
    --cc=grundler@google.com \
    --cc=henryp@broadcom.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=noheek@broadcom.com \
    --cc=vrao@broadcom.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).