Beagleboard xM DVI

[overoarm]

I should have my xm in a few days, but I believe the hdmi is like my overo's expansion that I use for when at a desk. The hdmi is not a true hdmi signal and its basically a dvi-d signal coming out of it and if your TV does not handle that digital signal at all or through a hdmi plug it will not work.

For me it works with some TV's and not with other's both with using a hdmi to hdmi in TV and hdmi to dvi-d in TV.

Don't hold me to it but HTH

edit:
Just looked on a spec page and it is the same it is a dvi-d signal out of the hdmi plug.

[brad0383]

I know it is is DVI-D. HDMI is backwards compatible with DVI-D, video only of course.

[overoarm]

Then wouldnt that mean any HDMI TV would automatically work and be able to read the DVI-D signal, especially if you are sending the correct resolution and info that works on HDMI for that same TV? Because from my testing not every TV can actually do that. But I could totally be wrong. Also have seen the same mentioned on beagleboard BBS's as well as on gumstix BBS's.

[brad0383]

That is what I am asking. I believe I need to set the output to 720p @ 60 Hz. I think I found a bigger problem however. I am trying to get XBMC working and it looks like there isn't a xf86-video-omap package available for Arch Arm.

[overoarm]

$this->bbcode_second_pass_code('', 'omapfb.mode=dvi:1024x768MR-16@60 omapdss.def_disp=dvi vram=12M')that is the uboot variable you should be passing for 720p. I use this variable all the time and like I stated earlier I do not have luck with every TV that has a HDMI plug. Some see it and accept it as 720p others do not. Seems the older the TV with HDMI the better chance it will not work for me. But that's just my luck and experience.

From my understanding a DVI-D signal is not the same as a true HDMI signal regardless of the settings you pass and this is what gives the difficulty on some TV's. Not trying to say you're wrong by any means just been dealing with this since 2010 in the gumstix world. Tracking says my xm arrives today, I have a TV here that will not accept DVI-D through its HDMI and will test once I get Arch on the XM.

xf86-video-omapfb is available in the repo's

edit: added more info and put in code blocks

[brad0383]

XBMC fails and gives me an error that it requires 24 bit color depth. Also, xf86-video-omapfb gave me an error that is was not found. Anyways, I have shelved the XM for the time begin, more pressing things. Thanks for the help.

[overoarm]

if you can not find it in the repos sounds like you need to refresh pacman. -Syyuu. I just checked on my running alarm and it comes up. You could always do a search with -Ss xf86-video- because it comes up on all 8 of my overo's running alarm.

If I figure out anything on mine when I try I will post it here in case it helps you as well. Are you sure a touchscreen driver is not being loaded? I know on my fresh alarm install I had to blacklist the touchscreen driver or else for some reason no matter the uboot variable it would try and load a touchscreen, after updating and configuring things it was still an issue, the kernel I have been building for my overo's does not have the problem of trying to load the touchscreen driver regardless, but may not be the same on yours. Maybe try building a newer uboot.bin and MLO. Never used xbmc before, but sounds like the wrong driver not getting in there. Hopefully it does not stay on the shelf too long :p

[overoarm]

Just thought of this as well I passed you a 16bit variable
$this->bbcode_second_pass_code('', 'omapfb.mode=dvi:1024x768MR-24@60 omapdss.def_disp=dvi vram=12M') Sorry about that you should also be able to change to 32

edit:
Also found this
$this->bbcode_second_pass_code('', 'For 16bit:
console=ttyS0,115200n8=noinitrd ip=dhcp rw root=/dev/mmcblk0p2 omapfb.mode=dvi:1280×720MR-16@60

For 32bit:
console=ttyS0,115200n8=noinitrd ip=dhcp rw root=/dev/mmcblk0p2 omapfb.mode=dvi:1280×720MR-24@60

followed by:

/usr/sbin/fbset.real -depth 32 -rgba 8/16,8/8,8/0,8/24') These were listed on a beagleboard bbs and seem to be the way beagleboard-xm wants the variables you need. Of course edit out the parts you do not need I just c/p the whole string.

HTH

[brad0383]

Thanks for the info, this will be helpful. I may have to pull it off the shelf sooner then I thought! What touchscreen driver did you blacklist?

$this->bbcode_second_pass_quote('overoarm', '[')code]omapfb.mode=dvi:1024x768MR-16@60 omapdss.def_disp=dvi vram=12M[/code]that is the uboot variable you should be passing for 720p.