Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753442AbdCOOCh (ORCPT ); Wed, 15 Mar 2017 10:02:37 -0400 Received: from ec2-52-27-115-49.us-west-2.compute.amazonaws.com ([52.27.115.49]:47692 "EHLO osg.samsung.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1752501AbdCOOBg (ORCPT ); Wed, 15 Mar 2017 10:01:36 -0400 Date: Wed, 15 Mar 2017 11:01:28 -0300 From: Mauro Carvalho Chehab To: Eric Anholt Cc: Greg Kroah-Hartman , devel@driverdev.osuosl.org, linux-media@vger.kernel.org, Mauro Carvalho Chehab , linux-rpi-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 0/6] staging: BCM2835 MMAL V4L2 camera driver Message-ID: <20170315110128.37e2bc5a@vento.lan> In-Reply-To: <20170127215503.13208-1-eric@anholt.net> References: <20170127215503.13208-1-eric@anholt.net> Organization: Samsung X-Mailer: Claws Mail 3.14.1 (GTK+ 2.24.31; x86_64-redhat-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1892 Lines: 45 Em Fri, 27 Jan 2017 13:54:57 -0800 Eric Anholt 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