All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos Palminha <CARLOS.PALMINHA@synopsys.com>
To: laurent.pinchart@ideasonboard.com,
	dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org
Cc: tomi.valkeinen@ti.com, CARLOS.PALMINHA@synopsys.com
Subject: Whats missing in my new FB DRM driver... "No connectors reported connected with modes"?
Date: Wed, 30 Dec 2015 18:53:14 +0000	[thread overview]
Message-ID: <5684281A.7040300@synopsys.com> (raw)
In-Reply-To: <5684268E.2000607@synopsys.com>

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=Ja8fM7rTae4

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?

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 ---

WARNING: multiple messages have this Message-ID (diff)
From: Carlos Palminha <CARLOS.PALMINHA@synopsys.com>
To: laurent.pinchart@ideasonboard.com,
	dri-devel@lists.freedesktop.org, linux-fbdev@vger.kernel.org
Cc: tomi.valkeinen@ti.com, CARLOS.PALMINHA@synopsys.com
Subject: Whats missing in my new FB DRM driver... "No connectors reported connected with modes"?
Date: Wed, 30 Dec 2015 18:53:14 +0000	[thread overview]
Message-ID: <5684281A.7040300@synopsys.com> (raw)

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=Ja8fM7rTae4

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?

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 ---
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  reply	other threads:[~2015-12-30 18:53 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-30 18:46 Whats missing in my new FB DRM driver... "No connectors reported connected with modes"? Carlos Palminha
2015-12-30 18:53 ` Carlos Palminha [this message]
2015-12-30 18:53   ` Carlos Palminha
2015-12-31  2:19 ` Xinliang Liu
2016-01-18 14:32   ` Carlos Palminha
2016-01-18 14:32     ` Carlos Palminha
2016-01-18 14:45     ` Carlos Palminha
2016-01-18 14:45       ` Carlos Palminha
2016-01-19  3:38       ` Xinliang Liu
2016-01-19 16:03         ` Carlos Palminha
2016-01-19 16:03           ` Carlos Palminha
2016-01-19 16:52           ` Carlos Palminha
2016-01-19 16:52             ` Carlos Palminha
2016-01-20  1:24             ` Xinliang Liu
2016-01-20  1:24               ` Xinliang Liu
2016-01-21 18:09               ` Carlos Palminha
2016-01-21 18:09                 ` Carlos Palminha
2016-01-21 18:30                 ` Whats missing in my new FB DRM driver in ARC... waiting for console_lock to return Carlos Palminha
2016-01-21 18:30                   ` Carlos Palminha
2016-01-21 18:30                   ` Carlos Palminha
2016-01-22  8:32                   ` Daniel Stone
2016-01-22  8:32                     ` Daniel Stone
2016-01-22  8:32                     ` Daniel Stone
2016-01-28 14:20                   ` Alexey Brodkin
2016-01-28 14:20                     ` Alexey Brodkin
2016-01-28 14:20                     ` Alexey Brodkin
2016-01-28 15:42                     ` Rob Clark
2016-01-28 15:42                       ` Rob Clark
2016-01-28 15:42                       ` Rob Clark
2016-01-22  7:41                 ` Whats missing in my new FB DRM driver... "No connectors reported connected with modes"? Daniel Vetter
2016-01-22  7:41                   ` Daniel Vetter
2016-01-22  8:34                   ` Daniel Stone
2016-01-22  8:34                     ` Daniel Stone

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=5684281A.7040300@synopsys.com \
    --to=carlos.palminha@synopsys.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-fbdev@vger.kernel.org \
    --cc=tomi.valkeinen@ti.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 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.