From: Michael Zoran <mzoran@crowfest.net>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: Eric Anholt <eric@anholt.net>,
devel@driverdev.osuosl.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-media@vger.kernel.org
Subject: Re: [PATCH 0/6] staging: BCM2835 MMAL V4L2 camera driver
Date: Mon, 20 Mar 2017 08:11:41 -0700 [thread overview]
Message-ID: <1490022701.11105.3.camel@crowfest.net> (raw)
In-Reply-To: <20170320115821.736931ee@vento.lan>
On Mon, 2017-03-20 at 11:58 -0300, Mauro Carvalho Chehab wrote:
> Em Mon, 20 Mar 2017 04:08:21 -0700
> Michael Zoran <mzoran@crowfest.net> escreveu:
>
> > On Mon, 2017-03-20 at 07:58 -0300, Mauro Carvalho Chehab wrote:
> > > Em Sun, 19 Mar 2017 22:11:07 -0300
> > > Mauro Carvalho Chehab <mchehab@s-opensource.com> escreveu:
> > >
> > > > Em Sun, 19 Mar 2017 10:04:28 -0700
> > > > Michael Zoran <mzoran@crowfest.net> escreveu:
> > > >
> > > > > A working DT that I tried this morning with the current
> > > > > firmware
> > > > > is
> > > > > posted here:
> > > > > http://lists.infradead.org/pipermail/linux-rpi-kernel/2017-Ma
> > > > > rch/
> > > > > 005924
> > > > > .html
> > > > >
> > > > > It even works with minecraft_pi!
> > >
> > >
> >
> > Hi, can you e-mail out your config.txt? Do you have audio enabled
> > in
> > config.txt?
>
> yes, I have this:
>
> $ cat config.txt |grep -i audio
> # uncomment to force a HDMI mode rather than DVI. This can make audio
> work in
> # Enable audio (loads snd_bcm2835)
> dtparam=audio=on
>
> Full config attached.
>
> Thanks,
> Mauro
>
Are you using Eric Anholt's HDMI Audio driver that's included in VC4?
That could well be incompatible with the firmware driver. Or are you
using a half mode of VC4 for audio and VCHIQ for video?
next prev parent reply other threads:[~2017-03-20 15:12 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 21:54 [PATCH 0/6] staging: BCM2835 MMAL V4L2 camera driver Eric Anholt
2017-01-27 21:54 ` [PATCH 1/6] staging: Import the BCM2835 MMAL-based " Eric Anholt
2017-02-03 18:59 ` Mauro Carvalho Chehab
2017-02-05 22:15 ` Dave Stevenson
2017-02-05 23:13 ` Michael Zoran
2017-02-06 8:30 ` Greg Kroah-Hartman
2017-02-06 12:37 ` Mauro Carvalho Chehab
2017-02-06 15:01 ` Dave Stevenson
2017-02-06 9:08 ` Hans Verkuil
2017-02-06 11:37 ` Dave Stevenson
2017-02-06 12:58 ` Hans Verkuil
2017-02-06 15:21 ` Dave Stevenson
2017-02-06 16:00 ` Hans Verkuil
2017-02-10 9:47 ` Hans Verkuil
2017-02-06 12:59 ` Hans Verkuil
2017-01-27 21:54 ` [PATCH 2/6] staging: bcm2835-v4l2: Update the driver to the current VCHI API Eric Anholt
2017-01-27 21:55 ` [PATCH 3/6] staging: bcm2835-v4l2: Add a build system for the module Eric Anholt
2017-01-29 14:12 ` Michael Zoran
2017-02-03 19:01 ` Mauro Carvalho Chehab
2017-01-27 21:55 ` [PATCH 4/6] staging: bcm2835-v4l2: Add a TODO file for improvements we need Eric Anholt
2017-01-27 21:55 ` [PATCH 5/6] staging: bcm2835-v4l2: Apply many whitespace fixes from checkpatch Eric Anholt
2017-01-27 21:55 ` [PATCH 6/6] staging: bcm2835-v4l2: Apply spelling " Eric Anholt
2017-01-27 22:30 ` Joe Perches
2017-01-30 20:05 ` Eric Anholt
2017-01-31 1:38 ` Joe Perches
2017-01-31 18:30 ` Eric Anholt
2017-01-31 18:49 ` Joe Perches
2017-03-15 14:01 ` [PATCH 0/6] staging: BCM2835 MMAL V4L2 camera driver Mauro Carvalho Chehab
2017-03-15 21:50 ` Stefan Wahren
2017-03-15 22:01 ` Eric Anholt
2017-03-16 1:08 ` Mauro Carvalho Chehab
2017-03-16 1:46 ` Michael Zoran
2017-03-16 9:29 ` Mauro Carvalho Chehab
2017-03-18 0:34 ` Eric Anholt
2017-03-19 16:58 ` Mauro Carvalho Chehab
2017-03-19 17:04 ` Michael Zoran
2017-03-20 1:11 ` Mauro Carvalho Chehab
2017-03-20 10:58 ` Mauro Carvalho Chehab
2017-03-20 11:08 ` Michael Zoran
2017-03-20 14:58 ` Mauro Carvalho Chehab
2017-03-20 15:11 ` Michael Zoran [this message]
2017-03-20 15:33 ` Mauro Carvalho Chehab
2017-03-20 15:40 ` Michael Zoran
2017-03-22 17:10 ` Mauro Carvalho Chehab
2017-03-20 11:57 ` Stefan Wahren
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=1490022701.11105.3.camel@crowfest.net \
--to=mzoran@crowfest.net \
--cc=devel@driverdev.osuosl.org \
--cc=eric@anholt.net \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mchehab@kernel.org \
--cc=mchehab@s-opensource.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