Re: [riot-devel] Mailserver issues
Oleg, Thank you for handling this! Best, Thomas On 8 Aug 2017, at 7:53 PDT(-0700), Oleg Hahm wrote: > Dear RIOTers, > > due to an immense load of requests on the mailing lists, ten thousands of > mails got queued over the last days. This lead to a delay for mail delivery up > to several days. After some throttling and performance tuning on the mail > server everything should be back to normal and most of the mails should have > been delivered by now. > > Sorry for the inconvenience and please let me know if you encounter further > problems. > > Cheers, > Oleg > -- > The best thing about script jokes is that they start with a bang. > ___ > devel mailing list > devel@riot-os.org > https://lists.riot-os.org/mailman/listinfo/devel smime.p7s Description: S/MIME digital signature ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] Mailserver issues
Dear RIOTers, due to an immense load of requests on the mailing lists, ten thousands of mails got queued over the last days. This lead to a delay for mail delivery up to several days. After some throttling and performance tuning on the mail server everything should be back to normal and most of the mails should have been delivered by now. Sorry for the inconvenience and please let me know if you encounter further problems. Cheers, Oleg -- The best thing about script jokes is that they start with a bang. signature.asc Description: PGP signature ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] testmail
this is just a test - we are under the impression that no mails are delivered on the devel list currently... So if you see this mail, its a false alarm... Cheers, Hauke ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
Re: [riot-devel] Colorized compiler output not for Emacs users
Hi Kees, I was not aware of the compatibility issues for Emacs users when enabling the colored gcc output. So yes, I'd say a conditional flag preventing this on demand is indeed needed. I just opened a PR with that fix [1]. Cheers, Hauke P.S. AFAIK many in the community actually use VIM for coding. Personally I use sublime-text for most editing... [1] https://github.com/RIOT-OS/RIOT/pull/7451 On 06.08.2017 19:00, Kees Bakker wrote: Hey, Since commit 2811adc0 we get colorized gcc output. Hmm. That's unfortunate for Emacs users (I'm probably one of the very few). Emacs parses the compiler output and now it cannot match the error messages anymore. Would it be possible to add some variable to disable the coloring? (There's more than just this GCC diagnostics-color.) Something like DONOT_COLOR. This would be in the same category as QUIET, I guess. But really, I'm curious what people use to develop RIOT-OS. VIM?, Eclipse? Atom? Emacs? ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] Colorized compiler output not for Emacs users
Hey, Since commit 2811adc0 we get colorized gcc output. Hmm. That's unfortunate for Emacs users (I'm probably one of the very few). Emacs parses the compiler output and now it cannot match the error messages anymore. Would it be possible to add some variable to disable the coloring? (There's more than just this GCC diagnostics-color.) Something like DONOT_COLOR. This would be in the same category as QUIET, I guess. But really, I'm curious what people use to develop RIOT-OS. VIM?, Eclipse? Atom? Emacs? -- Kees ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
[riot-devel] Fwd: help please driver_lis3dh
-- Forwarded message -- From: Walter Literowich Date: Sat, Aug 5, 2017 at 8:15 PM Subject: help please driver_lis3dh To: us...@riot-os.org I’m trying to get the tests/driver_lis3dh running on a Nordic nrf51 using 1; a BLE400 http://www.ebay.com/itm/NRF51822-Eval-BLE400-Mother-Board- BLE4-0-Bluetooth-2-4G-Wireless-Module-Kit-/322579874665?var= &hash=item4b1b424369:m:m428eWQ4GIwIx9XKgxJ1D4w interfaced to a accelerometer cjmcu-33 http://www.ebay.com/itm/CJMCU-33-LIS33DE-Three-Axis-Accelera ted-Speed-Meter-Module-Stable-Digital-Output-/332204857695 and 2; a CJMCU-8223 Nrf51822 http://www.dx.com/p/cjmcu-8223-nrf51822-lis3dh-bluetooth- acceleration-module-purple-449109#.WYZbu4QrJQI my problem is that I cannot get any output from term - it seems to lock out without any output I’m trying to debug it with gdb , put having got the skills to really understand its output === 0x15c0 in spi_transfer_bytes (bus=bus@entry=0, cs=cs@entry=30, cont=cont@entry=true, out=out@entry=0x29f7 , in=in@entry=0x0 , len=len@entry=1) at /home/vagrant/RIOT/cpu/nrf5x_common/periph/spi.c:107 #0 0x15c0 in spi_transfer_bytes (bus=bus@entry=0, cs=cs@entry=30, cont=cont@entry=true, out=out@entry=0x29f7 , in=in@entry=0x0 , len=len@entry=1) at /home/vagrant/RIOT/cpu/nrf5x_common/periph/spi.c:107 #1 0x1680 in spi_transfer_regs (bus=0, cs=30, reg=reg@entry=207 'Ï', out=out@entry=0x0 , in=in@entry=0x2a37 , len=len@entry=1) at /home/vagrant/RIOT/drivers/periph_common/spi.c:68 #2 0x1298 in lis3dh_read_regs ( dev=dev@entry=0x2a60 , reg=reg@entry=LIS3DH_REG_WHO_AM_I, len=len@entry=1 '\001', buf=buf@entry=0x2a37 "") at /home/vagrant/RIOT/drivers/lis3dh/lis3dh.c:241 #3 0x1444 in lis3dh_init ( dev=dev@entry=0x2a60 , params=params@entry=0x2740 ) at /home/vagrant/RIOT/drivers/lis3dh/lis3dh.c:55 #4 0x0fa8 in main () at /home/vagrant/RIOT/tests/driver_lis3dh/main.c:50 Continuing. I been at this for several days without any success of understanding of the problems or issues The header files have been set up for both the boards and peripherals Thanks for your help and responses ___ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
