Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 22 May 2015 08:27:30 +0300
From:      Daniel Braniss <danny@cs.huji.ac.il>
To:        Ian Lepore <ian@FreeBSD.org>
Cc:        hackers@freebsd.org, current@freebsd.org
Subject:   Re: OF_getprop weirdness - raspberry pi
Message-ID:  <288BCD94-70F2-46B1-80F8-9755678E3D3F@cs.huji.ac.il>
In-Reply-To: <1432218339.1208.1.camel@freebsd.org>
References:  <D0B40E58-32EB-4CFE-950E-78EAA05E9018@cs.huji.ac.il> <1432218339.1208.1.camel@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help


> On May 21, 2015, at 5:25 PM, Ian Lepore <ian@FreeBSD.org> wrote:
> 
> On Thu, 2015-05-21 at 09:41 +0300, Daniel Braniss wrote:
>> Hi,
>> I’m running current as of last week on a raspberry pi B.
>> 
>> i don’t know if this only related to arm, but this is what I have in my rpi-b.dts:
>> 	….
>> 		spi0 {
>> 		     rfid0 {
>> 		     	   compatible = "rfid,mfrc5";
>> 			   spi-chipselect = <0>;
>> 			   reset {
>> 			   	 compatible = "pcd-reset";
>> 				 gpios = <&gpio 6 2>;
>> 			   };
>> 			   lock {
>> 			   	compatible = "lock-1";
>> 				gpios = <&gpio 13 2>;
>> 			   };
>> 			   sense {
>> 			   	 compatible = "sense-1";
>> 				 gpios = <&gpio 19 1>;
>> 			   }; 
>> 		     };
>> …
>> and a call to
>> 	uint32_t data[3];
>> 	
>> 	OF_getprop(node, “gpios”, data, sizeof(data)); // node is ‘pcd-reset'
>> 	returns:
>> 		data[0]: 0x03000000
>> 		data[1]: 0x06000000
>> 		data[2]: 0x02000000
>> 
>> which looks to me that it’s in the wrong endian?
>> 
>> cheers,
>> 	danny
> 
> FDT data is always big-endian, use OF_getencprop() to unpack it to host
> format.
> 

thanks!
is there (apart from the source), some man pages, doc? so far I found outdated,
or incomplete info.

	danny

> -- Ian




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?288BCD94-70F2-46B1-80F8-9755678E3D3F>