Re: RTEMS_BSP_FAMILIY?

2018-01-03 Thread Chris Johns

> On 3 Jan 2018, at 2:44 am, Joel Sherrill  wrote:
> 
> 
> 
> On Jan 2, 2018 8:58 AM, "Sebastian Huber" 
>  wrote:
> Hello,
> 
> some BSPs use this:
> 
> c/src/lib/libbsp/m68k/mcf5225x/make/custom/mcf5225x.cfg:RTEMS_BSP_FAMILY=mcf5225x
> c/src/lib/libbsp/powerpc/mvme5500/make/custom/mvme5500.cfg:RTEMS_BSP_FAMILY=mvme5500
> c/src/lib/libbsp/powerpc/beatnik/make/custom/beatnik.cfg:RTEMS_BSP_FAMILY=beatnik
> c/src/lib/libbsp/sparc64/usiii/make/custom/usiii.cfg:RTEMS_BSP_FAMILY=usiii
> c/src/lib/libbsp/sparc64/niagara/make/custom/niagara.cfg:RTEMS_BSP_FAMILY=niagara
> 
> There is a one-to-one relationship between this RTEMS_BSP_FAMILY and the BSP 
> directory containing this *.cfg file. What this the purpose of this stuff? 
> Can we remove it?
> 
> It shouldn't be used anymore. I think it was used by the old m4 logic that 
> found BSPs.
> 
> It is still a useful concept but no use to the build system.

The BSP family is used in the no-preinstall build to find the linkcmds files. 
Setting it in the .cfg file seems dangerous and I think should be removed. 

Chris___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

[PATCH 1/3] bsps/powerpc: Move shared irq.h

2018-01-03 Thread Sebastian Huber
This header file is only used by motorola_powerpc, so not shared.

Update #3254.
Update #3268.
---
 c/src/lib/libbsp/powerpc/motorola_powerpc/Makefile.am | 4 ++--
 .../libbsp/powerpc/{shared/irq => motorola_powerpc/include/bsp}/irq.h | 0
 c/src/lib/libbsp/powerpc/motorola_powerpc/preinstall.am   | 2 +-
 c/src/lib/libbsp/powerpc/mvme3100/Makefile.am | 3 +--
 4 files changed, 4 insertions(+), 5 deletions(-)
 rename c/src/lib/libbsp/powerpc/{shared/irq => 
motorola_powerpc/include/bsp}/irq.h (100%)

diff --git a/c/src/lib/libbsp/powerpc/motorola_powerpc/Makefile.am 
b/c/src/lib/libbsp/powerpc/motorola_powerpc/Makefile.am
index ade69a2323..657dde206a 100644
--- a/c/src/lib/libbsp/powerpc/motorola_powerpc/Makefile.am
+++ b/c/src/lib/libbsp/powerpc/motorola_powerpc/Makefile.am
@@ -84,13 +84,13 @@ libbsp_a_SOURCES += ../../powerpc/shared/console/consoleIo.h
 libbsp_a_SOURCES += ../../powerpc/shared/console/keyboard.h
 libbsp_a_SOURCES += ../../powerpc/shared/console/uart.h
 
-include_bsp_HEADERS += ../../powerpc/shared/irq/irq.h \
+include_bsp_HEADERS += include/bsp/irq.h \
../../../libcpu/@RTEMS_CPU@/@exceptions@/bspsupport/irq_supp.h
 
 # irq
 libbsp_a_SOURCES += ../../powerpc/shared/irq/irq_init.c
 libbsp_a_SOURCES += ../../powerpc/shared/irq/openpic_i8259_irq.c
-libbsp_a_SOURCES += ../../powerpc/shared/irq/i8259.c 
../../powerpc/shared/irq/irq.h
+libbsp_a_SOURCES += ../../powerpc/shared/irq/i8259.c
 
 include_bsp_HEADERS += ../../powerpc/shared/motorola/motorola.h
 # motorola
