On Wed, 14 Jan 2015, Robert Kuhn <robert@xxxxx> 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@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
