From mboxrd@z Thu Jan 1 00:00:00 1970 From: Xinliang Liu Subject: Re: Whats missing in my new FB DRM driver... "No connectors reported connected with modes"? Date: Thu, 31 Dec 2015 10:19:48 +0800 Message-ID: References: <5684268E.2000607@synopsys.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1819085676==" Return-path: Received: from mail-ob0-f174.google.com (mail-ob0-f174.google.com [209.85.214.174]) by gabe.freedesktop.org (Postfix) with ESMTPS id 1F0A76E040 for ; Wed, 30 Dec 2015 18:19:49 -0800 (PST) Received: by mail-ob0-f174.google.com with SMTP id ba1so188904618obb.3 for ; Wed, 30 Dec 2015 18:19:49 -0800 (PST) In-Reply-To: <5684268E.2000607@synopsys.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: Carlos Palminha Cc: linux-fbdev@vger.kernel.org, tomi.valkeinen@ti.com, laurent.pinchart@ideasonboard.com, dri-devel List-Id: dri-devel@lists.freedesktop.org --===============1819085676== Content-Type: multipart/alternative; boundary=047d7b2e4e38f7d0d105282849c4 --047d7b2e4e38f7d0d105282849c4 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On 31 December 2015 at 02:46, Carlos Palminha wrote: > Hi guys, > > I'm writing a DRM driver for a framebuffer embedded hardware that uses an > i2c encoder (adv7511), following the basic steps suggested by Laurent in > "anatomy of an embedded KMS driver": > https://www.youtube.com/watch?v=3DJa8fM7rTae4 > > After initiliazing all kms, crtc, encoder, i2c, connector functions and > structures i'm calling drm_fbdev_cma_init to create a fbdev. > > When booting i'm getting an error message saying "No connectors reported > connected with modes", but the driver init is ok and i can find the > /dev/dri/* and /dev/fb0 devices. > > Any clue what i might be missing during the driver load? > =E2=80=8BI think you should check on the 'get_modes'=E2=80=8B call back of = adv7511 driver. (Or, if possible show us the code.) Best, -xinliang > > Thanks... > > Regards, > C.Palminha > > --- boot log snippet --- > [drm] Initialized drm 1.1.0 20060810 > drm-arcpgu e0017000.pgu: No connectors reported connected with modes > [drm] Cannot find any crtc or sizes - going 1024x768 > Console: switching to colour frame buffer device 128x48 > drm-arcpgu e0017000.pgu: fb0: frame buffer device > [drm] Initialized drm-arcpgu 1.0.0 20151127 on minor 0 > --- boot log snippet --- > -- > To unsubscribe from this list: send the line "unsubscribe linux-fbdev" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > --047d7b2e4e38f7d0d105282849c4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On 31 December 2015 at 02:46, Carlos Palminha <CAR= LOS.PALMINHA@synopsys.com> wrote:
Hi guys= ,

I'm writing a DRM driver for a framebuffer embedded hardware that uses = an i2c encoder (adv7511), following the basic steps suggested by Laurent in= "anatomy of an embedded KMS driver": https:/= /www.youtube.com/watch?v=3DJa8fM7rTae4

After initiliazing all kms, crtc, encoder, i2c, connector functions and str= uctures i'm calling drm_fbdev_cma_init to create a fbdev.

When booting i'm getting an error message saying "No connectors re= ported connected with modes", but the driver init is ok and i can find= the /dev/dri/* and /dev/fb0 devices.

Any clue what i might be missing during the driver load?

=E2=80=8BI think you should check on the 'get_mode= s'=E2=80=8B call back of adv7511 driver. (Or, if possible show us the c= ode.)

Best,
-xinliang
=C2=A0

Thanks...

Regards,
C.Palminha

--- boot log snippet ---
[drm] Initialized drm 1.1.0 20060810
drm-arcpgu e0017000.pgu: No connectors reported connected with modes
[drm] Cannot find any crtc or sizes - going 1024x768
Console: switching to colour frame buffer device 128x48
drm-arcpgu e0017000.pgu: fb0:=C2=A0 frame buffer device
[drm] Initialized drm-arcpgu 1.0.0 20151127 on minor 0
--- boot log snippet ---
--
To unsubscribe from this list: send the line "unsubscribe linux-fbdev&= quot; in
the body of a message to majordomo@vger.kernel.org
More majordomo info at=C2=A0 http://vger.kernel.org/majord= omo-info.html

--047d7b2e4e38f7d0d105282849c4-- --===============1819085676== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHA6Ly9saXN0 cy5mcmVlZGVza3RvcC5vcmcvbWFpbG1hbi9saXN0aW5mby9kcmktZGV2ZWwK --===============1819085676==--