Trying to come to grips with the myriad of source trees from which BeagleBoard related source can be pulled, I updated the BeagleBoard build system the other day to make it easier to pull from the various archives.\u00a0 Technically there are four ways to get source related to BeagleBoard:<\/p>\n
Currently pulling from GIT archives and HTTP sites are supported but extending this to other protocols wouldn’t be particularly hard.\u00a0 Fortunately, most of this code is being managed with GIT.<\/p>\n
The main archives are either kernel.org<\/a> (for the kernel) or denx.de<\/a> (for the bootloader, u-boot).\u00a0 Both sites also have GIT repositories.\u00a0 The gitorious.org<\/a> site appears to have BeagleBoard developer branches that eventually get pushed to the main archive GIT repositories, which have their own repos and branches that merge their way into the mainlines.\u00a0 Then there are developer-specific GIT repositories that have special versions of code that hasn’t been pushed upstream to gitorious.org and\/or the mainlines.\u00a0 The latter I have yet to deal with but I know they can exist.<\/p>\n The BeagleBox build now allows selection of which repository to pull from based on configs\/<component>-<repo>.cfg<\/span> files.\u00a0 The repo can be specified with environment variables, such as KSRC=gitorious and KSRC=org for the kernel pulling from gitorious or kernel.org or USRC=git or USRC=gitorious for pulling from denx.de GIT or gitorious.org, respectively.\u00a0 The <component>-showconfig targets show which configurations are available to choose from.\u00a0 Additional repos and configurations (branches or commits to pull from, for example) can be added fairly easily using on of the existing configs as an example.\u00a0 This is similar in use to recipes in Angstrom but the implementation is based on make<\/em> instead of bitbake<\/em>.<\/p>\n After putting all this together I can build a variety of combinations of u-boot and kernel.\u00a0 My goal at this point is to get a working S-Video display from my BeagleBoard.\u00a0 So far, only the validation image builds of u-boot and the kernel have generated any TV output.\u00a0 However, those builds appear to use DSS1, the original display support for OMAP processors.\u00a0 DSS2 is the rewritten version and the one I’d like to be using.\u00a0 Unfortunately, no combination of u-boot and kernel, as of yet, has found any display devices for use with DSS2.\u00a0 Not even DVI.\u00a0 I have a TV connected to the S-Video port and the TV is turned on prior to booting the board.\u00a0 The HDMI port is not connected to anything.\u00a0 Assuming autoprobing I would expect to see the TV display configured but not the DVI.\u00a0 Still, I have no displays at all.<\/p>\n At this point I’m nearing the end of my trial-and-error approach to finding DSS2 support for TV-out (re: S-Video).\u00a0 My next test is with u-boot’s 2010.09 (mainline GIT) and a kernel from gitorious.org that is from the DSS2 developer (linux-omap-dss2<\/a>), which is based on Linux 2.6.37.\u00a0 If this test doesn’t work, then I’m going to disable the bootloader config check (CONFIG_FB_OMAP_BOOTLOADER_INIT) in the kernel and try again.\u00a0 That should force the kernel to enable DSS2 displays without any help from the bootloader.<\/p>\n If that doesn’t work, it’s time to start pinging developers.\u00a0 I’m just not sure who to ping first.\u00a0 Posts about this to the BeagleBoard mailing list have not generated much response and my assumption based on posts to the list is that everyone is doing either HDMI or DVI-D (via HDMI) or has a VGA daughterboard on their BeagleBoards.\u00a0 Not much TV-out discussion there that I’ve seen recently.\u00a0 The other option is the linux-omap<\/strong> mailing list mentioned<\/a> by the maintainer of the linux-omap-dss2 repo<\/a> (Tomi’s kernel tree<\/a> is the link from elinux.org.) on gitorious.org.\u00a0 However, he doesn’t say where you can go to get on or access that list.\u00a0 So I’ll have to google around to find it (maybe elinux.org has a link).<\/p>\n","protected":false},"excerpt":{"rendered":" Trying to come to grips with the myriad of source trees from which BeagleBoard related source can be pulled, I updated the BeagleBoard build system the other day to make it easier to pull from the various archives.\u00a0 Technically there are four ways to get source related to BeagleBoard: A compressed tarball from a main […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ngg_post_thumbnail":0,"jetpack_post_was_ever_published":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false},"version":2}},"categories":[390,8,5,6],"tags":[447,376,381,454,445,497,484,496,115,252,439,495,248],"class_list":{"0":"post-800","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-beaglebox-hardware","7":"category-hardware","8":"category-linux","9":"category-software-development","10":"tag-angstrom","11":"tag-beagleboard","12":"tag-beaglebox","13":"tag-bootloader","14":"tag-dss","15":"tag-dvi-d","16":"tag-git","17":"tag-hdmi","18":"tag-kernel","19":"tag-omap","20":"tag-s-video","21":"tag-tv-out","22":"tag-video-display","23":"czr-hentry"},"jetpack_publicize_connections":[],"aioseo_notices":[],"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/pe9t8-cU","jetpack_sharing_enabled":true,"jetpack-related-posts":[],"jetpack_likes_enabled":true,"_links":{"self":[{"href":"https:\/\/www.graphics-muse.org\/wp\/index.php?rest_route=\/wp\/v2\/posts\/800","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.graphics-muse.org\/wp\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.graphics-muse.org\/wp\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.graphics-muse.org\/wp\/index.php?rest_route=\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.graphics-muse.org\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=800"}],"version-history":[{"count":5,"href":"https:\/\/www.graphics-muse.org\/wp\/index.php?rest_route=\/wp\/v2\/posts\/800\/revisions"}],"predecessor-version":[{"id":804,"href":"https:\/\/www.graphics-muse.org\/wp\/index.php?rest_route=\/wp\/v2\/posts\/800\/revisions\/804"}],"wp:attachment":[{"href":"https:\/\/www.graphics-muse.org\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=800"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.graphics-muse.org\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=800"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.graphics-muse.org\/wp\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=800"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}