On Mon, Feb 22, 2010 at 2:32 PM, Gerrit Voigt
wrote:
> Hello,
> I am trying to understand the at86rf230.c source code, but unfortunately
[skipped]
> Apparently I am missing something.
In the function __at86rf230_read_subreg:
if (status == 0)
*data = buf[1];
--
With best wishes
Dmi
Hello,
On Mon, Feb 22, 2010 at 2:31 PM, Gerrit Voigt
wrote:
> Hi,
> how do I get access to the at86rf230 driver from user-space?
> Do I go the regular way by opening(open()) a driver-file and then use
> ioctl()? I am asking because I don't really understand how izchat for
> instance gets access.
On Mon, Feb 22, 2010 at 7:06 PM, Christian Rusch
wrote:
> Hello,
>
> we cross compiled the lowpan-tools-0.2-rc4 package with the package mangager
> of buildroot.
> We copied iz, izattach, izchat and izcoordinator in the target's /bin
> directory.
> Are there any files or libraries that I still nee
Hello,
we cross compiled the lowpan-tools-0.2-rc4 package with the package
mangager of buildroot.
We copied iz, izattach, izchat and izcoordinator in the target's /bin
directory.
Are there any files or libraries that I still need on my target's
file-system? (maybe some iplink stuff)
for testin
Hi Dmitry,
Any objections adding two members of struct ieee802154_hw_addr_filt to struct
ieee802154_dev?
One is filled by the mib, the other is updated by the driver.
In case fields differ we schedule work and call
ieee802154_ops:set_hw_addr_filt() with a changed mask.
struct ieee802154_hw_addr
On Mon, Feb 22, 2010 at 6:31 AM, Gerrit Voigt
wrote:
> Hi,
> how do I get access to the at86rf230 driver from user-space?
I haven't tried this... but I believe there is a generic module that
can be loaded that allows user space access to SPI devices. I'm sure
there is one for I2C and I think ther
Hi,
how do I get access to the at86rf230 driver from user-space?
Do I go the regular way by opening(open()) a driver-file and then use
ioctl()? I am asking because I don't really understand how izchat for
instance gets access.
For 8-bit systems it is necessary to use the
Hardware-Abstraction-Lay
Hello,
I am trying to understand the at86rf230.c source code, but unfortunately
I am stuck with understanding the purpose of some variables and pointers
that are handed over in some functions.
For example the function "at86rf230_state(struct ieee802154_dev *dev,
int state)", which is supposed to