Hi Alan,

We are now able to confirm that device ".name" and 
".modalias" inside board configuration have got the same value.

Everything seems fine and correctly executed during boot sequence.

We've made the driver as a loadable module. Then when we "modprobe" the module 
it correctly start/init and register. BUT definitely we never go through it's 
"probe" function.
We are expecting a new physical driver that could be detected with the "iz 
listphy" userspace tool from Linux-zigbee (like a "wpan-phyX" interface). Is 
that ok ? 

Have you got any idea about what we are missing ?

Maybe something to do on user side ?

Have you got any idea of where we could find the task that "probe" existing or 
"loadable" driverS inside the kernel ? This way we could try to debug it to see 
if it parse all the declared SPI devices ?

In advance thanks

Pierre-emmanuel

-----Message d'origine-----
De : Alan Ott [mailto:a...@signal11.us] 
Envoyé : jeudi 24 mai 2012 16:08
À : Pierre-Emmanuel Goudet
Cc : linux-zigbee-devel@lists.sourceforge.net; E Layec
Objet : Re: [Linux-zigbee-devel] [PATCH] BeagleBone: Patch to register SPIDEV 
on one of the SPI ports.

On 05/24/2012 03:24 AM, Pierre-Emmanuel Goudet wrote:
> Thanks for this.
> We are already trying such a modification but not for "spidev" but for 
> "cc120" that we are trying to connect to beaglebone, through 
> "mac802154/iee802154" proto drivers.

Yes, that's why I clarified in the second email. I sent the wrong patch, but 
the idea is the same, substituting cc120 for spidev. I thought your previous 
email said cc2420. If that's the case, then there's already of course a driver 
for it and you just need to attach to it (similar to what I did in the patch I 
sent). If cc120 is a new device, then you'll need to write a driver for it.

> Not yet successful but still working on. Will soon send our state on the 
> mailing list.
>
> We are a bit "new" to kernel and hardware/protocols drivers in Linux. Why the 
> way is so tricky for us. Do you know a good "tutorial" showing global schemes 
> of interfaces between Network stack / Protocols drivers / hardware drivers ?
>

The first thing you'll want to see You'll want to see 
Documentation/spi/spi-summary for information about SPI, assuming that you're 
using an SPI device like the cc2420.

Also see Documentation/networking/ieee802154.txt .

For general information about making drivers, see Linux Device Drivers, 3rd 
Edition at http://lwn.net/Kernel/LDD3/ .

Beyond that you'll need to read the code. Look at drivers which are similar to 
your device to see how they work.

Alan.




------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Linux-zigbee-devel mailing list
Linux-zigbee-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-zigbee-devel

Reply via email to