All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Stezenbach <js@linuxtv.org>
To: Mauro Carvalho Chehab <m.chehab@samsung.com>
Cc: Michael Ira Krufky <mkrufky@linuxtv.org>,
	linux-media <linux-media@vger.kernel.org>,
	Richard Vollkommer <linux@hauppauge.com>,
	Devin Heitmueller <dheitmueller@kernellabs.com>
Subject: Re: [PATCH 1/3] xc5000: tuner firmware update
Date: Mon, 27 Oct 2014 17:22:52 +0100	[thread overview]
Message-ID: <20141027162252.GA9984@linuxtv.org> (raw)
In-Reply-To: <20141027135727.297ba10a.m.chehab@samsung.com>

On Mon, Oct 27, 2014 at 01:57:27PM -0200, Mauro Carvalho Chehab wrote:
> Em Mon, 27 Oct 2014 10:25:48 -0400
> Michael Ira Krufky <mkrufky@linuxtv.org> escreveu:
> 
> > I like the idea of supporting older firmware revisions if the new one
> > is not present, but, the established president for this sort of thing
> > has always been to replace older firmware with newer firmware without
> > backward compatibility support for older binaries.
> 
> No, we're actually adding backward support. There are some drivers
> already with it. See for example xc4000 (changeset da7bfa2c5df).
> 
> > Although the current driver can work with both old and new firmware
> > versions, this hasn't been the case in the past, and won't always be
> > the case with future firmware revisions.
> 
> Yeah, we did a very crap job breaking backward firmware compat in
> the past. We're not doing it anymore ;)
> 
> > Hauppauge has provided links to the new firmware for both the XC5000
> > and XC5000C chips along with licensing.  Maybe instead, we can just
> > upstream those into the linux-firmware packages for distribution.
> 
> Upstreaming to linux-firmware was done already for the previous firmwares.
> The firmwares at linux-firmware for xc5000 and xc5000c were merged back 
> there for 3.17 a few weeks ago.
> 
> Feel free to submit them a new version.
> 
> > I don't think supporting two different firmware versions is a good
> > idea for the case of the xc5000 driver.
> 
> Why not? It should work as-is with either version. We can always add
> some backward compat code if needed.

FWIW, Linus recently addressed the topic wrt wireless firmware:
http://article.gmane.org/gmane.linux.kernel.wireless.general/126794


HTH,
Johannes

  reply	other threads:[~2014-10-27 16:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-25 20:17 [PATCH 1/3] xc5000: tuner firmware update Michael Krufky
2014-10-27 11:46 ` Mauro Carvalho Chehab
2014-10-27 14:25   ` Michael Ira Krufky
2014-10-27 15:57     ` Mauro Carvalho Chehab
2014-10-27 16:22       ` Johannes Stezenbach [this message]
2014-10-27 17:38         ` Michael Ira Krufky
2014-10-27 19:07           ` Mauro Carvalho Chehab
2014-10-30 13:20             ` Devin Heitmueller

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=20141027162252.GA9984@linuxtv.org \
    --to=js@linuxtv.org \
    --cc=dheitmueller@kernellabs.com \
    --cc=linux-media@vger.kernel.org \
    --cc=linux@hauppauge.com \
    --cc=m.chehab@samsung.com \
    --cc=mkrufky@linuxtv.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.