|
Dev-Review Meeting Agenda (Sept 5)
Kumar Gala
This week we are going to use the dev-review meeting to work on the backlog of issues/enhancements/feature requests.
The idea here is to triage issues, close out one’s that we aren’t going to handle, try and see if there are some common areas we need to focus on for the 2.1 release. I’ve asked Maureen to lead the call as I will not be able to make it. Thanks - k
|
|||||||||||||
|
|
|||||||||||||
|
Re: NRF52810
Bolivar, Marti
Hi,
" via Lists.Zephyrproject.Org" <tcpipchip=hotmail.com@lists.zephyrproject.org> writes: Thank you PrestonIt looks like Carles helped you out on Slack and your question was answered. (Posting this just to track the status on this for people only watching the ML.) Marti
|
|||||||||||||
|
|
|||||||||||||
|
Re: Do not use west v0.6.1; upgrade to v0.6.2
Marc Herbert
it seems extremely serious, considering that west basically has one job (versioning).One of those jobs that everyone needs but no one wants to do? PS: versioning plus a bit more https://docs.zephyrproject.org/latest/guides/west/why.html
|
|||||||||||||
|
|
|||||||||||||
|
NRF52810
Miguel Wisintainer <tcpipchip@...>
Thank you Preston
See attached team
After i compile successfully the beacon sample, i tried to burn with J-LINK to NRF52810 and nothing is detected in my scanner!
I choose the HEX
Is there anything else that i forgot ?
It´s a SKYLAB VG01 beacon that i am replacing the code!
Thank you so much!
De: Brett Preston <bpreston@...>
Enviado: quarta-feira, 4 de setembro de 2019 17:12 Para: tcpipchip@... <tcpipchip@...> Cc: Team <info@...> Assunto: Re: New submission from Contact Us
On Wed, Sep 4, 2019 at 10:09 AM Zephyr Project - General Contact Form <webmaster@...> wrote:
--
|
|||||||||||||
|
|
|||||||||||||
|
Re: Do not use west v0.6.1; upgrade to v0.6.2
Bolivar, Marti
"Youse, Charles via Lists.Zephyrproject.Org"
<charles.youse=intel.com@lists.zephyrproject.org> writes: Hi Marti,I agree that it is a serious bug (see "high impact", below), and again, I'm sorry for the lack of test coverage that led to it happening in the first place. I'm grateful to the reporter for bringing it up. Now that the hotfix is out in the 0.6.x branch, I'm going to be adding regression testing. I do my best to make sure fixes get regression tests. Thanks, Marti
|
|||||||||||||
|
|
|||||||||||||
|
Re: Do not use west v0.6.1; upgrade to v0.6.2
Bolivar, Marti
"Youse, Charles" <charles.youse@intel.com> writes:
Marti,Of course. We have a process in place. It failed here due to lack of coverage, which unfortunate oversight and I'm very sorry for it, especially for those who ran into it. However, it was lack of coverage, and not lack of process, that was to blame. West has a test suite that works at both API and functional levels. The repository CI runs it on each commit (on Linux, via shippable). We also run it on supported platforms before cutting a release. In this case, that's Windows 10 and macOS. (This is in addition to informal testing that people are doing on the code in the master branch, which isn't relevant to this point since you are asking about process.) More testers and attention to testing are always welcome, so feel free to make any concrete suggestions for how we can improve our QA. Thanks, Marti
|
|||||||||||||
|
|
|||||||||||||
|
Re: Do not use west v0.6.1; upgrade to v0.6.2
Youse, Charles
Hi Marti,
toggle quoted messageShow quoted text
In spite of the fact that it doesn't cause data loss, it seems extremely serious, considering that west basically has one job (versioning). Thanks, Charles
-----Original Message-----
From: devel@lists.zephyrproject.org [mailto:devel@lists.zephyrproject.org] On Behalf Of Bolivar, Marti Sent: Wednesday, September 4, 2019 12:39 PM To: users@lists.zephyrproject.org; devel@lists.zephyrproject.org Subject: Re: [Zephyr-devel] Do not use west v0.6.1; upgrade to v0.6.2 Marti Bolivar <marti.bolivar@nordicsemi.no> writes: Hi,I was requested to add a link to the bug: https://github.com/zephyrproject-rtos/west/issues/298 It won't cause data loss, but it will cause west update to fail to check out the correct revision in some cases. Marti
|
|||||||||||||
|
|
|||||||||||||
|
Re: Do not use west v0.6.1; upgrade to v0.6.2
Bolivar, Marti
Marti Bolivar <marti.bolivar@nordicsemi.no> writes:
Hi,I was requested to add a link to the bug: https://github.com/zephyrproject-rtos/west/issues/298 It won't cause data loss, but it will cause west update to fail to check out the correct revision in some cases. Marti
|
|||||||||||||
|
|
|||||||||||||
|
Re: Do not use west v0.6.1; upgrade to v0.6.2
Youse, Charles
Marti,
toggle quoted messageShow quoted text
Thanks for letting us know. Perhaps, since 'west' has been made practically essential to Zephyr, we should investigate some kind of QA process for west releases. Thanks Charles
-----Original Message-----
From: devel@lists.zephyrproject.org [mailto:devel@lists.zephyrproject.org] On Behalf Of Bolivar, Marti Sent: Wednesday, September 4, 2019 9:48 AM To: users@lists.zephyrproject.org; devel@lists.zephyrproject.org Subject: [Zephyr-devel] Do not use west v0.6.1; upgrade to v0.6.2 Hi, West v0.6.1 contains a high impact bug in the "west update" behavior that is fixed in v0.6.2. Users of v0.6.0 and earlier are not affected. If you are using west v0.6.1 (check with west --version), please upgrade now using the usual process: Linux: pip3 install -U --user west macOS and Windows: pip3 install -U west Thanks, Marti
|
|||||||||||||
|
|
|||||||||||||
|
Do not use west v0.6.1; upgrade to v0.6.2
Bolivar, Marti
Hi,
West v0.6.1 contains a high impact bug in the "west update" behavior that is fixed in v0.6.2. Users of v0.6.0 and earlier are not affected. If you are using west v0.6.1 (check with west --version), please upgrade now using the usual process: Linux: pip3 install -U --user west macOS and Windows: pip3 install -U west Thanks, Marti
|
|||||||||||||
|
|
|||||||||||||
|
Error in NRF SoC flash memory compilation
#nrf52840
giriprasad@...
When Iam trying to include flash.h file in my application noticed below compilation error.
Can you help me to resolve the issue
ZEPHYR/zephyrproject/zephyr/ ZEPHYR/zephyrproject/zephyr/ const struct flash_driver_api *api = dev->driver_api; ~~~~~^~~~~~~~~~ ZEPHYR/zephyrproject/zephyr/ EPHYR/zephyrproject/zephyr/ const struct flash_driver_api *api = dev->driver_api; ~~~~~^~~~~~~~~~ ZEPHYR/zephyrproject/zephyr/ ZEPHYR/zephyrproject/zephyr/ const struct flash_driver_api *api = dev->driver_api; ~~~~~^~~~~~~~~~ ZEPHYR/zephyrproject/zephyr/ ZEPHYR/zephyrproject/zephyr/ const struct flash_driver_api *api = dev->driver_api; ~~~~~^~~~~~~~~~ ZEPHYR/zephyrproject/zephyr/ ZEPHYR/zephyrproject/zephyr/ const struct flash_driver_api *api = dev->driver_api;
|
|||||||||||||
|
|
|||||||||||||
|
Zephyr 2.0.0-rc3 tagged
Glaropoulos, Ioannis
Hi Zephyr developers,
We have now tagged Zephyr 2.0.0-rc3!
All major external dependencies and components, are now up-to-date. All high-priority bugs (including last-minute high-priority issues) have been addressed, and the corresponding PRs are merged to master. We, currently have 16 medium-priority bugs, which is below the threshold required for release.
We are now in the release testing phase. Master branch is now open only for documentation updates and patches that contribute to the release notes for 2.0. Everything else should wait until after we open the merge window, again.
The full release log can be found here: https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.0.0-rc3
More details about Zephyr releases is found here: https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management
We expect to release Zephyr 2.0 after the release testing completes successfully.
Thanks to everybody who has contributed to this release!
Ioannis Glaropoulos
Från: Glaropoulos, Ioannis
Hi Zephyr developers,
We have now tagged Zephyr 2.0.0-rc2!
All major external dependencies and components, are now up-to-date. All high-priority bugs have been addressed, and the corresponding PRs are merged to master.
We still have a (relatively short) list of bug-fix PRs that need to be reviewed and merged, in order to drop the bug count below the threshold that is required for the release.
Besides that, documentation updates and patches that contribute to the release notes for 2.0 may be merged to master.
Everything else should wait until after we open the merge window, again.
The full release log can be found here: https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.0.0-rc2
More details about Zephyr releases is found here: https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management
The final release is tentatively scheduled for August 30th.
Thanks to everybody who has contributed to this release!
Ioannis Glaropoulos
Från: Glaropoulos, Ioannis
Hi Zephyr developers,
We have just tagged Zephyr 2.0.0-rc1.
All required features scheduled for 2.0 release are now merged into master. As of now we are in the stabilization phase for 2.0 release; the merge window is closed for new features and enhancements, and will remain closed until the release date. We will also start working on filling in the existing skeleton for the release notes.
During the stabilization period bug-fix, documentation, and stabilization-related patches may be merged to master. Additional features or enhancements for 2.0 release will need to be approved by TSC.
As we need to reduce bug counts for the release, you are all encouraged to submit PRs that close existing bug reports, and to help reviewing such PRs submitted by other contributors or maintainers. Testing Zephyr release candidate branches is also highly appreciated; please, test the code base and file bug reports so they can be addressed before the release deadline.
The full release log can be found here: https://github.com/zephyrproject-rtos/zephyr/releases/tag/v2.0.0-rc1
More details about Zephyr releases is found here: https://github.com/zephyrproject-rtos/zephyr/wiki/Program-Management
The final release is tentatively scheduled for August 30th.
Thanks to everybody who contributed to this release!
Ioannis Glaropoulos
|
|||||||||||||
|
|
|||||||||||||
|
Upcoming Event: Zephyr Project: APIs - Tue, 09/03/2019 9:00am-10:00am, Please RSVP
#cal-reminder
devel@lists.zephyrproject.org Calendar <devel@...>
Reminder: Zephyr Project: APIs When: Tuesday, 3 September 2019, 9:00am to 10:00am, (GMT-07:00) America/Los Angeles Where:https://zoom.us/j/177647878 An RSVP is requested. Click here to RSVP Organizer: devel@... Description: Join from PC, Mac, Linux, iOS or Android: https://zoom.us/j/177647878 Live meeting minutes: https://docs.google.com/
|
|||||||||||||
|
|
|||||||||||||
|
API meeting: agenda
Carles Cufi
Hi all,
This week we will look at: Agenda: - Sensor API: Potential sharing between V4Z and rtio - GPIO: Update on https://github.com/zephyrproject-rtos/zephyr/pull/16648 and possibly merging it Additional items in the "Triage" column in the GitHub project may be discussed if time permits. If you want an item included in the meeting, please add it to the GitHub project. https://github.com/zephyrproject-rtos/zephyr/wiki/Zephyr-Committee-and-Working-Group-Meetings#zephyr-api-discussion https://github.com/zephyrproject-rtos/zephyr/projects/18 https://docs.google.com/document/d/1lv-8B5QE2m4FjBcvfqAXFIgQfW5oz6306zJ7GIZIWCk/edit Regards, Carles
|
|||||||||||||
|
|
|||||||||||||
|
Re: OpenThread development guide
Benjamin Lindqvist
Thanks, I really appreciate the response and especially the PR reference. Will check it out.
On Mon, Sep 2, 2019 at 12:51 PM Lubos, Robert <Robert.Lubos@...> wrote:
|
|||||||||||||
|
|
|||||||||||||
|
Re: OpenThread development guide
Lubos, Robert
Hi Benjamin,
Sorry for late reply, I’ve just came back from holiday. See my responses inline.
Regards, Robert
From: devel@... [mailto:devel@...]
On Behalf Of Benjamin Lindqvist via Lists.Zephyrproject.Org
Sent: Tuesday, August 27, 2019 13:31 To: devel@... Cc: devel@... Subject: [Zephyr-devel] OpenThread development guide
Hi,
I've verified basic OT functionality using the echo_client/server samples with the openthread overlays. That's nice, but it's not obvious to me how I proceed after this. A few things that had me confused:
- how do I configure my Zephyr device as a sleepy end device?
It is not possible to configure Sleepy End Device on current master, there is a PR that adds this functionality though (https://github.com/zephyrproject-rtos/zephyr/pull/15552). It’s been open for some time now, feel free to comment in there if it’s a desired feature for you.
- can I setup my west.yml to clone openthread + dependencies as a module to prevent cmake from doing it at build every time?
This has already been done recently, make sure to check out the current master. West will now download OpenThread for you as a Zephyr module, and use it during OT samples builds.
- can I modify the network credentials at run-time? Or in other words, does Zephyr support anything but hardcoded OT commissioning?
Zephyr supports two ways of obtaining network credentials (commissioning):
Both methods will configure your device during initial startup, and store network parameters in the flash. If, for whatever reason, you’d want to modify the network credentials afterwards, you’d need to call OpenThread API directly, there’s no support in Zephyr for that. See https://github.com/zephyrproject-rtos/openthread/blob/0dbecf508e7a79aae8ed9631f1a63fc65478b213/include/openthread/thread.h#L393 for available API functions. Just note, that in order to use OT API directly, you’d need to obtain OT context first from the OT network interface.
- can I build NCP firmware for a border router using Zephyr?
No, Zephyr cannot be configured as a NCP. For a NCP application, check the OpenThread repository.
etc. Right now I get the impression that the openthread integration is in a sort of proof-of-concept stage. Is this the case? If not, it would be nice with some more documentation, perhaps even a sample app...
Well, for sure I’d not call it a proof-of-concept at this point, yet indeed there’s still work to do. Lack of time/resources to push it forward is the only answer I can provide for now.
|
|||||||||||||
|
|
|||||||||||||
|
Bolivar, Marti
"Alberto Escolar Piedras (ALPI)" <ALPI@demant.com> writes:
Hi Marti,You're right, of course.I get a build error following along with the getting started guide:That would seem to be just a warning. I looked at the output itself without seeing the "warning" prefix. This is building and running fine (apart from the warning) using ZEPHYR_TOOLCHAIN_VARIANT=zephyr for me on my arch system. Thanks for your fast response! Andrew, can you please try again with the same toolchain configuration and let us know if you're still having problems? Thanks Marti
|
|||||||||||||
|
|
|||||||||||||
|
alpi@...
Hi Marti,
I get a build error following along with the getting started guide:That would seem to be just a warning. (At least another developer has also reported it, and I think he was also using Arch Linux) As far as a I understand it is harmless. The binary (build/zephyr/zephyr.exe) should have been produced without issues. BR Alberto -----Original Message----- From: devel@lists.zephyrproject.org <devel@lists.zephyrproject.org> On Behalf Of Bolivar, Marti via Lists.Zephyrproject.Org Sent: Saturday 31 August 2019 06:48 To: andrewtholt60@gmail.com; devel@lists.zephyrproject.org Cc: devel@lists.zephyrproject.org Subject: Re: [Zephyr-devel] Build posix sample problem (cmake error) #samples #samples #adc #samples I can't reproduce this exact issue, but I can confirm that with ZEPHYR_TOOLCHAIN_VARIANT=zephyr and ZEPHYR_TOOLCHAIN_VARIANT=host, I get a build error following along with the getting started guide: [74/74] Linking C executable zephyr/zephyr.elf /usr/bin/objdump: warning: zephyr.elf: corrupt GNU_PROPERTY_TYPE (5) size: 0 /usr/bin/objdump: warning: zephyr.elf: corrupt GNU_PROPERTY_TYPE (5) size: 0 /usr/bin/objdump: warning: zephyr.elf: corrupt GNU_PROPERTY_TYPE (5) size: 0 My host objdump is v2.32 on Arch; my zephyr SDK version is 0.10.3. Marti "Andrew Holt via Lists.Zephyrproject.Org" <andrewtholt60=gmail.com@lists.zephyrproject.org> writes: Hi,
|
|||||||||||||
|
|
|||||||||||||
|
回复: add new boards based on i.mxrt1050
nie ninesun
Dear Maureen Helm
Thank for your indication.I check the dts file. then I find the upcase of letter for the dts file name is wrong. after I correct. the compile is sucessful
发件人: Maureen Helm <maureen.helm@...>
发送时间: 2019年8月30日 23:22 收件人: xz_nie@... <xz_nie@...>; devel@... <devel@...> 主题: RE: add new boards based on i.mxrt1050 It looks like you may have forgotten to #include <nxp/nxp_rt.dtsi> in your board dts file.
From: devel@... <devel@...>
On Behalf Of nie ninesun via Lists.Zephyrproject.Org
Sent: Thursday, August 29, 2019 6:05 PM To: devel@... Cc: devel@... Subject: [Zephyr-devel] add new boards based on i.mxrt1050
Hi, I want to add new board based on boards of mimxrt1050_evk, The difference is flash for mimxrt1050_evk, The flash on my board is winbond w25q32. Then I combine the mimxrt1050_ek.dts and mimxrt1050_evk_qspi.dts.I add following code in mimxrt1050_evk.dts file: &flexspi0 { reg = <0x402a8000 0x4000>, <0x60000000 0x800000>; w25q32: w25q32@0 { compatible = "winbond,w25q32", "jedec,spi-nor"; label = "W25Q32"; reg = <0>; spi-max-frequency = <100000000>; status = "okay"; jedec-id = [ef 40 16]; }; };
then I use cmake -GNinja -DBOARD=mimxrt1050_OK1052 -DBOARD_ROOT=$rootdir .. to build the configuration. then i use ninja to build the firmware. The following error is displayed:
In file included from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/generated_dts_board.h:20, from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/arch.h:20, from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/cpu.h:17, from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/kernel_includes.h:34, from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/kernel.h:17, from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/kernel/include/kernel_structs.h:10, from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/arch/arm/core/offsets/offsets.c:26: /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/asm_inline_gcc.h: In function 'z_arch_irq_lock': zephyr/include/generated/generated_dts_board_fixups.h:11:32: error: 'DT_ARM_V7M_NVIC_E000E100_ARM_NUM_IRQ_PRIORITY_BITS' undeclared (first use in this function) #define DT_NUM_IRQ_PRIO_BITS DT_ARM_V7M_NVIC_E000E100_ARM_NUM_IRQ_PRIORITY_BITS ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ zephyr/include/generated/generated_dts_board_fixups.h:11:32: note: in definition of macro 'DT_NUM_IRQ_PRIO_BITS' #define DT_NUM_IRQ_PRIO_BITS DT_ARM_V7M_NVIC_E000E100_ARM_NUM_IRQ_PRIORITY_BITS ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/exc.h:40:31: note: in expansion of macro 'Z_EXC_PRIO' #define _EXC_IRQ_DEFAULT_PRIO Z_EXC_PRIO(_IRQ_PRIO_OFFSET) ^~~~~~~~~~ /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/asm_inline_gcc.h:91:9: note: in expansion of macro '_EXC_IRQ_DEFAULT_PRIO' : "i"(_EXC_IRQ_DEFAULT_PRIO) ^~~~~~~~~~~~~~~~~~~~~ zephyr/include/generated/generated_dts_board_fixups.h:11:32: note: each undeclared identifier is reported only once for each function it appears in #define DT_NUM_IRQ_PRIO_BITS DT_ARM_V7M_NVIC_E000E100_ARM_NUM_IRQ_PRIORITY_BITS ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ zephyr/include/generated/generated_dts_board_fixups.h:11:32: note: in definition of macro 'DT_NUM_IRQ_PRIO_BITS' #define DT_NUM_IRQ_PRIO_BITS DT_ARM_V7M_NVIC_E000E100_ARM_NUM_IRQ_PRIORITY_BITS ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/exc.h:40:31: note: in expansion of macro 'Z_EXC_PRIO' #define _EXC_IRQ_DEFAULT_PRIO Z_EXC_PRIO(_IRQ_PRIO_OFFSET) ^~~~~~~~~~ /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/asm_inline_gcc.h:91:9: note: in expansion of macro '_EXC_IRQ_DEFAULT_PRIO' : "i"(_EXC_IRQ_DEFAULT_PRIO) ^~~~~~~~~~~~~~~~~~~~~ In file included from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/cortex_m/mpu/arm_mpu_v7m.h:10, from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/cortex_m/mpu/arm_mpu.h:13, from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/arch.h:245, from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/cpu.h:17, from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/kernel_includes.h:34, from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/kernel.h:17, from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/kernel/include/kernel_structs.h:10, from /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/arch/arm/core/offsets/offsets.c:26: /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/cortex_m/cmsis.h: At top level: /home/xxxxxxxxx/Desktop/olddisk/zephyrproj/zephyr/include/arch/arm/cortex_m/cmsis.h:92:2: error: #error "DT_NUM_IRQ_PRIO_BITS and __NVIC_PRIO_BITS are not set to the same value" #error "DT_NUM_IRQ_PRIO_BITS and __NVIC_PRIO_BITS are not set to the same value" ^~~~~ ninja: build stopped: subcommand failed.
who can give me some suggestions about it? Thanks
|
|||||||||||||
|
|
|||||||||||||
|
Bolivar, Marti
I can't reproduce this exact issue, but I can confirm that with
toggle quoted messageShow quoted text
ZEPHYR_TOOLCHAIN_VARIANT=zephyr and ZEPHYR_TOOLCHAIN_VARIANT=host, I get a build error following along with the getting started guide: [74/74] Linking C executable zephyr/zephyr.elf /usr/bin/objdump: warning: zephyr.elf: corrupt GNU_PROPERTY_TYPE (5) size: 0 /usr/bin/objdump: warning: zephyr.elf: corrupt GNU_PROPERTY_TYPE (5) size: 0 /usr/bin/objdump: warning: zephyr.elf: corrupt GNU_PROPERTY_TYPE (5) size: 0 My host objdump is v2.32 on Arch; my zephyr SDK version is 0.10.3. Marti "Andrew Holt via Lists.Zephyrproject.Org" <andrewtholt60=gmail.com@lists.zephyrproject.org> writes:
Hi,
|
|||||||||||||
|
|
|||||||||||||
