|
Re: Source the project environment file from zsh
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 [
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 [
|
By
Yannis Damigos
·
#2291
·
|
|
Build fails when the sdk is not installed in the default path in Archlinux.
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
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
|
By
Yannis Damigos
·
#2290
·
|
|
Re: Source the project environment file from zsh
Hi Oleg,
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 --
Hi Oleg,
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 --
|
By
Nashif, Anas
·
#2289
·
|
|
Re: Non-binary SDK?
Oleg,
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
Oleg,
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
|
By
Nashif, Anas
·
#2288
·
|
|
Non-binary SDK?
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
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
|
By
Oliver Hahm <oliver.hahm@...>
·
#2286
·
|
|
Source the project environment file from zsh
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
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
|
By
Oliver Hahm <oliver.hahm@...>
·
#2287
·
|
|
Re: RFC: return type of functions passed to DEVICE_INIT()
Why not create a dedicated status field in device object?
Additionally we can provide an API to query status of devices. This
will help query status of devices it does not bind to.
Why not create a dedicated status field in device object?
Additionally we can provide an API to query status of devices. This
will help query status of devices it does not bind to.
|
By
Thomas, Ramesh
·
#2285
·
|
|
Re: RFC: return type of functions passed to DEVICE_INIT()
That should be fine. So the kernel decision to abort will be based on a
"fatal" error return from any of the device's init function.
We still need to decide what does "abort" mean for kernel. It
That should be fine. So the kernel decision to abort will be based on a
"fatal" error return from any of the device's init function.
We still need to decide what does "abort" mean for kernel. It
|
By
Thomas, Ramesh
·
#2284
·
|
|
Re: galileo building problem
Hi,
You need to go into an application directory and build in the application directory, for example:
$ cd samples/hello_world/nanokernel
$ make BOARD=galileo
Regards,
Anas
Hi,
You need to go into an application directory and build in the application directory, for example:
$ cd samples/hello_world/nanokernel
$ make BOARD=galileo
Regards,
Anas
|
By
Nashif, Anas
·
#2283
·
|
|
galileo building problem
Hi,
I had set up all the dev libaries, SDK and downloaded required files ( https://www.zephyrproject.org/doc/board/galileo.html ). but under $ZEPHYR_BASE directory when I did make BOARD=galileo it
Hi,
I had set up all the dev libaries, SDK and downloaded required files ( https://www.zephyrproject.org/doc/board/galileo.html ). but under $ZEPHYR_BASE directory when I did make BOARD=galileo it
|
By
Anupam Datta
·
#2282
·
|
|
issue setup galileo board
Hi,
I had set up all the dev libaries, SDK and downloaded required files (
https://www.zephyrproject.org/doc/board/galileo.html ). but under
$ZEPHYR_BASE directory when I did make BOARD=galileo it
Hi,
I had set up all the dev libaries, SDK and downloaded required files (
https://www.zephyrproject.org/doc/board/galileo.html ). but under
$ZEPHYR_BASE directory when I did make BOARD=galileo it
|
By
Anupam Datta
·
#2280
·
|
|
issue setup galileo board
Hi,
I had set up all the dev libaries, SDK and downloaded required files (
https://www.zephyrproject.org/doc/board/galileo.html ). but under
$ZEPHYR_BASE directory when I did make BOARD=galileo it
Hi,
I had set up all the dev libaries, SDK and downloaded required files (
https://www.zephyrproject.org/doc/board/galileo.html ). but under
$ZEPHYR_BASE directory when I did make BOARD=galileo it
|
By
Anupam Datta
·
#2281
·
|
|
Re: RFC: return type of functions passed to DEVICE_INIT()
This should work. We need to rework some of the drivers as they make
the driver_api assignment unconditionally.
----------
Daniel Leung
This should work. We need to rework some of the drivers as they make
the driver_api assignment unconditionally.
----------
Daniel Leung
|
By
Daniel Leung <daniel.leung@...>
·
#2279
·
|
|
Re: RFC: make _fiber_start() return a handle on the fiber
Sure.
By
Benjamin Walsh <benjamin.walsh@...>
·
#2278
·
|
|
Re: RFC: make _fiber_start() return a handle on the fiber
You are right, this will not break existing code.
Nevertheless, we should track such API changes and document them in release notes.
Anas
>
You are right, this will not break existing code.
Nevertheless, we should track such API changes and document them in release notes.
Anas
>
|
By
Nashif, Anas
·
#2277
·
|
|
Re: RFC: make _fiber_start() return a handle on the fiber
We're just returning a thread ID when we start a fiber now, you can
ignore it. I don't see an issue here...
We're just returning a thread ID when we start a fiber now, you can
ignore it. I don't see an issue here...
|
By
Benjamin Walsh <benjamin.walsh@...>
·
#2276
·
|
|
Re: RFC: make _fiber_start() return a handle on the fiber
Ugh, you're right, it's a nano_thread_id_t.
Ugh, you're right, it's a nano_thread_id_t.
|
By
Benjamin Walsh <benjamin.walsh@...>
·
#2275
·
|
|
Re: How to setup git-review
Hi Anas,
Quoting Nashif, Anas (2016-02-19 14:07:36)
Yes, I agree.
I'm not a gerrit expert but from I could understand, this is related to the
'forge author' settings from submitter rights. I'm CCing
Hi Anas,
Quoting Nashif, Anas (2016-02-19 14:07:36)
Yes, I agree.
I'm not a gerrit expert but from I could understand, this is related to the
'forge author' settings from submitter rights. I'm CCing
|
By
Andre Guedes <andre.guedes@...>
·
#2274
·
|
|
Re: RFC: return type of functions passed to DEVICE_INIT()
How about something like this:
diff --git a/kernel/nanokernel/device.c b/kernel/nanokernel/device.c
index f86f95f..82774c4 100644
--- a/kernel/nanokernel/device.c
+++ b/kernel/nanokernel/device.c
@@
How about something like this:
diff --git a/kernel/nanokernel/device.c b/kernel/nanokernel/device.c
index f86f95f..82774c4 100644
--- a/kernel/nanokernel/device.c
+++ b/kernel/nanokernel/device.c
@@
|
By
Dirk Brandewie <dirk.j.brandewie@...>
·
#2273
·
|
|
Re: RFC: make _fiber_start() return a handle on the fiber
Makes sense but why not tell the compiler the truth about the type?
Makes sense but why not tell the compiler the truth about the type?
|
By
Dirk Brandewie <dirk.j.brandewie@...>
·
#2272
·
|