From: Jani Nikula <jani.nikula@linux.intel.com>
To: Robert Kuhn <robert@ku.hn>, dri-devel@lists.freedesktop.org
Subject: Re: boot delay with drm_kms_helper.edid_firmware
Date: Thu, 15 Jan 2015 10:59:41 +0200 [thread overview]
Message-ID: <87387cfmgy.fsf@intel.com> (raw)
In-Reply-To: <CAES30Qn6dU8n5=Ecdu3_66onCRS-4Ffbp5mgSWOKhaBeDhnp8Q@mail.gmail.com>
On Wed, 14 Jan 2015, Robert Kuhn <robert@ku.hn> wrote:
> thanks for the answer. I believe I got it. I did not know that there are
> already some edids build into the kernel. What I did try to achieve is that
> my edid placed in the file system (under /lib/firmware/edid/) is loaded on
> boot. I named my special edid file also 1024x786.bin so I never noticed
> that my file wasn't loaded. Instead the edid build into the kernel was
> used. Got it.
>
> For testing I renamed my edid to myedid.bin. Now I got (of course):
> [ 0.767201] pinctrl-single 44e10800.pinmux: pin 44e10854 already
> requested by 44e10800.pinmux; cannot claim for gpio-leds.8
> [ 0.778895] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status
> -22
> [ 0.786166] pinctrl-single 44e10800.pinmux: could not request pin 21 on
> device pinctrl-single
> [ 61.001555] [drm:edid_load] *ERROR* Requesting EDID firmware
> "edid/myedid.bin" failed (err=-2)
>
> But there is the file:
> debian@beaglebone:~$ ls -ls /lib/firmware/edid/
> total 4
> 4 -rw-r--r-- 1 debian debian 128 Feb 17 2014 myedid.bin
Hmm, you have drm and drm_kms_helper built-in to the kernel. If you're
using an initrd, I believe the firmware loader will look there instead
of your rootfs. I am not sure if having the modules loadable but still
in initrd helps, probably not. You may need to have the modules in
rootfs or put the edid in initrd. It gets a bit tricky.
> So with 3.8. its not possible to tell the kernel to load the buildin first?
That seems to be the case.
> Okay, then I will try the v3.18.x branch for Beaglebone.
Good luck!
> Thanks!
No problem.
BR,
Jani.
--
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2015-01-15 8:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 7:40 boot delay with drm_kms_helper.edid_firmware Robert Kuhn
2015-01-14 10:40 ` Jani Nikula
2015-01-14 11:42 ` Robert Kuhn
2015-01-14 13:32 ` Jani Nikula
2015-01-14 15:21 ` Robert Kuhn
2015-01-15 8:59 ` Jani Nikula [this message]
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=87387cfmgy.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=robert@ku.hn \
/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.