From: Tomi Valkeinen <tomi.valkeinen@ti.com>
To: Javier Martinez Canillas <javier@dowhile0.org>,
Koen Kooi <koen@dominion.thruhere.net>
Cc: Linux OMAP Mailing List <linux-omap@vger.kernel.org>
Subject: Re: Display not working if omapdrm is builtin with 3.15rc
Date: Fri, 2 May 2014 15:00:49 +0300 [thread overview]
Message-ID: <536388F1.7050304@ti.com> (raw)
In-Reply-To: <CABxcv==fYi6fhTj9_qdoozooi6Su7KCao+GY9cx242_BwvC+Ew@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1061 bytes --]
On 02/05/14 14:25, Javier Martinez Canillas wrote:
> Hello Koen,
>
> On Fri, May 2, 2014 at 12:47 PM, Koen Kooi <koen@dominion.thruhere.net> wrote:
>> Hi,
>>
>> I've been trying to get DVI on my beagleboard XM to output a picture with mainline and with 3.15rc it still doesn't work. If I statically build in everything the drm encoders and connectors all go into deferred probe mode and fail, falling back to 1024x768. I with omapdrm and encoders/outputs/etc as modules deferred probe is avoided, far fewer error messages and a 1280x1024 resolution is being used. But still the monitor still says 'no signal' detected.
>>
>> So what's the magic to get an actual signal on the hdmi connector?
>>
>> regards,
>>
>> Koen--
>
> This is a known issue as far as I know. You need [0] to correctly set
> the display PLL clock rates.
>
> Best regards,
> Javier
>
> [0]: http://permalink.gmane.org/gmane.linux.ports.arm.kernel/295077
Different board, different problem. The link talks about beaglebone,
Koen about beagleboard.
Tomi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-05-02 12:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-02 10:47 Display not working if omapdrm is builtin with 3.15rc Koen Kooi
2014-05-02 11:25 ` Javier Martinez Canillas
2014-05-02 11:55 ` Koen Kooi
2014-05-02 12:00 ` Tomi Valkeinen [this message]
2014-05-02 11:59 ` Tomi Valkeinen
2014-05-02 12:33 ` Koen Kooi
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=536388F1.7050304@ti.com \
--to=tomi.valkeinen@ti.com \
--cc=javier@dowhile0.org \
--cc=koen@dominion.thruhere.net \
--cc=linux-omap@vger.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.