Re: [beagleboard] Device Tree Overlay ? why do we need it?

2013-10-06 Thread Amalinda J' Gamage
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

Re: [beagleboard] Device Tree Overlay ? why do we need it?

2013-10-06 Thread David Goodenough
On Sunday 06 Oct 2013, Amalinda J' Gamage wrote: I am a new user to beaglebone and I have a couple of basic questions. I want to know what is meant by DT or Device tree overlay and why it is required for BB/ ARM335X. Is it not required for other main processors like Intel because they are

Re: [beagleboard] Device Tree Overlay ? why do we need it?

2013-10-06 Thread Amalinda J' Gamage
Dear garyamort, Since the book is written for the Linux Kernel version 3.2 and the current version is 3.8 do you think I will have any problem? awaiting your reply. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google

Re: [beagleboard] Device Tree Overlay ? why do we need it?

2013-10-06 Thread David Lambert
I think this rant from Linus explains it all ;) http://article.gmane.org/gmane.linux.ports.arm.omap/55060 On 13-10-05 11:07 PM, Amalinda J' Gamage wrote: I am a new user to beaglebone and I have a couple of basic questions. I want to know what is meant by DT or Device tree overlay and why it

Re: [beagleboard] Device Tree Overlay ? why do we need it?

2013-10-06 Thread garyamort
On Sunday, October 6, 2013 11:38:31 AM UTC-4, Amalinda J' Gamage wrote: Dear garyamort, Since the book is written for the Linux Kernel version 3.2 and the current version is 3.8 do you think I will have any problem? awaiting your reply. It includes both versions - the examples

Re: [beagleboard] Device Tree Overlay ? why do we need it?

2013-10-06 Thread Brandon I
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:

Re: [beagleboard] Device Tree Overlay ? why do we need it?

2013-10-06 Thread Amalinda J' Gamage
thank you David Lambert , G aryamort and Brandon , appreciate your time spent! I'm planing to buy the book recomended. I think it might stop me from wandering around with my problems:-) and that means using previous Kernel in the beaglebone its possible that we connect an LED in series with a

Re: [beagleboard] Device Tree Overlay ? why do we need it?

2013-10-06 Thread Pedro A. Melendez
this blog have a lot of helpful DT stuff http://hipstercircuits.com/ On Sun, Oct 6, 2013 at 3:48 PM, Amalinda J' Gamage amalinda.gam...@gmail.com wrote: thank you David Lambert , G aryamort and Brandon , appreciate your time spent! I'm planing to buy the book recomended. I think it might

[beagleboard] Device Tree Overlay ? why do we need it?

2013-10-05 Thread Amalinda J' Gamage
I am a new user to beaglebone and I have a couple of basic questions. I want to know what is meant by DT or Device tree overlay and why it is required for BB/ ARM335X. Is it not required for other main processors like Intel because they are defined in the Linux kernel? and TI ARM3358

Re: [beagleboard] Device Tree Overlay ? why do we need it?

2013-10-05 Thread Pedro A. Melendez
DT simplify kernel development for arm processor as they tend to vary on features, its easier to make a general formula than custom driver for each processor. I think this link will answer your quetions https://github.com/jadonk/validation-scripts/tree/master/test-capemgr -Pedro

Re: [beagleboard] Device Tree Overlay ? why do we need it?

2013-10-05 Thread Przemek Klosowski
That's a good question---I think the reason is that ARM has much wider choice of peripherals that tend to be simpler than typical peripherals on the x86 architecture. On x86, they are usually connected using the PCI infrastructure, which configures their register and interrupt layout at boot and