mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: dean <dean@sensoray.com>
Cc: Oliver Neukum <oliver@neukum.org>, Greg KH <greg@kroah.com>,
	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: Fri, 16 May 2008 15:17:18 -0300	[thread overview]
Message-ID: <20080516151718.15de1b9b@gaivota> (raw)
In-Reply-To: <482DAEDB.70702@sensoray.com>

Dean,

On Fri, 16 May 2008 08:57:15 -0700
dean <dean@sensoray.com> wrote:

> Hi Oliver,
> 
> Just to be clear.  You mean fixing the loading issues(ugly msleep, 
> etc...) that Mauro mentioned, not the YUV formats(which seem unrelated)? 
> 
> Would it be ok to have just 422P and greyscale in the driver for now if 
> we can't get a firmware update in a reasonable timeframe? It's certainly 
> not ideal, but we could direct our customers to the libraries, at least 
> until we get a proper HW fix.

Feature regression is something that shouldn't happen. If we add the driver
with a color conversion inside, we should somehow keep this feature available
on newer versions. That's said, I don't see any issue if the later versions do
this implementation inside hardware/firmware, since the end result is that the
driver will keep supporting those standards.

>From my side, I'm ok on having this color conversion for a short timeframe (one
or two kernel releases), if you are sure that those features will be present
on the next firmwares.

The better is to mark the driver as EXPERIMENTAL, at Kconfig.

Cheers,
Mauro

  parent reply	other threads:[~2008-05-16 18:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 20:59 Greg KH
2008-05-15  1:17 ` [v4l-dvb-maintainer] " Markus Rechberger
2008-05-15  2:41   ` Greg KH
2008-05-15  3:12     ` Trent Piepho
2008-05-15 15:34       ` Dean Anderson
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
2008-05-15 20:13           ` Oliver Neukum
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 [this message]
2008-05-16 14:53   ` dean
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=20080516151718.15de1b9b@gaivota \
    --to=mchehab@infradead.org \
    --cc=dean@sensoray.com \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®