All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Eric Anholt <eric@anholt.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	devel@driverdev.osuosl.org, linux-media@vger.kernel.org,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	linux-rpi-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/6] staging: BCM2835 MMAL V4L2 camera driver
Date: Wed, 15 Mar 2017 11:01:28 -0300	[thread overview]
Message-ID: <20170315110128.37e2bc5a@vento.lan> (raw)
In-Reply-To: <20170127215503.13208-1-eric@anholt.net>

Em Fri, 27 Jan 2017 13:54:57 -0800
Eric Anholt <eric@anholt.net> escreveu:

> Here's my first pass at importing the camera driver.  There's a bunch
> of TODO left to it, most of which is documented, and the rest being
> standard checkpatch fare.
> 
> Unfortunately, when I try modprobing it on my pi3, the USB network
> device dies, consistently.  I'm not sure what's going on here yet, but
> I'm going to keep working on some debug of it.  I've unfortunately
> changed a lot of variables (pi3 vs pi2, upstream vs downstream, vchi's
> updates while in staging, 4.9 vs 4.4), so I probably won't figure it
> out today.
> 
> Note that the "Update the driver to the current VCHI API" patch will
> conflict with the outstanding "Add vchi_queue_kernel_message and
> vchi_queue_user_message" series, but the fix should be pretty obvious
> when that lands.
> 
> I built this against 4.10-rc1, but a merge with staging-next was clean
> and still built fine.

I'm trying it, building from the linux-next branch of the staging
tree. No joy.

That's what happens when I modprobe it:

[  991.841549] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned.
[  991.842931] vchiq_get_state: g_state.remote == NULL
[  991.843437] vchiq_get_state: g_state.remote == NULL
[  991.843940] vchiq_get_state: g_state.remote == NULL
[  991.844444] vchiq_get_state: g_state.remote == NULL
[  991.844947] vchiq_get_state: g_state.remote == NULL
[  991.845451] vchiq_get_state: g_state.remote == NULL
[  991.845954] vchiq_get_state: g_state.remote == NULL
[  991.846457] vchiq_get_state: g_state.remote == NULL
[  991.846961] vchiq_get_state: g_state.remote == NULL
[  991.847464] vchiq_get_state: g_state.remote == NULL
[  991.847969] vchiq: vchiq_initialise: videocore not initialized

[  991.847973] mmal_vchiq: Failed to initialise VCHI instance (status=-1)


Thanks,
Mauro

  parent reply	other threads:[~2017-03-15 14:01 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 ` Mauro Carvalho Chehab [this message]
2017-03-15 21:50   ` [PATCH 0/6] staging: BCM2835 MMAL V4L2 camera driver 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
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=20170315110128.37e2bc5a@vento.lan \
    --to=mchehab@s-opensource.com \
    --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 \
    /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.