On Thu, 2009-02-19 at 17:21 +0530, Vijay Nikam wrote:
> Also is it possible to compile device tree on Linux host and genreate
> dtb for powerpc ? ? ? If yes, then how ? ? ? please let me know ...
> thanks ...
Uh, get a copy of the DTC using:
$ git clone git://git.jdl.com/software/dtc.git
> Because dtc will generate phandles automatically when you reference the
> node with the & operator.
Yes the same statement I found in dts-bindings for gpio txt, sorry I
missed it somehow ...
> Do you want your changes to ever make it into the upstream kernel?
Yes I would like to do that ... bu
On Wed, Feb 18, 2009 at 05:31:34PM +0530, Vijay Nikam wrote:
> > Don't specify this explicitly. Please base new development off of the
> > device tree that is in upstream Linux, not the very old tree in your BSP.
>
> May I know the reason why I should not specify it explicitly ? ? ?
Because dtc
I checked and read the
Documentation/powerpc/dts-bindings/fsl/8xxx_gpio.txt and
booting-without-of.txt. It is different then what I read before from
booting-without-of.txt ... perhaps as it is old and came with BSP. Am
I right ? ? ?
> Don't specify this explicitly. Please base new development off
Vijay Nikam wrote:
I added the gpio node as follows to mpc8313erdb.dts;
g...@c00 {
linux,phandle = ;
Don't specify this explicitly. Please base new development off of the
device tree that is in upstream Linux, not the very old tree in your BSP.
device_type = "gpio";
No d
I added the gpio node as follows to mpc8313erdb.dts;
g...@c00 {
linux,phandle = ;
device_type = "gpio";
compatible = "";
reg = ;
interrupts = <4a 8>;
interrupt-parent = <700>;
};
The only thing I need to know what should I write at 'compatib
On Mon, Feb 16, 2009 at 05:25:23PM +0530, Vijay Nikam wrote:
> 2. Also I would like to ask how I can determine the virtual irq using
> irq_of_parse_and_map (struct device_node *dev, int index) ? ? ?
>
> here I am not getting what I should pass *dev and index ? ? ? as in my
> mpc8313erdb.dts I cou
Hello All,
I have mpc8313erdb evaluation board and writing GPIO driver for it. I
know that it is not possible to use directly hardware_irq_number given
from the processor manual. In my case hardware _irq_number is 74 (for
GPIO). As request_irq uses the virtual irq.
So to know or determine what vi
