|
Re: Build fails when the sdk is not installed in the default path in Archlinux.
Dirk Brandewie <dirk.j.brandewie@...>
On 02/22/2016 09:59 AM, Yannis Damigos wrote:
-----BEGIN PGP SIGNED MESSAGE-----Hmm looks like an SDK issue :-( I have created a bug for it https://jira.zephyrproject.org/browse/ZEP-65 I don't have any more useful advice unfortunately. --Dirk
|
|
|
|
Re: RFC: make _fiber_start() return a handle on the fiber
Mitsis, Peter <Peter.Mitsis@...>
For what it is worth, I am currently tackling this item.
toggle quoted messageShow quoted text
Peter
-----Original Message-----
|
|
|
|
Re: Build fails when the sdk is not installed in the default path in Archlinux.
Yannis Damigos
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256 On 02/22/2016 07:26 PM, Dirk Brandewie wrote: Here it is https://gist.github.com/xekarfwtos/78d9c85f018ed2a0ce4b
|
|
|
|
Re: Build fails when the sdk is not installed in the default path in Archlinux.
Dirk Brandewie <dirk.j.brandewie@...>
On 02/22/2016 08:42 AM, Yannis Damigos wrote:
On 02/22/2016 05:10 PM, Dirk Brandewie wrote:Hmmm :-/ Can you send the output of the make command adding V=1 to theYes, ZEPHYR_SDK_INSTALL_DIR is pointing to the correct SDK install directory. command line?
|
|
|
|
Re: Build fails when the sdk is not installed in the default path in Archlinux.
Yannis Damigos
On 02/22/2016 05:10 PM, Dirk Brandewie wrote:
Yes, ZEPHYR_SDK_INSTALL_DIR is pointing to the correct SDK install directory.
|
|
|
|
Re: RFC: return type of functions passed to DEVICE_INIT()
Dirk Brandewie <dirk.j.brandewie@...>
On 02/19/2016 05:20 PM, Thomas, Ramesh wrote:
I was considering the possible use case of PM app calling_sys_device_do_config_level() is *not* a public API and is *not* guaranteed be stable or even exist from release to release. AFAIK calling _sys_device_do_config_level() again would not break any of our current drivers but is the driver is is creating some state in init() (e.g. security context, network connection) all hell is likely to break loose. The driver could maintain whether init() has been called to work around this but at the cost of RAM. What is the use case? What functionality do you need? --Dirk
|
|
|
|
Re: RFC: return type of functions passed to DEVICE_INIT()
Dirk Brandewie <dirk.j.brandewie@...>
On 02/19/2016 05:31 PM, Thomas, Ramesh wrote:
On Fri, 2016-02-19 at 10:05 -0800, Daniel Leung wrote:It would take more RAM :-) Not sure exactly what you would want toOn Fri, Feb 19, 2016 at 08:31:48AM -0800, Dirk Brandewie wrote:Why not create a dedicated status field in device object? return in the status? If device init() fails there is nothing the application code can do about it other that fail gracefully. Additionally we can provide an API to query status of devices. ThisIf you are not binding to a device why do you need the status? If there is a good use case propose the API with the patch ;-)
|
|
|
|
Re: How to setup git-review
Andrew Grimberg <agrimberg@...>
On 02/19/2016 08:37 AM, Andre Guedes wrote:
Hi Anas,Forcing people to use git-review is not the intent. Using git-review eases the cognitive burden of working inside the enforced gerrit worfklow. Tell me, which would you find easier to do / remember? --[cut with git review]-- git checkout master && git pull && git checkout -b my_topic # make changes git commit -asm 'gee whiz feature' && git review --[/cut with git review]-- vs --[cut without git review]-- git checkout master && git pull && git checkout -b my_topic # make changes git commit -asm 'gee whiz feature' && git rebase master && git push origin HEAD:refs/for/master/my_topic --[/cut without git review]-- Or for pulling a remote submission for local review --[cut with git review]-- git checkout master && git pull && git review -d $submission_number --[/cut with git review]-- NOTES: * not supplying a patch number gets the latest if multiple, to specify an earlier version of a submission use $submission_number,$patch_number * submission number gets checked out locally to branch review/<user>/topic_name (or revision number if no topic) vs --[cut without git review]-- git checkout master && git pull git fetch origin refs/changes/$change_id_mod_100/$change_id/$patch_number git checkout -b local_review_of_$change_id FETCH_HEAD --[/cut without git review]-- After all the issues folks have been having because of forge author I'veIt worked for us before in many other projects, why is thisI'm not a gerrit expert but from I could understand, this is related to the relaxed the restriction some. Registered users may 'Forge Author' now, but this is honestly non-optimal. People should not be repushing changes that they did not author. The only time that's really a proper option is when a committer forces a rebase of a patch via the gerrit UI. Which brings us to git-review, when using it it will detect if you're trying to push an entire patch set and ask if you really want to do that, it should also allow you to indicate that you only want to push certain patches out of the set (though it's a feature I myself never use as I usually only work a single patch at a time of a series on a particular topic) For those that are trying to figure out what these 'forge author' or 'forge committer' rights that we keep talking about in gerrit are, it breaks down as follows: A git commit has an author and a committer. Both pieces are stored in the metadata and in the case of the author, also partly in the commit message. The committer is the one who actually pushes the submission to git. The author is the one that the commit is attributed to. Gerrit takes this one step further with the requirement of Signed-off-by lines. If the Signed-off-by line does not match the author it gets rejected. Enabling 'forge author' allows someone to submit code where the signed-off-by line does not match the authorship of the code and additionally, where the one committing the code does not match the authorship. 'forge committer' (which was only available to committers during the initial repository load in) allows anyone with the right to push code that they did not actually commit to the repo. This is useful primarily in history imports, but occasionally useful for automated processes (jenkins) that do automatic version bumping, tagging and branching. -Andy- -- Andrew J Grimberg Systems Administrator The Linux Foundation
|
|
|
|
Re: Build fails when the sdk is not installed in the default path in Archlinux.
Dirk Brandewie <dirk.j.brandewie@...>
On 02/20/2016 07:50 AM, Yannis Damigos wrote:
Dear all,Is ZEPHYR_SDK_INSTALL_DIR pointing to the SDK install directory? When the sdk is installed under the default path compiling succeeded.
|
|
|
|
Re: Source the project environment file from zsh
Yannis Damigos
|
|
|
|
Re: RFC: make _fiber_start() return a handle on the fiber
Jukka Rissanen
Hi Ben,
On Fri, 2016-02-19 at 10:36 -0500, Benjamin Walsh wrote: I am a bit busy right now so I am fine if you do it.Looks like it. You want to do the implementation yourself Jukka ?When we start a fiber via the _fiber_start() API family, we don'tNo comments -> no objects -> perhaps we can continue with this Cheers, Jukka
|
|
|
|
Re: Non-binary SDK?
Oliver Hahm <oliver.hahm@...>
Hi Anas!
Thanks for the fast response! On Sat, Feb 20, 2016 at 01:47:19PM +0000, Nashif, Anas wrote: Thanks for the explanation and looking forward for the pointer.Looking into this file I realized that it contains a big block of binary data.We do have instructions on how to build the SDK yourself, I can’t find the The Zephyr SDK is provided to help you getting started with all supportedThat's what I somehow assumed. Would be good to know, which variables have to be set to use the existing toolchains. Or maybe you good even provide something like a Makefile.toolchain.gcc, so that I can compile withe usual gcc toolchains for ARM and x86. Okay, so this is more an optional prerequisite. Most embedded developers willWhat additional tools apart from a cross-compiler toolchain are requiredThe SDK contains cross-compiler toolchains for all supported architectures have these tools already installed, I guess. Cheers, Oleg P.S. The path to the sample apps as described here https://www.zephyrproject.org/doc/getting_started/building_zephyr.html also seems to have changed. It's not "$ZEPHYR_BASE/samples/hello_world/microkernel" any more, but "$ZEPHYR_BASE/samples/microkernel/apps/hello_world".
|
|
|
|
Re: Source the project environment file from zsh
Oliver Hahm <oliver.hahm@...>
Hi!
On Sat, Feb 20, 2016 at 02:00:18PM +0000, Nashif, Anas wrote: Can you file a bug in https://jira.zephyrproject.org please? :-)I would love to, but somehow the page is not loading (neither in firefox nor in iron). Cheers, Oleg
|
|
|
|
Re: Source the project environment file from zsh
Oliver Hahm <oliver.hahm@...>
Hi!
On Sun, Feb 21, 2016 at 05:37:26PM -0000, Yannis Damigos wrote: Hi all,Thanks, that seems to work for zsh and bash. Cheers, Oleg
|
|
|
|
Re: Source the project environment file from zsh
Yannis Damigos
Hi all,
The above did not work for me. The following worked diff --git a/zephyr-env.sh b/zephyr-env.sh index dcb0638..21eca53 100644 --- a/zephyr-env.sh +++ b/zephyr-env.sh @@ -1,5 +1,5 @@ -if [ "X$(basename -- "$0")" == "Xzephyr-env.sh" ]; then +if [ "X$(basename -z -- "$0")" = "Xzephyr-env.sh" ]; then echo "Source this file (do NOT execute it!) to set the Zephyr Kernel environment." exit fi Yannis
|
|
|
|
Build fails when the sdk is not installed in the default path in Archlinux.
Yannis Damigos
Dear all,
Building the philosophers sample fails when the sdk is not installed under the default path (/opt/zephyr-sdk) in Archlinux with the following error: make[1]: Entering directory '/home/xekarfwtos/projects/zephyr' make[2]: Entering directory '/home/xekarfwtos/projects/philosophers/outdir' Using /home/xekarfwtos/projects/zephyr as source for kernel GEN ./Makefile CHK include/generated/version.h HOSTCC scripts/basic/fixdep HOSTCC scripts/gen_idt/version.o HOSTCC scripts/gen_idt/gen_idt.o HOSTLD scripts/gen_idt/gen_idt HOSTCC scripts/gen_offset_header/gen_offset_header.o HOSTLD scripts/gen_offset_header/gen_offset_header CHK misc/generated/configs.c UPD misc/generated/configs.c i586-poky-elf-gcc: error trying to exec 'cc1': execvp: No such file or directory /home/xekarfwtos/projects/zephyr/./Kbuild:98: recipe for target 'arch/x86/core/offsets/offsets.o' failed make[3]: *** [arch/x86/core/offsets/offsets.o] Error 1 /home/xekarfwtos/projects/zephyr/Makefile:892: recipe for target 'prepare' failed make[2]: *** [prepare] Error 2 make[2]: Leaving directory '/home/xekarfwtos/projects/philosophers/outdir' Makefile:169: recipe for target 'sub-make' failed make[1]: *** [sub-make] Error 2 make[1]: Leaving directory '/home/xekarfwtos/projects/zephyr' /home/xekarfwtos/projects/zephyr/Makefile.inc:61: recipe for target 'all' failed make: *** [all] Error 2 When the sdk is installed under the default path compiling succeeded. Best regards, Yannis
|
|
|
|
Re: Source the project environment file from zsh
Nashif, Anas
Hi Oleg,
On 20/02/2016, 08:24, "Oleg Hahm" <oliver.hahm(a)inria.fr> wrote: Dear Zephyr development team,I think this can be fixed with: diff --git a/zephyr-env.sh b/zephyr-env.sh index dcb0638..d17780a 100644 --- a/zephyr-env.sh +++ b/zephyr-env.sh @@ -1,5 +1,5 @@ -if [ "X$(basename -- "$0")" == "Xzephyr-env.sh" ]; then +if [ "X$(basename -- "$0")" = "Xzephyr-env.sh" ]; then echo "Source this file (do NOT execute it!) to set the Zephyr Kernel environment." exit fi Can you file a bug in https://jira.zephyrproject.org please? :-) Anas
|
|
|
|
Re: Non-binary SDK?
Nashif, Anas
Oleg,
On 20/02/2016, 08:35, "Oleg Hahm" <oliver.hahm(a)inria.fr> wrote: Dear Zephy development team,you can also install without sudo in your home directory or any other location. The script will only extract the contents of the file. We do have instructions on how to build the SDK yourself, I can’t find the pointer right now, but will add this to the documentation for easy access. The SDK itself is built using Yocto. The Zephyr SDK is provided to help you getting started with all supported platforms, however, you should be able to use other cross-compilers installed on your system if you wish. The SDK contains cross-compiler toolchains for all supported architectures and host tools. Additionally it contains hosts tools like python, gcc, make, openocd. Anas
|
|
|
|
Non-binary SDK?
Oliver Hahm <oliver.hahm@...>
Dear Zephy development team,
your Getting Started Guide [1] tells at some point to download a SDK, make it executable, run it: Run the installation binary, type: $ chmod +x zephyr-sdk-0.7.2-i686-setup.run $ sudo ./zephyr-sdk-0.7.2-i686-setup.run Looking into this file I realized that it contains a big block of binary data. I'm feeling somehow uncomfortable with just executing a binary from an unknown source (particular with sudo). Is there another way to install this SDK with non binary data (I'm willing if build it myself) or to tell me what this SDK apart from cross-compiler-toolchains contains? What additional tools apart from a cross-compiler toolchain are required anyway (and why) for your OS? Thanks, Oleg [1] https://www.zephyrproject.org/doc/getting_started/installation_linux.html#installing-requirements-and-dependencies
|
|
|
|
Source the project environment file from zsh
Oliver Hahm <oliver.hahm@...>
Dear Zephyr development team,
following the instructions in your Getting Started Guide [1], I tried to run source zephyr-env.sh in my zsh 5.2, but get: zephyr-env.sh:2: = not found With my limited knowledge about shell the syntax of this script seems indeed not to be POSIX shell compatible, but rather resemble bash syntax. Cheers, Oleg P.S. Manually copying&pasting the last lines of the script seems to work though. [1] https://www.zephyrproject.org/doc/getting_started/installation_linux.html#environment-variables
|
|
|