public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: Andy Walls <awalls@radix.net>
Cc: Mauro Carvalho Chehab <mchehab@infradead.org>,
	linux-media <linux-media@vger.kernel.org>
Subject: Re: [PATCH 29/75] cx18: declare MODULE_FIRMWARE
Date: Sun, 08 Nov 2009 01:53:58 +0000	[thread overview]
Message-ID: <1257645238.15927.624.camel@localhost> (raw)
In-Reply-To: <1257644422.6895.8.camel@palomino.walls.org>

[-- Attachment #1: Type: text/plain, Size: 1870 bytes --]

On Sat, 2009-11-07 at 20:40 -0500, Andy Walls wrote:
> On Sat, 2009-11-07 at 21:51 +0000, Ben Hutchings wrote:
> > Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
> > ---
> >  drivers/media/video/cx18/cx18-av-firmware.c |    1 +
> >  drivers/media/video/cx18/cx18-dvb.c         |    2 ++
> >  drivers/media/video/cx18/cx18-firmware.c    |    3 +++
> >  3 files changed, 6 insertions(+), 0 deletions(-)
> > 
> > diff --git a/drivers/media/video/cx18/cx18-av-firmware.c b/drivers/media/video/cx18/cx18-av-firmware.c
> > index b9e8cc5..137445c 100644
> > --- a/drivers/media/video/cx18/cx18-av-firmware.c
> > +++ b/drivers/media/video/cx18/cx18-av-firmware.c
> > @@ -32,6 +32,7 @@
> >  #define CX18_AI1_MUX_INVALID 0x30
> >  
> >  #define FWFILE "v4l-cx23418-dig.fw"
> > +MODULE_FIRMWARE(FWFILE);
> >  
> >  static int cx18_av_verifyfw(struct cx18 *cx, const struct firmware *fw)
> >  {
> > diff --git a/drivers/media/video/cx18/cx18-dvb.c b/drivers/media/video/cx18/cx18-dvb.c
> > index 51a0c33..9f70168 100644
> > --- a/drivers/media/video/cx18/cx18-dvb.c
> > +++ b/drivers/media/video/cx18/cx18-dvb.c
> > @@ -131,6 +131,8 @@ static int yuan_mpc718_mt352_reqfw(struct cx18_stream *stream,
> >  	return ret;
> >  }
> >  
> > +MODULE_FIRMWARE("dvb-cx18-mpc718-mt352.fw");
> > +
> 
> Ben,
> 
> This particular firmware is only needed by one relatively rare TV card.
> Is there any way for MODULE_FIRMWARE advertisements to hint at
> "mandatory" vs. "particular case(s)"?

No, but perhaps there ought to be.  In this case the declaration could
be left out for now.  It is only critical to list all firmware in
drivers that may be needed for booting.

Ben.

-- 
Ben Hutchings
The generation of random numbers is too important to be left to chance.
                                                            - Robert Coveyou

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2009-11-08  1:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-07 21:51 [PATCH 29/75] cx18: declare MODULE_FIRMWARE Ben Hutchings
2009-11-08  1:40 ` Andy Walls
2009-11-08  1:53   ` Ben Hutchings [this message]
2009-11-08  2:08     ` Andy Walls
2009-11-09 10:06       ` Hans Verkuil
2009-11-09 12:03         ` Andy Walls
2009-11-09 12:34           ` Mauro Carvalho Chehab

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=1257645238.15927.624.camel@localhost \
    --to=ben@decadent.org.uk \
    --cc=awalls@radix.net \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox