public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Anton Sviridenko <anton@corp.bluecherry.net>
To: Ismael Luceno <ismael@iodev.co.uk>
Cc: Andrey Utkin <andrey.utkin@corp.bluecherry.net>,
	Bluecherry Maintainers <maintainers@bluecherrydvr.com>,
	linux-media@vger.kernel.org
Subject: Re: [PATCH] [media] solo6x10: release vb2 buffers in solo_stop_streaming()
Date: Fri, 10 Mar 2017 20:03:44 +0400	[thread overview]
Message-ID: <20170310160343.GA4406@magpie-gentoo> (raw)
In-Reply-To: <20170309215842.GB2940@pirotess.bf.iodev.co.uk>

On Thu, Mar 09, 2017 at 06:58:45PM -0300, Ismael Luceno wrote:
> On 08/Mar/2017 21:59, Andrey Utkin wrote:
> > Signed-off-by: Andrey Utkin <andrey.utkin@corp.bluecherry.net>
> > Signed-off-by: Andrey Utkin <andrey_utkin@fastmail.com>
> > 
> > Please welcome Anton who is now in charge of solo6x10 and tw5864 support
> > and development in Bluecherry company, I have sent out to him the
> > hardware samples I possessed. (We will prepare the patch updating
> > MAINTAINERS file soon.)
> > 
> > If anybody has any outstanding complains, concerns or tasks regarding
> > solo6x10 and tw5864 drivers, I think now is good occasion to let us know
> > about it.
> 
> Welcome Anton!
> 
> The first issue that comes to mind is that quantization matrices
> need to be adjusted since forever. Also it needs more realistic
> buffer sizes.

Hi Ismael,

can you provide more details about quantization matrices issue and
buffer sizes?

  reply	other threads:[~2017-03-10 16:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08 17:47 [PATCH] [media] solo6x10: release vb2 buffers in solo_stop_streaming() Anton Sviridenko
2017-03-08 21:59 ` Andrey Utkin
2017-03-09 21:58   ` Ismael Luceno
2017-03-10 16:03     ` Anton Sviridenko [this message]
2017-03-09 11:55 ` Hans Verkuil
2017-03-09 13:39   ` Anton Sviridenko

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=20170310160343.GA4406@magpie-gentoo \
    --to=anton@corp.bluecherry.net \
    --cc=andrey.utkin@corp.bluecherry.net \
    --cc=ismael@iodev.co.uk \
    --cc=linux-media@vger.kernel.org \
    --cc=maintainers@bluecherrydvr.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