Re: [riot-devel] at86rf2xx: packet too large -> FCS check

2017-05-17 Thread Alexander Aring
Hi, On Wed, May 17, 2017 at 07:56:05PM +0200, Baptiste Clenet wrote: > 2017-05-17 17:47 GMT+02:00 Thomas Eichinger : > > Hi Baptiste, > > > > On 17 May 2017, at 1:14 PDT(-0700), Baptiste Clenet wrote: > > > >> According to their example: > >> Example: > >> A frame transmission

Re: [riot-devel] at86rf2xx: packet too large -> FCS check

2017-05-17 Thread Baptiste Clenet
2017-05-17 17:47 GMT+02:00 Thomas Eichinger : > Hi Baptiste, > > On 17 May 2017, at 1:14 PDT(-0700), Baptiste Clenet wrote: > >> According to their example: >> Example: >> A frame transmission of length five with TX_AUTO_CRC_ON set, is >> started with a Frame Buffer write

Re: [riot-devel] at86rf2xx: packet too large -> FCS check

2017-05-17 Thread Thomas Eichinger
Hi Baptiste, On 17 May 2017, at 1:14 PDT(-0700), Baptiste Clenet wrote: According to their example: Example: A frame transmission of length five with TX_AUTO_CRC_ON set, is started with a Frame Buffer write access of five bytes (the last two bytes can be omitted). The first three bytes are

Re: [riot-devel] RIOT Package

2017-05-17 Thread Baptiste Clenet
2017-05-17 11:20 GMT+02:00 Cenk Gündoğan : > Hi Baptiste, Oleg, > > On 17-05-17 11:07:25, Oleg Hahm wrote: >> Hi! >> >> On Wed, May 17, 2017 at 10:21:45AM +0200, Baptiste Clenet wrote: >> > I see! Very interesting feature and I really think it should be >> > enabled by

Re: [riot-devel] devel Digest, Vol 51, Issue 10

2017-05-17 Thread Liu Tieping
that is used to cache > the necessary git objects. > > Cheers, > Cenk > > > > > Cheers, > > Oleg > > -- > > /* Fuck me gently with a chainsaw... */ > > linux-2.0.38/arch/sparc/kernel/ptrace.c > > ___

Re: [riot-devel] RIOT Package

2017-05-17 Thread Cenk Gündoğan
Hi Baptiste, Oleg, On 17-05-17 11:07:25, Oleg Hahm wrote: > Hi! > > On Wed, May 17, 2017 at 10:21:45AM +0200, Baptiste Clenet wrote: > > I see! Very interesting feature and I really think it should be > > enabled by default! What's your opinion? > > Not sure what you mean. The feature is

Re: [riot-devel] RIOT Package

2017-05-17 Thread Oleg Hahm
Hi! On Wed, May 17, 2017 at 10:21:45AM +0200, Baptiste Clenet wrote: > I see! Very interesting feature and I really think it should be > enabled by default! What's your opinion? Not sure what you mean. The feature is enabled by default, the only thing you need to do is to add git-cache to your

Re: [riot-devel] RIOT Package

2017-05-17 Thread Baptiste Clenet
Thank you for your answers. I see! Very interesting feature and I really think it should be enabled by default! What's your opinion? 2017-05-17 10:12 GMT+02:00 Oleg Hahm : > Hi Baptiste! > > On Wed, May 17, 2017 at 10:08:50AM +0200, Baptiste Clenet wrote: >> So you mean

Re: [riot-devel] at86rf2xx: packet too large -> FCS check

2017-05-17 Thread Baptiste Clenet
According to their example: Example: A frame transmission of length five with TX_AUTO_CRC_ON set, is started with a Frame Buffer write access of five bytes (the last two bytes can be omitted). The first three bytes are used for FCS generation; the last two bytes are replaced by the internally

Re: [riot-devel] RIOT Package

2017-05-17 Thread Oleg Hahm
Hi Baptiste! On Wed, May 17, 2017 at 10:08:50AM +0200, Baptiste Clenet wrote: > So you mean that git-cache is already used and allow to download an > archive of a .git repo? Yes, but you have to "install" git-cache first (see dist/tools/git/README.md). > Could you give me an example of a

Re: [riot-devel] RIOT Package

2017-05-17 Thread Baptiste Clenet
So you mean that git-cache is already used and allow to download an archive of a .git repo? Could you give me an example of a package that is download as an archive and store so you don't need to git clone again? 2017-05-17 9:28 GMT+02:00 Oleg Hahm : > Hi Baptiste, > > On

Re: [riot-devel] RIOT Package

2017-05-17 Thread Oleg Hahm
Hi Baptiste, On Wed, May 17, 2017 at 08:24:50AM +0200, Baptiste Clenet wrote: > Concerning external package, I suggest that RIOT download and store > the archive in pkg folder then extract here in the right location to > be compiled. This is helpful when you work on a package so you don't > need