All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Oliver Neukum <oliver@neukum.org>
Cc: mchehab@infradead.org, v4l-dvb-maintainer@linuxtv.org,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	video4linux-list@redhat.com
Subject: Re: [PATCH] USB: add Sensoray 2255 v4l driver
Date: Thu, 15 May 2008 13:10:49 -0700	[thread overview]
Message-ID: <20080515201049.GA24999@kroah.com> (raw)
In-Reply-To: <200805152154.13630.oliver@neukum.org>

On Thu, May 15, 2008 at 09:54:12PM +0200, Oliver Neukum wrote:
> Am Donnerstag 15 Mai 2008 20:44:24 schrieb Greg KH:
> > On Thu, May 15, 2008 at 02:03:18PM +0200, Oliver Neukum wrote:
> > > Am Donnerstag 15 Mai 2008 13:38:37 schrieb Oliver Neukum:
> > > > 3. The firmware stuff. That's an interesting solution. However:
> > > 
> > > Actually, on second thought, I take that back. It's a bad solution.
> > > If you don't want to do it in probe(), the only other sensible place
> > > is in open(). That way you can avoid the whole trouble if nobody
> > > opens the device. And you need to handle the case of unloaded
> > > firmware anyway, so you can trigger firmware load there.
> > 
> > No, we want to do firmware load on probe, I'll change it to be async so
> 
> Could you state your reasons for that preference?

I don't want to create the device nodes, and have userspace think the
device really is working, only to have everything fall down and die if
open() is called and the firmware isn't present.  I'd rather not create
the video devices if we know this isn't going to work at all.

Just trying to be nicer to users who would get very confused, "but wait,
the device nodes are there, and the application finds the device, why is
it not working properly?"

thanks,

greg k-h

  reply	other threads:[~2008-05-15 20:11 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 20:59 [PATCH] USB: add Sensoray 2255 v4l driver Greg KH
2008-05-15  1:17 ` [v4l-dvb-maintainer] " Markus Rechberger
2008-05-15  1:17   ` Markus Rechberger
2008-05-15  2:41   ` Greg KH
2008-05-15  3:12     ` Trent Piepho
2008-05-15  3:12       ` Trent Piepho
2008-05-15 15:34       ` Dean Anderson
2008-05-15 16:57         ` Markus Rechberger
2008-05-15 16:57           ` Markus Rechberger
2008-05-16  2:59         ` Mauro Carvalho Chehab
2008-05-15 11:38 ` Oliver Neukum
2008-05-15 12:03   ` Oliver Neukum
2008-05-15 18:44     ` Greg KH
2008-05-15 19:54       ` Oliver Neukum
2008-05-15 20:10         ` Greg KH [this message]
2008-05-15 20:13           ` Oliver Neukum
2008-05-16  2:51 ` Mauro Carvalho Chehab
2008-05-16  2:51   ` Mauro Carvalho Chehab
2008-05-16  6:28   ` Oliver Neukum
2008-05-16 15:57     ` dean
2008-05-16 16:04       ` Oliver Neukum
2008-05-16 18:17       ` Mauro Carvalho Chehab
2008-05-16 18:17         ` Mauro Carvalho Chehab
2008-05-16 14:53   ` dean
2008-05-16 15:34     ` Mauro Carvalho Chehab
2008-05-16 15: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=20080515201049.GA24999@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=oliver@neukum.org \
    --cc=v4l-dvb-maintainer@linuxtv.org \
    --cc=video4linux-list@redhat.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 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.