From the EDID traces, it doesn't look like the monitor advertises 1920x1080 as a supported resolution. So the display driver is doing the "correct" thing and picking the highest supported resolution, which happens to be a VESA mode instead of CEA mode.
There is one possibility, in earlier versions of the drm driver, in omap_connector.c, there was a:
#define MAX_EDID 256
which should have been:
#define MAX_EDID 512
there is a slim chance that this is causing it to miss a 1920x1080 mode. Although I would have expected the 1080p timings to be in the first 128byte block of the EDID.
Beyond that, you need the pvr accelerated xorg driver (default xf86-video-fbdev does not support KMS) to support changing resolution. Or you can use bootargs to force 1280x720. I guess that should be enough to make HDMI audio to work, or at least get the driver to pick a CEA mode, which I think is required for HDMI audio to work.
The bit about aplay segfaulting sounds like a different issue.. at least that part is not related to the display driver so I can't say anything intelligent about that ;-)
From the EDID traces, it doesn't look like the monitor advertises 1920x1080 as a supported resolution. So the display driver is doing the "correct" thing and picking the highest supported resolution, which happens to be a VESA mode instead of CEA mode.
There is one possibility, in earlier versions of the drm driver, in omap_connector.c, there was a:
#define MAX_EDID 256
which should have been:
#define MAX_EDID 512
there is a slim chance that this is causing it to miss a 1920x1080 mode. Although I would have expected the 1080p timings to be in the first 128byte block of the EDID.
Beyond that, you need the pvr accelerated xorg driver (default xf86-video-fbdev does not support KMS) to support changing resolution. Or you can use bootargs to force 1280x720. I guess that should be enough to make HDMI audio to work, or at least get the driver to pick a CEA mode, which I think is required for HDMI audio to work.
The bit about aplay segfaulting sounds like a different issue.. at least that part is not related to the display driver so I can't say anything intelligent about that ;-)
BR,
-R