search

cdsteinkuehler / beaglebone-universal-io

Device tree overlay and support scripts for using most available hardware I/O on the BeagleBone without editing dts files or rebuilding the kernel
GNU General Public License v2.0
128 stars 54 forks source link

Why no setting with HDMI disabled? #7

Closed jadonk closed 10 years ago

jadonk commented 10 years ago

I'm so confused. I thought one of these was with HDMI disabled, but none of them seem to actually use the HDMI pins. What is going on here?

verminsky commented 10 years ago

Jason - I got this from Charles back in May - does it help you? From: Charles Steinkuehler charles@steinkuehler.net Date: Wednesday, May 28, 2014 at 3:48 PM To: John Cutler verminsky@earthlink.net Subject: Re: config-pin for Debian BBB question

On 5/28/2014 5:43 PM, John Cutler wrote: Charles: Your config-pin is working well. I do have a couple of questions though… What is the difference between cape-universal and cape-universaln ? Also, what is cape-universal-emmc? All 3 are in /lib/firmware on my debian BBB 3.8.13-bone 54 running from eMMC The cape-universaln is the one that is working on this board for me…

The universal and universaln match up with the HDMI and HDMIN "capes".

universal & HDMI: These both grab the audio pins

universaln & HDMIN: These leave the audio pins alone.

So, you can load both 'n' versions, or one each 'n' and 'not-n', but you can't load both 'not-n' versions or you have two capes trying to claim the same pins.

The universal-emmc cape takes over the eMMC pins, and can only be loaded if you disable the virtual eMMC cape.

There will eventually be a cape-universal-hdmi that will support use of the HDMI/LCD pins if you disable the loading of the HDMI "cape".

Charles Steinkuehler charles@steinkuehler.net

cdsteinkuehler commented 10 years ago

On 7/10/2014 11:44 AM, Jason Kridner wrote:

I'm so confused. I thought one of these was with HDMI disabled, but none of them seem to actually use the HDMI pins. What is going on here?

I haven't made the overlay that takes over the HDMI pins yet. :(

Charles Steinkuehler charles@steinkuehler.net

adityapatadia commented 10 years ago

I think this issue is now solved and the universal and HDMI file does exactly what it is supposed to do. I have implemented it in octalbonescript. You can check the implementation here: https://github.com/theoctal/octalbonescript

cdsteinkuehler commented 10 years ago

You are correct. The HDMI pins have been added (Thanks jstampfl!), but I neglected to close this issue. Any actual problems with the HDMI overlay should have a new issue created.