diff --git a/c/src/lib/libbsp/powerpc/shared/irq/irq.h 
b/c/src/lib/libbsp/powerpc/motorola_powerpc/include/bsp/irq.h
similarity index 100%
rename from c/src/lib/libbsp/powerpc/shared/irq/irq.h
rename to c/src/lib/libbsp/powerpc/motorola_powerpc/include/bsp/irq.h
diff --git a/c/src/lib/libbsp/powerpc/motorola_powerpc/preinstall.am 
b/c/src/lib/libbsp/powerpc/motorola_powerpc/preinstall.am
index 6396cb5b66..8604111de3 100644
--- a/c/src/lib/libbsp/powerpc/motorola_powerpc/preinstall.am
+++ b/c/src/lib/libbsp/powerpc/motorola_powerpc/preinstall.am
@@ -85,7 +85,7 @@ $(PROJECT_INCLUDE)/bsp/uart.h: 
../../powerpc/shared/console/uart.h $(PROJECT_INC
$(INSTALL_DATA) $< $(PROJECT_INCLUDE)/bsp/uart.h
 PREINSTALL_FILES += $(PROJECT_INCLUDE)/bsp/uart.h
 
-$(PROJECT_INCLUDE)/bsp/irq.h: ../../powerpc/shared/irq/irq.h 
$(PROJECT_INCLUDE)/bsp/$(dirstamp)
+$(PROJECT_INCLUDE)/bsp/irq.h: include/bsp/irq.h 
$(PROJECT_INCLUDE)/bsp/$(dirstamp)
$(INSTALL_DATA) $< $(PROJECT_INCLUDE)/bsp/irq.h
 PREINSTALL_FILES += $(PROJECT_INCLUDE)/bsp/irq.h
 
diff --git a/c/src/lib/libbsp/powerpc/mvme3100/Makefile.am 
b/c/src/lib/libbsp/powerpc/mvme3100/Makefile.am
index 6bf46a9f67..b86c21a864 100644
--- a/c/src/lib/libbsp/powerpc/mvme3100/Makefile.am
+++ b/c/src/lib/libbsp/powerpc/mvme3100/Makefile.am
@@ -74,8 +74,7 @@ libbsp_a_SOURCES += ../../powerpc/shared/console/uart.c \
 include_bsp_HEADERS += irq/irq.h
 # irq
 libbsp_a_SOURCES += irq/irq_init.c \
-../../powerpc/shared/irq/openpic_i8259_irq.c \
-../../powerpc/shared/irq/irq.h
+../../powerpc/shared/irq/openpic_i8259_irq.c
 
 include_bsp_HEADERS += ../../powerpc/shared/openpic/openpic.h
 # openpic
-- 
2.12.3

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel


[PATCH 2/3] bsps/powerpc: Rename BSP specific linkcmds.base

2018-01-03 Thread Sebastian Huber
Avoid name conflicts with shared linkcmds.base.

Update #3254.
---
 c/src/lib/libbsp/powerpc/gen5200/Makefile.am| 2 +-
 c/src/lib/libbsp/powerpc/gen5200/preinstall.am  | 6 +++---
 c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.brs5l | 2 +-
 c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.brs6l | 2 +-
 c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.dp2   | 2 +-
 .../gen5200/startup/{linkcmds.base => linkcmds.gen5200_base}| 0
 c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.icecube   | 2 +-
 c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.pm520_cr825   | 2 +-
 c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.pm520_ze30| 2 +-
 c/src/lib/libbsp/powerpc/tqm8xx/Makefile.am | 2 +-
 c/src/lib/libbsp/powerpc/tqm8xx/preinstall.am   | 6 +++---
 c/src/lib/libbsp/powerpc/tqm8xx/startup/linkcmds.tqm8xx | 2 +-
 .../powerpc/tqm8xx/startup/{linkcmds.base => linkcmds.tqm8xx_base}  | 0
 13 files changed, 15 insertions(+), 15 deletions(-)
 rename c/src/lib/libbsp/powerpc/gen5200/startup/{linkcmds.base => 
linkcmds.gen5200_base} (100%)
 rename c/src/lib/libbsp/powerpc/tqm8xx/startup/{linkcmds.base => 
linkcmds.tqm8xx_base} (100%)

diff --git a/c/src/lib/libbsp/powerpc/gen5200/Makefile.am 
b/c/src/lib/libbsp/powerpc/gen5200/Makefile.am
index 19b4312205..3110518f21 100644
--- a/c/src/lib/libbsp/powerpc/gen5200/Makefile.am
+++ b/c/src/lib/libbsp/powerpc/gen5200/Makefile.am
@@ -32,7 +32,7 @@ rtems_crti.$(OBJEXT): ../../powerpc/shared/start/rtems_crti.S
$(CPPASCOMPILE) -o $@ -c $<
 project_lib_DATA += rtems_crti.$(OBJEXT)
 
-dist_project_lib_DATA += startup/linkcmds.base
+dist_project_lib_DATA += startup/linkcmds.gen5200_base
 project_lib_DATA += startup/linkcmds
 EXTRA_DIST += startup/linkcmds.brs5l
 EXTRA_DIST += startup/linkcmds.brs6l
diff --git a/c/src/lib/libbsp/powerpc/gen5200/preinstall.am 
b/c/src/lib/libbsp/powerpc/gen5200/preinstall.am
index 382b283794..b6b203150d 100644
--- a/c/src/lib/libbsp/powerpc/gen5200/preinstall.am
+++ b/c/src/lib/libbsp/powerpc/gen5200/preinstall.am
@@ -85,9 +85,9 @@ $(PROJECT_LIB)/rtems_crti.$(OBJEXT): rtems_crti.$(OBJEXT) 
$(PROJECT_LIB)/$(dirst
$(INSTALL_DATA) $< $(PROJECT_LIB)/rtems_crti.$(OBJEXT)
 TMPINSTALL_FILES += $(PROJECT_LIB)/rtems_crti.$(OBJEXT)
 
-$(PROJECT_LIB)/linkcmds.base: startup/linkcmds.base $(PROJECT_LIB)/$(dirstamp)
-   $(INSTALL_DATA) $< $(PROJECT_LIB)/linkcmds.base
-PREINSTALL_FILES += $(PROJECT_LIB)/linkcmds.base
+$(PROJECT_LIB)/linkcmds.gen5200_base: startup/linkcmds.gen5200_base 
$(PROJECT_LIB)/$(dirstamp)
+   $(INSTALL_DATA) $< $(PROJECT_LIB)/linkcmds.gen5200_base
+PREINSTALL_FILES += $(PROJECT_LIB)/linkcmds.gen5200_base
 
 $(PROJECT_LIB)/linkcmds: startup/linkcmds $(PROJECT_LIB)/$(dirstamp)
$(INSTALL_DATA) $< $(PROJECT_LIB)/linkcmds
diff --git a/c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.brs5l 
b/c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.brs5l
index 944cc36f4d..58407e5f56 100644
--- a/c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.brs5l
+++ b/c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.brs5l
@@ -12,4 +12,4 @@ MEMORY {
REGS : ORIGIN = 0xf000, LENGTH = 64k
 }
 
-INCLUDE linkcmds.base
+INCLUDE linkcmds.gen5200_base
diff --git a/c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.brs6l 
b/c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.brs6l
index 3563f49f11..ae80a72ad5 100644
--- a/c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.brs6l
+++ b/c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.brs6l
@@ -12,4 +12,4 @@ MEMORY {
REGS : ORIGIN = 0xf000, LENGTH = 64k
 }
 
-INCLUDE linkcmds.base
+INCLUDE linkcmds.gen5200_base
diff --git a/c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.dp2 
b/c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.dp2
index 398919ae8c..4ad76d6fce 100644
--- a/c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.dp2
+++ b/c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.dp2
@@ -12,4 +12,4 @@ MEMORY {
DPRAM : ORIGIN = 0x0, LENGTH = 0
 }
 
-INCLUDE linkcmds.base
+INCLUDE linkcmds.gen5200_base
diff --git a/c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.base 
b/c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.gen5200_base
similarity index 100%
rename from c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.base
rename to c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.gen5200_base
diff --git a/c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.icecube 
b/c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.icecube
index 17c707fb49..c05d45a852 100644
--- a/c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.icecube
+++ b/c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.icecube
@@ -12,4 +12,4 @@ MEMORY {
DPRAM : ORIGIN = 0x0, LENGTH = 0
 }
 
-INCLUDE linkcmds.base
+INCLUDE linkcmds.gen5200_base
diff --git a/c/src/lib/libbsp/powerpc/gen5200/startup/linkcmds.pm520_cr825 
b/c/src/lib/libbsp/pow

[PATCH 3/3] bsps/powerpc: Remove unused RTEMS_CPU_MODEL

2018-01-03 Thread Sebastian Huber
---
 c/src/lib/libcpu/powerpc/configure.ac | 20 +++-
 1 file changed, 3 insertions(+), 17 deletions(-)

diff --git a/c/src/lib/libcpu/powerpc/configure.ac 
b/c/src/lib/libcpu/powerpc/configure.ac
index 9f57922cc3..81e6bfab2c 100644
--- a/c/src/lib/libcpu/powerpc/configure.ac
+++ b/c/src/lib/libcpu/powerpc/configure.ac
@@ -24,21 +24,14 @@ AM_CONDITIONAL(shared, \
 || test "$RTEMS_CPU_MODEL" = "mpc750" \
 || test "$RTEMS_CPU_MODEL" = "mpc7400" \
 || test "$RTEMS_CPU_MODEL" = "mpc7455" \
-|| test "$RTEMS_CPU_MODEL" = "mpc7457" \
 || test "$RTEMS_CPU_MODEL" = "mpc555" \
 || test "$RTEMS_CPU_MODEL" = "mpc55xx" \
-|| test "$RTEMS_CPU_MODEL" = "mpc5xx" \
-|| test "$RTEMS_CPU_MODEL" = "ppc603e" \
-|| test "$RTEMS_CPU_MODEL" = "ppc403" \
 || test "$RTEMS_CPU_MODEL" = "ppc405" \
 || test "$RTEMS_CPU_MODEL" = "ppc440" \
 || test "$RTEMS_CPU_MODEL" = "mpc604" \
 || test "$RTEMS_CPU_MODEL" = "mpc6xx" \
-|| test "$RTEMS_CPU_MODEL" = "mpc8xx" \
-|| test "$RTEMS_CPU_MODEL" = "mpc821" \
 || test "$RTEMS_CPU_MODEL" = "mpc860" \
 || test "$RTEMS_CPU_MODEL" = "mpc8240" \
-|| test "$RTEMS_CPU_MODEL" = "mpc8245" \
 || test "$RTEMS_CPU_MODEL" = "mpc8260" \
 || test "$RTEMS_CPU_MODEL" = "mpc83xx" \
 || test "$RTEMS_CPU_MODEL" = "qoriq" \
@@ -47,30 +40,23 @@ AM_CONDITIONAL(shared, \
 # test on CPU type
 AM_CONDITIONAL(mpc505, test "$RTEMS_CPU_MODEL" = "mpc505")
 AM_CONDITIONAL(mpc55xx, test "$RTEMS_CPU_MODEL" = "mpc55xx")
-AM_CONDITIONAL(mpc5xx, test "$RTEMS_CPU_MODEL" = "mpc5xx" \
-|| test "$RTEMS_CPU_MODEL" = "mpc555" )
+AM_CONDITIONAL(mpc5xx, test "$RTEMS_CPU_MODEL" = "mpc555" )
 AM_CONDITIONAL(mpc6xx, test "$RTEMS_CPU_MODEL" = "mpc6xx" \
 || test "$RTEMS_CPU_MODEL" = "mpc604" \
 || test "$RTEMS_CPU_MODEL" = "mpc7400" \
 || test "$RTEMS_CPU_MODEL" = "mpc7455" \
-|| test "$RTEMS_CPU_MODEL" = "mpc7457" \
 || test "$RTEMS_CPU_MODEL" = "mpc750" \
 || test "$RTEMS_CPU_MODEL" = "mpc8240" \
-|| test "$RTEMS_CPU_MODEL" = "mpc8245" \
 || test "$RTEMS_CPU_MODEL" = "mpc83xx")
-AM_CONDITIONAL(mpc8xx, test "$RTEMS_CPU_MODEL" = "mpc8xx" \
-|| test "$RTEMS_CPU_MODEL" = "mpc821" \
-|| test "$RTEMS_CPU_MODEL" = "mpc860" )
+AM_CONDITIONAL(mpc8xx, test "$RTEMS_CPU_MODEL" = "mpc860" )
 AM_CONDITIONAL(mpc8260, test "$RTEMS_CPU_MODEL" = "mpc8260")
 AM_CONDITIONAL(mpc83xx, test "$RTEMS_CPU_MODEL" = "mpc83xx")
 AM_CONDITIONAL(qoriq, test "$RTEMS_CPU_MODEL" = "qoriq")
 
 # the ppc405 share files with the ppc403
-AM_CONDITIONAL(ppc403, test "$RTEMS_CPU_MODEL" = "ppc403")
 AM_CONDITIONAL(ppc405, test "$RTEMS_CPU_MODEL" = "ppc405")
 AM_CONDITIONAL(ppc440, test "$RTEMS_CPU_MODEL" = "ppc440")
-AM_CONDITIONAL(ppc4xx, test "$RTEMS_CPU_MODEL" = "ppc403" \
-|| test "$RTEMS_CPU_MODEL" = "ppc405")
+AM_CONDITIONAL(ppc4xx, test "$RTEMS_CPU_MODEL" = "ppc405")
 
 AM_CONDITIONAL(e500_clock, test "$RTEMS_CPU_MODEL" = "e500" \
 || test "$RTEMS_CPU_MODEL" = "ppc440")
-- 
2.12.3

___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel


Re: No preinstall and rtems.git master freeze

2018-01-03 Thread Gedare Bloom
On Sat, Dec 23, 2017 at 7:52 PM, Chris Johns  wrote:
> Hi,
>
> I have a branch called 'no-preinstall' in a personal repo:
>
>  https://git.rtems.org/chrisj/rtems.git/?h=no-preinstall
>
> It builds a beagleboneblack without networking and not much else looking at 
> the
> results of a tier-1 build:
>
>  https://lists.rtems.org/pipermail/build/2017-December/000324.html
>
> It is now a process of working through the issues. A brief review shows a mix 
> of
> source referencing a local header, ie '#include "cs8900.h"' and the header is
> now in a fixed part of the header API tree, or build related issues like the
> Xilinx Zynq's linkercmds file is not being found. The linkcmds files are now
> referenced in the source and not copied and renamed to the build tree which
> exposes issues in some BSPs.
>
> I will start to push changes onto my personal branch. Please post patches
> against the branch to this list and I will merge them. I need help or this 
> will
> take a while to complete.
>
> I suggest we freeze the rtems.git master branch if this is possible until we 
> get
> the no-preinstall changes merged.
>
What are the conditions to "thaw" it / when do you expect to be
comfortable merging the branch?

Is there any point to freezing the master versus merging your branch
as it is and fixing it? I guess some users who grab master will
encounter trouble, so perhaps not great.

> Should I post the changes for review or can the branch I listed above we OK 
> for
> review purposes?
>
I believe the branch listed is OK for review purposes.

> Thanks
> Chris
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel


GSoC Mentors and Open Projects

2018-01-03 Thread Gedare Bloom
RTEMS development community:

The GSoC organization application opens tomorrow. If you anticipate
being able to mentor/co-mentor this summer please let me know, or if
you were a mentor in the past but are not able to this year please
also give me a heads up. An ounce of prevention is worth a pound of
cure.

If everyone could, please take a look at the Open Projects page to see
if anything should be added or removed. Also, if you would like to
take the time to convert one of the older open projects into a ticket,
that would be greatly appreciated! Potential Mentors should especially
be sure that any projects you might like to mentor exist as a ticket.

https://devel.rtems.org/wiki/Developer/OpenProjects

Thanks, and Happy New Year,
Gedare
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel


Re: GSoC Mentors and Open Projects

2018-01-03 Thread Denis Obrezkov
May be risc-v port should be added as a ticket? Hesham?

P.S. What a shame that Google differentiates stipend amounts. It really
demotivates students.

2018-01-03 20:24 GMT+03:00 Gedare Bloom :

> RTEMS development community:
>
> The GSoC organization application opens tomorrow. If you anticipate
> being able to mentor/co-mentor this summer please let me know, or if
> you were a mentor in the past but are not able to this year please
> also give me a heads up. An ounce of prevention is worth a pound of
> cure.
>
> If everyone could, please take a look at the Open Projects page to see
> if anything should be added or removed. Also, if you would like to
> take the time to convert one of the older open projects into a ticket,
> that would be greatly appreciated! Potential Mentors should especially
> be sure that any projects you might like to mentor exist as a ticket.
>
> https://devel.rtems.org/wiki/Developer/OpenProjects
>
> Thanks, and Happy New Year,
> Gedare
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel
>



-- 
Regards, Denis Obrezkov
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: GSoC Mentors and Open Projects

2018-01-03 Thread Christian Mauderer
- Ursprüngliche Mail -
> Von: "Gedare Bloom" 
> An: "RTEMS Devel" 
> Gesendet: Mittwoch, 3. Januar 2018 18:24:21
> Betreff: GSoC Mentors and Open Projects

> RTEMS development community:
> 
> The GSoC organization application opens tomorrow. If you anticipate
> being able to mentor/co-mentor this summer please let me know, or if
> you were a mentor in the past but are not able to this year please
> also give me a heads up. An ounce of prevention is worth a pound of
> cure.
> 
> If everyone could, please take a look at the Open Projects page to see
> if anything should be added or removed. Also, if you would like to
> take the time to convert one of the older open projects into a ticket,
> that would be greatly appreciated! Potential Mentors should especially
> be sure that any projects you might like to mentor exist as a ticket.
> 
> https://devel.rtems.org/wiki/Developer/OpenProjects
> 
> Thanks, and Happy New Year,
> Gedare
> ___
> devel mailing list
> devel@rtems.org
> http://lists.rtems.org/mailman/listinfo/devel

Hello Gedare,

GSoC has been really been a lot of fun last time so I would be happy to be a 
mentor again if there is an interesting proposal.

Regarding the tickets:
- I added some notes and updates to the Beagle BSP ticket.
- Some time back I had a discussion on the mailing list (I think mainly with 
Chris Johns) regarding two WiFi topics. Both might could be a project. I've 
added the tickets to a new "libbsd" section in the project list in the wiki.

By the way: Back when I created the tickets for WiFi I have been in a hurry. So 
the tickets are a little simple and short. I would have liked to reformat and 
improve the tickets at least a little. But I haven't seen a possibility to 
change the initial text. It seems that at least the Beagle Bone ticket has been 
changed a few times. Did I just miss the correct link for changing the ticket 
or is there some special permission necessary to do that?

Regards

Christian
-- 

embedded brains GmbH
Christian Mauderer
Dornierstr. 4
D-82178 Puchheim
Germany
email: christian.maude...@embedded-brains.de
Phone: +49-89-18 94 741 - 18
Fax:   +49-89-18 94 741 - 08
PGP: Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Re: No preinstall and rtems.git master freeze

2018-01-03 Thread Chris Johns
On 4/1/18 1:47 am, Gedare Bloom wrote:
> On Sat, Dec 23, 2017 at 7:52 PM, Chris Johns  wrote:
>> Hi,
>>
>> I have a branch called 'no-preinstall' in a personal repo:
>>
>>  https://git.rtems.org/chrisj/rtems.git/?h=no-preinstall
>>
>> It builds a beagleboneblack without networking and not much else looking at 
>> the
>> results of a tier-1 build:
>>
>>  https://lists.rtems.org/pipermail/build/2017-December/000324.html
>>
>> It is now a process of working through the issues. A brief review shows a 
>> mix of
>> source referencing a local header, ie '#include "cs8900.h"' and the header is
>> now in a fixed part of the header API tree, or build related issues like the
>> Xilinx Zynq's linkercmds file is not being found. The linkcmds files are now
>> referenced in the source and not copied and renamed to the build tree which
>> exposes issues in some BSPs.
>>
>> I will start to push changes onto my personal branch. Please post patches
>> against the branch to this list and I will merge them. I need help or this 
>> will
>> take a while to complete.
>>
>> I suggest we freeze the rtems.git master branch if this is possible until we 
>> get
>> the no-preinstall changes merged.
>>
> What are the conditions to "thaw" it / when do you expect to be
> comfortable merging the branch?

I have worked on this task over the break and I have passed the baton to
Sebastian who is now working on it while I am consumed landscaping the backyard.

> Is there any point to freezing the master versus merging your branch
> as it is and fixing it? I guess some users who grab master will
> encounter trouble, so perhaps not great.

The issue is header changes break the moved files.

> 
>> Should I post the changes for review or can the branch I listed above we OK 
>> for
>> review purposes?
>>
> I believe the branch listed is OK for review purposes.
> 

I believe this is the path Sebastian will now follow.

This is a major change and it is working well considering the size of the
change. I feel this level of shake up will have issues and we will need to
address those as they are uncovered. I also think there are places we can
improve what we do so some parts of what has been done is to keep the changes
manageable.

Chris
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel