On Fri, Sep 7, 2012 at 12:08 AM, Jon <jdisnard(a)gmail.com> wrote:
On Tue, Aug 28, 2012 at 1:51 AM, Peter Robinson
> On Tue, Aug 28, 2012 at 3:55 AM, Jon <jdisnard(a)gmail.com> wrote:
>>>> Error: could not insert
>>>> Unknown symbol in module
>>> you should just do "modprobe omapdrm" not insmod the .ko as it
>>> care of its deps.
>> That worked, the omapdrm module loaded with modprobe.
>> Unfortunately that does not cause the HDMI video to suddenly start
>> Also, the path in sysfs was not present after loading the module:
> Thinking back to the 3.5 dev cycle in rawhide there was quite a bit of
> churn in the OMAP video stuff to do with the DSS module, it's possible
> we'll need to tweak the F-17 kernel build. Not sure if I'll get time
> to do that this week.
> I want to bring the config restructure back to F-17 but OMAP at least
> has some issues with USB on that build so I need to get the time to
> test all the various HW devices we vaguely support such as Panda,
> Beagle, Trimslice, Highbank, and VExpress. We know the imx at least
> vaguely works. For 3.5+ we really need to move to DeviceTree and I
> wonder if that isn't at least part of the issue with the video on 3.5
Diffed the configs for 3.4.2-3 and 3.5.2-3.
The 3.4 kernel had these kernel config's:
That would likely affect DVI but not HDMI.
They're the sound components for digital sound over the HDMI port so
won't affect video.
Could that contribute to the lack of HDMI/DVI-D on pandaboard on the
Possibly in addition to the omapdrm module not loading during boot?
Partially, I'm just looking at it now while I think of it.