Hi, After a longer break I'm pleased to announce an update of the L4Re system software. https://l4re.org Besides bug fixes and enhancements, noteworthy changes and additions of this update include: All: - LLVM/Clang: Fiasco.OC is supported with Clang now, for the userland we're nearly there - Updates for recent GCC versions - CROSS_COMPILE is the preferred way to set the compiler prefix now - URLs have been consolidated to be under the l4re.org domain but old ones will remain to work for a foreseeable future. L4Re: - Package reorganization: Core packages have been moved to a more hierarchical structure, e.g. l4re-core and io - New RPC framework using C++ that generates client and server side code from a single definition, code and examples have been adapted accordingly - Software updates, e.g. libstdc++, lua, libpng, libjpeg, lwip - New L4Re::Dma_space interface to support DMA and IOMMUs - io gained support for IOMMUs and MSI remapping - Virtio library to support the development of virtio host applications - Documentation improvements: https://l4re.org/doc/ Fiasco.OC: - IOMMU support, including MSI remapping (currently VT-d) - Clang support L4Linux: - Added x86-64 variant - Updated to version Linux 4.3 - MSI / MSI-X support Happy new year, Adam
Hi. Nice work Adam and all! Best wishes for 2016, Johan On Thu, 2015-12-31 at 16:53 +0100, Adam Lackorzynski wrote:
Hi,
After a longer break I'm pleased to announce an update of the L4Re system software.
Besides bug fixes and enhancements, noteworthy changes and additions of this update include:
All: - LLVM/Clang: Fiasco.OC is supported with Clang now, for the userland we're nearly there - Updates for recent GCC versions - CROSS_COMPILE is the preferred way to set the compiler prefix now - URLs have been consolidated to be under the l4re.org domain but old ones will remain to work for a foreseeable future.
L4Re: - Package reorganization: Core packages have been moved to a more hierarchical structure, e.g. l4re-core and io - New RPC framework using C++ that generates client and server side code from a single definition, code and examples have been adapted accordingly - Software updates, e.g. libstdc++, lua, libpng, libjpeg, lwip - New L4Re::Dma_space interface to support DMA and IOMMUs - io gained support for IOMMUs and MSI remapping - Virtio library to support the development of virtio host applications - Documentation improvements: https://l4re.org/doc/
Fiasco.OC: - IOMMU support, including MSI remapping (currently VT-d) - Clang support
L4Linux: - Added x86-64 variant - Updated to version Linux 4.3 - MSI / MSI-X support
Happy new year, Adam
_______________________________________________ l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers --
PGP Public Key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x08EDE1CD977FD2AB
Great, thanks to all the hard workers. But, the Config process seems to be broken, a little bit. I try to build for a Zynq ZedBoard. Doing: $ make setup $ make there is no chance to select 'zedboard' or 'zynq'. Anyway, after '$ make setup', i manually changed obj/fiasco/arm-mp-rv-a9-vexpress/globalconfig.out to my needing (CONFIG_PF_ZYNQ=y, CONFIG_BSP_NAME="zynq"). Although, i guess there is still something wrong. Because, the output of '$ make' says "=== Updating RAM_BASE for platform rv_vexpress to 0x60000000 ===" which is not corresponding to 'src/l4/mk/platforms/zynq.conf'. Maybe, there is a mash up with CONFIG_BSP_NAME 'zynq' and platform name 'zedboard'. Anybody know how to fix this? Greetings, ba_f Am 2015-12-31 16:53, schrieb Adam Lackorzynski:
Hi,
After a longer break I'm pleased to announce an update of the L4Re system software.
Besides bug fixes and enhancements, noteworthy changes and additions of this update include:
All: - LLVM/Clang: Fiasco.OC is supported with Clang now, for the userland we're nearly there - Updates for recent GCC versions - CROSS_COMPILE is the preferred way to set the compiler prefix now - URLs have been consolidated to be under the l4re.org domain but old ones will remain to work for a foreseeable future.
L4Re: - Package reorganization: Core packages have been moved to a more hierarchical structure, e.g. l4re-core and io - New RPC framework using C++ that generates client and server side code from a single definition, code and examples have been adapted accordingly - Software updates, e.g. libstdc++, lua, libpng, libjpeg, lwip - New L4Re::Dma_space interface to support DMA and IOMMUs - io gained support for IOMMUs and MSI remapping - Virtio library to support the development of virtio host applications - Documentation improvements: https://l4re.org/doc/
Fiasco.OC: - IOMMU support, including MSI remapping (currently VT-d) - Clang support
L4Linux: - Added x86-64 variant - Updated to version Linux 4.3 - MSI / MSI-X support
Happy new year, Adam
_______________________________________________ l4-hackers mailing list l4-hackers@os.inf.tu-dresden.de http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
On Mon Jan 04, 2016 at 15:53:22 +0100, ba_f wrote:
Great, thanks to all the hard workers.
But, the Config process seems to be broken, a little bit.
I try to build for a Zynq ZedBoard.
Doing: $ make setup $ make
there is no chance to select 'zedboard' or 'zynq'.
For the snapshot, those choices shall just be examples, not a complete selection of combinations!
Anyway, after '$ make setup', i manually changed obj/fiasco/arm-mp-rv-a9-vexpress/globalconfig.out to my needing (CONFIG_PF_ZYNQ=y, CONFIG_BSP_NAME="zynq"). Although, i guess there is still something wrong. Because, the output of '$ make' says "=== Updating RAM_BASE for platform rv_vexpress to 0x60000000 ===" which is not corresponding to 'src/l4/mk/platforms/zynq.conf'. Maybe, there is a mash up with CONFIG_BSP_NAME 'zynq' and platform name 'zedboard'.
Anybody know how to fix this?
Regarding building+launching nothing has changed to previous versions. Go to the l4re-build directory and do: make uimage PT=zedboard and you should get an image for the zedboard (given the search path points to the proper Fiasco build directory, as you described). Adam -- Adam adam@os.inf.tu-dresden.de Lackorzynski http://os.inf.tu-dresden.de/~adam/
participants (4)
-
Adam Lackorzynski -
Adam Lackorzynski -
ba_f -
Johan Dams