On 25/02/2020 09:02, Sebastian Huber wrote:
Hello,
in order to close this bug:
https://devel.rtems.org/ticket/3569
I would like to update waf to the latest version 2.0.19 in:
rtems-docs
rtems-tools
rtems-libbsd
rtems-examples
I updated these repositories to waf version 2.0.19 and also the
Also, Should look into ticket #3642 related to adding function prototypes
to wchar.h
On Thu, Feb 27, 2020 at 5:11 PM Eshan Dhawan
wrote:
>
>
> On Wed, Feb 26, 2020 at 8:50 PM Joel Sherrill wrote:
>
>>
>>
>> On Wed, Feb 26, 2020 at 9:06 AM Eshan Dhawan
>> wrote:
>>
>>> so the subtasks would
On Wed, Feb 26, 2020 at 8:50 PM Joel Sherrill wrote:
>
>
> On Wed, Feb 26, 2020 at 9:06 AM Eshan Dhawan
> wrote:
>
>> so the subtasks would consist of adding missing functions to stat.h ,
>> types.h mainly I suppose
>>
>
> What do you think is missing in those? My reading of the POSIX standard
Four spaces per indent level is used in most files.
Update #3853.
---
c-user/glossary.rst | 1284 +--
1 file changed, 642 insertions(+), 642 deletions(-)
diff --git a/c-user/glossary.rst b/c-user/glossary.rst
index a230d6c..67dce76 100644
---
Use the file history to derive the copyright information.
Update #3853.
---
c-user/glossary.rst | 3 +++
1 file changed, 3 insertions(+)
diff --git a/c-user/glossary.rst b/c-user/glossary.rst
index 9b9c3c0..c9a1dfb 100644
--- a/c-user/glossary.rst
+++ b/c-user/glossary.rst
@@ -1,5 +1,8 @@
..
This patch set reworks the glossary of terms so that it can be automatically
generated from specification items.
Sebastian Huber (5):
c-user: Use four spaces per indent level
c-user: Clarify return code related terms
c-user: Sort glossary terms
c-user: Merge parition term definitions
Remove duplicate "return code" definition. Add all related terms and
use references.
Update #3853.
---
c-user/glossary.rst | 18 --
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/c-user/glossary.rst b/c-user/glossary.rst
index 67dce76..9a88b5e 100644
---
Update #3853.
---
c-user/glossary.rst | 10 ++
1 file changed, 6 insertions(+), 4 deletions(-)
diff --git a/c-user/glossary.rst b/c-user/glossary.rst
index 3f53634..9b9c3c0 100644
--- a/c-user/glossary.rst
+++ b/c-user/glossary.rst
@@ -419,11 +419,13 @@ Glossary
multiprocessor
Update #3853.
---
c-user/glossary.rst | 66 ++---
1 file changed, 33 insertions(+), 33 deletions(-)
diff --git a/c-user/glossary.rst b/c-user/glossary.rst
index 9a88b5e..3f53634 100644
--- a/c-user/glossary.rst
+++ b/c-user/glossary.rst
@@ -57,25
---
bsps/shared/dev/display/disp_hcms29xx.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/bsps/shared/dev/display/disp_hcms29xx.c
b/bsps/shared/dev/display/disp_hcms29xx.c
index 5730b36ea9..9d3e7220cf 100644
--- a/bsps/shared/dev/display/disp_hcms29xx.c
+++
Hi Lou,
Did you ever solve this problem?
I just tried linking an out of tree program for the beaglebone black
BSP and have the same undefined symbols. The testsuite links correctly
and the symbols are in the testsuite binaries, but not in libbsd.a
doing a grep of the rtems-libbsd source there is
On 28/02/2020 06:23, Chris Johns wrote:
Hi,
Please find attached an error log for libbsd for the BBB.
This should be already fixed:
https://git.rtems.org/rtems-libbsd/commit/?id=7606ec29778f1fabf70f3fc10edca02155d02c8c
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4,
Hi,
Please find attached an error log for libbsd for the BBB.
Chris
RTEMS Tools Project - Source Builder Error Report
Build: error: building
rtems-libbsd-ve562e3bdf33f5de01ede936d5621ab7de88f74d3-x86_64-freebsd11.2-1
Command Line: ../source-builder/sb-set-builder --prefix=/opt/work/rtems/5
On 28/02/2020 04:40, Alan Cudmore wrote:
Hi Lou,
Did you ever solve this problem?
I just tried linking an out of tree program for the beaglebone black
BSP and have the same undefined symbols. The testsuite links correctly
and the symbols are in the testsuite binaries, but not in libbsd.a
For
Thank you for the reply, I am going through the tickets and will be fixing
the bugs for the same. I will be submitting the draft proposal as soon as
possible. Meanwhile, I will study previous student's work to get a heads-up.
Regards
Anmol Mishra
On Wed, Feb 26, 2020 at 5:34 PM Joel Sherrill
On 26/02/2020 05:51, Chris Johns wrote:
On 26/2/20 3:46 pm, Gedare Bloom wrote:
On Tue, Feb 25, 2020 at 9:18 PM Chris Johns wrote:
On 26/2/20 3:06 pm, Gedare Bloom wrote:
On Tue, Feb 25, 2020 at 6:57 PM Chris Johns wrote:
On 24/2/20 6:52 pm, Sebastian Huber wrote:
Hello,
I updated
From: Geert Uytterhoeven
The actual error is FDT_ERR_NOTFOUND, not FDT_ERR_NOT_FOUND.
Fixes: d29126c90acb0d70 ("libfdt: Add iterator over properties")
Fixes: 902d0f0953d0074b ("libfdt: Add a subnodes iterator macro")
Signed-off-by: Geert Uytterhoeven
Signed-off-by: David Gibson
---
From: Simon Glass
There does not seem to be a strong reason to inline this function. Also
we are about to add some extra code to it which will increase its size.
Move it into fdt.c and use a simple declaration in libfdt.h
Signed-off-by: Simon Glass
Message-Id:
From: Luc Michel
Including libfdt.h in a C++ project fails during compilation with recent
version of GCC or Clang.
This simple example:
extern "C" {
#include
}
int main(void) { return 0; }
leads to the following errors with GCC 9.1.0:
/usr/include/libfdt.h: In function ‘void
From: David Gibson
In libfdt we often sanity test fdt_totalsize(fdt) fairly early, then
trust it (but *only* that header field) for the remainder of our work.
However, Coverity gets confused by this - it sees the byteswap in
fdt32_ld() and assumes that means it is coming from an untrusted source
From: David Gibson
This function returns an int32_t, however the prototype in
libfdt_internal.h shows it returning an int. We haven't caught this before
because they're the same type on nearly all platforms this gets built on.
Apparently it's not the case on FreeRTOS, so someone hit this
From: David Gibson
6dcb8ba4 "libfdt: Add helpers for accessing unaligned words" introduced
the fdt32_ld() and fdt64_ld() helpers for loading values from the FDT blob
which might not be naturally aligned. This matters for ARM, where
attempting a plain unaligned load will often cause an
From: Rob Herring
Replace instances of dual GPLv2 or BSD license boilerplate with SPDX tags.
Signed-off-by: Rob Herring
Message-Id: <20190620211944.9378-3-r...@kernel.org>
Signed-off-by: David Gibson
---
cpukit/dtc/libfdt/fdt.c | 47 +
From: Nicholas Piggin
If fdt_add_property or fdt_property_placeholder fail after allocating
a string for the name, they return without freeing that string. This
does not change the structure of the tree, but in very specific cases
it could lead to undesirable space consumption.
Fix this by
From: Simon Glass
Allow enabling ASSUME_VALID_INPUT to disable sanity checks on the device
tree and the parameters to libfdt. This assumption covers that cases where
the problem could be with either.
Signed-off-by: Simon Glass
Message-Id: <20200220214557.176528-5-...@chromium.org>
From: Thierry Reding
The new fdt_generate_phandle() function can be used to generate a new,
unused phandle given a specific device tree blob. The implementation is
somewhat naive in that it simply walks the entire device tree to find
the highest phandle value and then returns a phandle value one
From: Geert Uytterhoeven
The second parameter of fdt_getprop_by_offset() is called "offset", not
"ffset".
Signed-off-by: Geert Uytterhoeven
Signed-off-by: David Gibson
---
cpukit/include/libfdt.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/cpukit/include/libfdt.h
From: Simon Glass
Allow enabling FDT_ASSUME_NO_ROLLBACK to disable rolling back after a
failed operation.
Signed-off-by: Simon Glass
Reviewed-by: David Gibson
Message-Id: <20200220214557.176528-6-...@chromium.org>
Signed-off-by: David Gibson
---
cpukit/dtc/libfdt/fdt_rw.c | 18
AKASHI Takahiro (1):
libfdt: add fdt_append_addrrange()
David Gibson (6):
libfdt: Don't use memcpy to handle unaligned reads on ARM
Revert "libfdt: Add phandle generation helper"
libfdt: Make fdt_get_max_phandle() an inline
libfdt: Tweak data handling to satisfy Coverity
libfdt: Allow
From: Thierry Reding
The fdt_get_max_phandle() function has some shortcomings. On one hand
it returns just a uint32_t which means to check for the "negative"
error code a caller has to explicitly check against the error code
(uint32_t)-1. In addition, the -1 is the only error code that can be
From: Nicholas Piggin
Searching for duplicate names scales O(n^2) with the number of names
added to a fdt, which can cause a noticable slowdown with larger device
trees and very slow CPU cores.
Add FDT_CREATE_FLAG_NO_NAME_DEDUP that allow the caller to trade fdt size
for speed in the creation
From: Simon Glass
Support ASSUME_VALID_DTB to disable some sanity checks
If we assume that the DTB itself is valid then we can skip some checks and
save code space. Add various conditions to handle this.
Signed-off-by: Simon Glass
Message-Id: <20200220214557.176528-4-...@chromium.org>
From: Simon Glass
This function is used to perform a full check of the device tree. Allow
it to be excluded if all assumptions are enabled.
Signed-off-by: Simon Glass
Reviewed-by: David Gibson
Message-Id: <20200220214557.176528-9-...@chromium.org>
Signed-off-by: David Gibson
---
From: Simon Glass
Add a new ASSUME_MASK option, which allows for some control over the
checks used in libfdt. With all assumptions enabled, libfdt assumes that
the input data and parameters are all correct and that internal errors
cannot happen.
By default no assumptions are made and all checks
From: Thierry Reding
The new fdt_generate_phandle() function can be used to generate a new,
unused phandle given a specific device tree blob. The implementation is
somewhat naive in that it simply walks the entire device tree to find
the highest phandle value and then returns a phandle value one
From: AKASHI Takahiro
This function will append an address range property using parent node's
"#address-cells" and "#size-cells" properties.
It will be used in implementing kdump with kexec_file_load system call
at linux kernel for arm64 once it is merged into kernel tree.
Signed-off-by:
From: Simon Glass
Add a way to remove this check and the reordering code, which is
unnecessary if the dtb is known to be correctly ordered.
Signed-off-by: Simon Glass
Reviewed-by: David Gibson
Message-Id: <20200220214557.176528-8-...@chromium.org>
Signed-off-by: David Gibson
---
From: David Gibson
c12b2b0c20eb "libfdt: fdt_address_cells() and fdt_size_cells()" introduced
a bug as it consolidated code between the helpers for getting
#address-cells and #size-cells. Specifically #size-cells is allowed to
be 0, and is frequently found so in practice for /cpus. IEEE1275
From: David Gibson
It's now a trivial wrapper around fdt_find_max_phandle() so we might as
well inline it. We also remove it from the versioning linker script.
Theoretically, that's a breaking ABI change except that we haven't yet
released a version with it exposed in the shared object, so we
From: John Clarke
According to the device tree specification, the default value for
#size-cells is 1, but fdt_size_cells() was returning 2 if this property
was not present.
This patch also makes fdt_address_cells() and fdt_size_cells() conform
to the behaviour documented in libfdt.h. The
From: David Gibson
This reverts commit 54ea41c22415cb0e283d22faf71202051c89400c.
Signed-off-by: David Gibson
---
cpukit/dtc/libfdt/fdt_ro.c | 31 ---
cpukit/include/libfdt.h | 19 ---
cpukit/include/libfdt_env.h | 1 -
3 files changed, 51
From: Chris Johns
Updates #3888
---
rtems_waf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/rtems_waf b/rtems_waf
index 1b896361..096372fc 16
--- a/rtems_waf
+++ b/rtems_waf
@@ -1 +1 @@
-Subproject commit 1b896361d302aeda0145af90972aea863e28898f
+Subproject commit
From: Chris Johns
Closes #3888
---
rtems_waf | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/rtems_waf b/rtems_waf
index 1b896361..096372fc 16
--- a/rtems_waf
+++ b/rtems_waf
@@ -1 +1 @@
-Subproject commit 1b896361d302aeda0145af90972aea863e28898f
+Subproject commit
Are maybe
rtems_scheduler_map_priority_to_posix()
rtems_scheduler_map_priority_from_posix()
better than the
rtems_scheduler_map_to_posix_priority()
rtems_scheduler_map_from_posix_priority()
of the patch?
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim,
From: Simon Glass
Allow enabling FDT_ASSUME_LATEST to disable version checks.
Signed-off-by: Simon Glass
Reviewed-by: David Gibson
Message-Id: <20200220214557.176528-7-...@chromium.org>
Signed-off-by: David Gibson
---
cpukit/dtc/libfdt/fdt.c| 34 +-
On Thu, Feb 27, 2020 at 5:49 AM Eshan Dhawan
wrote:
> Also, Should look into ticket #3642 related to adding function prototypes
> to wchar.h
>
Make sure what's left to do is always the first step. :)
And make sure you are making progress on a proposal.
>
> On Thu, Feb 27, 2020 at 5:11 PM
Update #3853.
---
c-user/glossary.rst | 51 +++-
eng/glossary.rst| 61 +
eng/index.rst | 1 +
3 files changed, 112 insertions(+), 1 deletion(-)
create mode 100644 eng/glossary.rst
diff --git
This patch demonstrates the automatic generation of the general glossary and the
new glossary for the RTEMS Software Engineering manual. In a private repository
I have specification items for groups of glossary terms (e.g. the general
glossary) and glossary terms. I also have a prototype for a
On Wed, Feb 26, 2020 at 11:56 PM Sebastian Huber
wrote:
>
> On 27/02/2020 07:38, Chris Johns wrote:
> > On 27/2/20 5:25 pm, Sebastian Huber wrote:
> >> On 26/02/2020 23:15, Chris Johns wrote:
> >>> On 27/2/20 12:26 am, Sebastian Huber wrote:
> On 26/02/2020
On 2020-02-27 08:45 +0100, Christian Mauderer wrote:
>
> It's just another problem that I noted sometimes on the mailing list
> with RTEMS and libbsd: Sometimes libbsd doesn't compile with some odd
> error messages like unresolved symbols. Most of the time the problem is
> that libbsd has been
Hi Suyash,
I have a few comments for you.
First, the commit message should follow the guidance at
https://docs.rtems.org/branches/master/eng/vc-users.html#creating-a-patch
and follow through the link about Commit Messages. We like to have a
short "tag" at the start of the commit to indicate the
Okay sorry I missed out on the coding standards docs.
yes code blocks edited without telling I will change its settings
On Thu, Feb 27, 2020 at 9:18 PM Gedare Bloom wrote:
> Hi Suyash,
>
> I have a few comments for you.
>
> First, the commit message should follow the guidance at
>
On Thu, Feb 27, 2020 at 9:48 AM Gedare Bloom wrote:
> Hi Suyash,
>
> I have a few comments for you.
>
> First, the commit message should follow the guidance at
> https://docs.rtems.org/branches/master/eng/vc-users.html#creating-a-patch
> and follow through the link about Commit Messages. We
Hi
The Microblaze uses the rtems-default.bset and is the only target that
isn't compiling.
It ends with this error which seems like something is off in a way that
should impact
all targets but doesn't. Any ideas?
FWIW I am proceeding with the update. Since we don't actually have a
Microblaze
I noticed that the Zephyr RTOS (https://www.zephyrproject.org) uses a
device tree based initialization for all of its BSPs.
For example, here is the top level device tree source for the Adafruit
Trinket M0, which is a very small Atmel Cortex M0 based board:
This picks up fixes for at least the RTEMS reported issues for missing
extern C in devctl.h and the symlink issue with bsdtar.
---
rtems/config/5/rtems-default.bset | 2 +-
rtems/config/5/rtems-epiphany.bset | 2 +-
rtems/config/5/rtems-or1k.bset
On 28/2/20 9:14 am, Gedare Bloom wrote:
> On Thu, Feb 27, 2020 at 3:01 PM Chris Johns wrote:
>>
>> On 28/2/20 7:23 am, Alan Cudmore wrote:
>>> I noticed that the Zephyr RTOS (https://www.zephyrproject.org) uses a
>>> device tree based initialization for all of its BSPs.
>>> For example, here is
On 28/2/20 2:35 am, Gedare Bloom wrote:
> On Wed, Feb 26, 2020 at 11:56 PM Sebastian Huber
> wrote:
>> On 27/02/2020 07:38, Chris Johns wrote:
>>> On 27/2/20 5:25 pm, Sebastian Huber wrote:
On 26/02/2020 23:15, Chris Johns wrote:
> On 27/2/20 12:26 am, Sebastian Huber wrote:
>> On
On 2020-02-28 09:01 +1100, Chris Johns wrote:
> The issue of RTEMS version mismatch of blobs is a real issue waiting to hit
> our
> users and simply linking the blobs into the executable would solve this.
> This also looks like a blocker for CI testing.
I agree with everything you said but
On 27/02/2020 18:14, Amar Takhar wrote:
> On 2020-02-27 08:45 +0100, Christian Mauderer wrote:
>>
>> It's just another problem that I noted sometimes on the mailing list
>> with RTEMS and libbsd: Sometimes libbsd doesn't compile with some odd
>> error messages like unresolved symbols. Most of the
On 2020-02-27 20:06 +0100, Christian Mauderer wrote:
> > The only good way to handle this is to have it all in 1 giant repository we
> > work
> > with. Every other solution is a pain no matter how well thought out it is.
> > I
> > personally lean more on the service side of things that it
On Thu, Feb 27, 2020 at 9:30 AM Joel Sherrill wrote:
>
>
>
> On Thu, Feb 27, 2020 at 9:48 AM Gedare Bloom wrote:
>>
>> Hi Suyash,
>>
>> I have a few comments for you.
>>
>> First, the commit message should follow the guidance at
>>
On Thu, Feb 27, 2020 at 3:01 PM Chris Johns wrote:
>
> On 28/2/20 7:23 am, Alan Cudmore wrote:
> > I noticed that the Zephyr RTOS (https://www.zephyrproject.org) uses a
> > device tree based initialization for all of its BSPs.
> > For example, here is the top level device tree source for the
Jeff.. try the stuff below and let us know.
On Tue, Feb 25, 2020 at 9:12 PM Chris Johns wrote:
> On 25/2/20 5:09 am, Joel Sherrill wrote:
> > Hi
> >
> > CentOS 8 does not have a package for pax. It does have a package for
> bsdtar.
> >
> > Is bsdtar sufficient for the tests? I don't call the
On 28/2/20 7:23 am, Alan Cudmore wrote:
> I noticed that the Zephyr RTOS (https://www.zephyrproject.org) uses a
> device tree based initialization for all of its BSPs.
> For example, here is the top level device tree source for the Adafruit
> Trinket M0, which is a very small Atmel Cortex M0 based
Hi
Please post the flyer in the link and encourage students. :)
Google has decided to sponsor the Summer of Code again. This year they
have accepted about 200 open source organizations including RTEMS.
As thrilled as I am to have students work with RTEMS, there are a LOT of
other free software
On 28/2/20 1:04 am, Sebastian Huber wrote:
> A contribution of the scripts and the specification items to the RTEMS Project
> is currently blocked due to several undecided things related to the RTEMS
> Qualification Project:
>
> https://lists.rtems.org/pipermail/devel/2020-February/057246.html
>
67 matches
Mail list logo
