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
source neither as I focused on the driver refactoring.

Looking forward for your review and testing.

Best, Thomas

> On 17 Mar 2015, at 12:42, Joakim Gebart <joakim.geb...@eistec.se> wrote:
> 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 a PR for the rf231
>>> before I begin my implementation work.
>> As Peter mentioned I'm working hard on refactoring the rf2xx driver. As we
>> want to use it on EmbeddedWorld on Tuesday you can expect a PR for this
>> soonish. :-)
> How is the new rf2xx driver coming along?
> I have been seeing some memory corruption problems on my platform and
> I think it originates somewhere in the radio stack, but I have not
> managed to pinpoint it further. I would like to test the new driver
> before I spend more time chasing down a bug that might have already
> been fixed in the refactoring process.
> Is there any WIP branch we can look at?
> Do you have any ETA for a PR?
> Best regards,
> Joakim
> _______________________________________________
> devel mailing list
> devel@riot-os.org
> http://lists.riot-os.org/mailman/listinfo/devel

devel mailing list

Reply via email to