* Subject: Problems with of_find_compatible_node
@ 2013-10-01 16:23 Vishwas Srivastava
2013-10-11 14:49 ` chrishell
0 siblings, 1 reply; 2+ messages in thread
From: Vishwas Srivastava @ 2013-10-01 16:23 UTC (permalink / raw)
To: kernelnewbies
Hi Chris,
probably you can do cat /proc/device-tree o/p to see if such
a node exist in the device tree file.
also you can check
arch/ppc/boot/dts/ directory and check the .dts file to check if such an
entry really exist in the .dts file which
you are using.
Since in your case
np = of_find_compatible_node(NULL,NULL,
"xilinx,cpld-led");
returns NULL, its a sign that the entry does not exist in the .dts file
your system is using.
thnaks,
Vishwas S
Hello out there,
I got a problem with the kernel function "of_find_compatible_node". I
use it with: np = of_find_compatible_node(NULL,NULL,
"xilinx,cpld-led"); or with np = of_find_compatible_node(NULL,NULL,
"cpld-led"); but none of this works, because I get a null-pointer back.
But it suppose to work? The target is a PPC-walnut-board.
Which is the mechanism behind this function, which namespace is parsed
in order to detect devices on the board? Can I parse the whole namespace
in order to list up all devices?
What else can I do to solve this problem?
Thank you in advance...
Regards /chris
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20131001/1d4f4d59/attachment.html
^ permalink raw reply [flat|nested] 2+ messages in thread
* Subject: Problems with of_find_compatible_node
2013-10-01 16:23 Subject: Problems with of_find_compatible_node Vishwas Srivastava
@ 2013-10-11 14:49 ` chrishell
0 siblings, 0 replies; 2+ messages in thread
From: chrishell @ 2013-10-11 14:49 UTC (permalink / raw)
To: kernelnewbies
Hello Vishwas,
thanks for your reply. But I don not have a /proc/device-tree at all. I
solved the problem by writing a appropriate node into the .dts-file and
recompile the whole kernel. I exchanged also "xilinx,cpld-led" with
"cpld-led". After that it worked.
Regards /Chris
> Hi Chris,
> probably you can do cat /proc/device-tree o/p to see if such
> a node exist in the device tree file.
> also you can check
> arch/ppc/boot/dts/ directory and check the .dts file to check if such an
> entry really exist in the .dts file which
> you are using.
>
> Since in your case
> np = of_find_compatible_node(NULL,NULL,
> "xilinx,cpld-led");
> returns NULL, its a sign that the entry does not exist in the .dts file
> your system is using.
> thnaks,
> Vishwas S
>
>
>
> Hello out there,
> I got a problem with the kernel function "of_find_compatible_node". I
> use it with: np = of_find_compatible_node(NULL,NULL,
> "xilinx,cpld-led"); or with np = of_find_compatible_node(NULL,NULL,
> "cpld-led"); but none of this works, because I get a null-pointer back.
> But it suppose to work? The target is a PPC-walnut-board.
> Which is the mechanism behind this function, which namespace is parsed
> in order to detect devices on the board? Can I parse the whole namespace
> in order to list up all devices?
>
> What else can I do to solve this problem?
>
> Thank you in advance...
>
> Regards /chris
>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: OpenPGP digital signature
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20131011/66ccb260/attachment.bin
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2013-10-11 14:49 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-10-01 16:23 Subject: Problems with of_find_compatible_node Vishwas Srivastava
2013-10-11 14:49 ` chrishell
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).