Hi Joakim,
as of today, I PRed a new version of the Xbee S1 radio driver[1], which
is build 100% on the new netdev interface. I think it makes a good
reference implementation for radio drivers, even if it is through it's
UART interface a little different from others drivers we are
Hi Thomas,
On Fri, Feb 20, 2015 at 10:53 AM, Thomas Eichinger
thomas.eichin...@fu-berlin.de wrote:
Hi Joakim,
On 20 Feb 2015, at 9:31 CET(+0100), Joakim Gebart wrote:
Thank you for the prompt response. I will start reading the existing
drivers but I think I will wait at least until there is
Hi Joakim,
sorry for the silence on this. The driver is almost ready I’ll open a
PR for it by Thursday at latest. I was discussing with Hauke the initialisation
process for the network stack and also initialisation in general.
I saw these memory corruptions too, but didn’t manage to identify the
PS: Sorry, you are Joakim not Joachim :-)
Am 20.02.2015 um 08:51 schrieb Peter Kietzmann:
Hi Joachim,
I think it will be the at86rf231-driver (in near future).
@thomaseichinger is currently working on the refactoring according to
the network restructuring. There is still no PR but as far as
Dear RIOT developers,
- Which radio driver is the most up to date with regards to the
network stack restructuring work being done in #2278?
- How stable is the radio device API currently? Are there any more
API changes coming?
- Would it be wise to wait until the restructuring todo list is
Hi Joachim,
I think it will be the at86rf231-driver (in near future).
@thomaseichinger is currently working on the refactoring according to
the network restructuring. There is still no PR but as far as I know the
progress is well. I think it's wise to wait at least until this driver
is
