2. > Why is a DT used to define the HDMI Because this is a system-on-chip. The HDMI, gpio, gpu, pruss, etc are all peripherals of the cpu that are located on the chip, but still separate from the cpu.
3. If you just want to get gpio or leds working quickly, check out this post: https://groups.google.com/d/msg/beagleboard/75suL1Mhzao/FBZr4gPM2wkJ And, make sure you have the latest production image and check out the /lib/firmware path. I think there's a device tree overlay for about everything on chip now. On Sunday, October 6, 2013 12:19:55 AM UTC-7, Amalinda J' Gamage wrote: > > > thank you Pedro and Przemek . > > I read through the materiel provided but I still have some doubts. > > 1. Do you know a place where a very beginner coming from TI > microcontrolers (e.g. MSP430 and ARM Cortex M) can learn this embedded > linux from the begining? can you provide a guidance? a series of videos or > an extemely good book or some really good source? because I dont seem to > get the hang of these stuff by going through posts and blogs because none > start from scratch. I haven't taken any units on e linux in uni either. > > > 2. Okay, I now get a little bigger picture that DTs are used to define > external hardware that can be or are already connected to the ARM Cortex A. > So, Why is a DT used to define the HDMI eMMC? It is because the > new Linux kernel has not included any hardware definitions for HDMI and > eMMC ? > > 3. Is it possible that GPIOs be programmed without doing anything with > Device trees using the new Linux Kernel in the BBB? > > thank you a lot for responses. > > > > > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
