l4-hackers May 2014

l4-hackers@os.inf.tu-dresden.de

17 participants
27 discussions

Missing library question
by Sören Jonsson 26 May '14

26 May '14

Hello, After an upgrade from VMWare Workstation 7 to 10 and removing my previous debian virtual machine. I am now building L4 and L4Re again. The build of L4 went smoothly, but when I try to build L4Re I get the following error message: === Building package "bootstrap" === ===> Linking bootstrap32.elf /usr/bin/ld skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/4.7/libgcc.a when searching for -lgcc /usr/bin/ld: cannot find -lgcc collect2: error: ld returned 1 exit status make [5]: *** [bootstrap32.elf] Error 1 make [4]: *** [/home/osj/l4re/pkg/bootstrap/server/src/OBJ-amd64_amdfam10] Error 2 make [3]: *** [src] Error 2 make [2]: *** [server] Error 2 make [1]: *** [bootstrap] Error 2 make: *** [pkg] Error 2 I have configured L4 and L4Re to build for an AMD K10 processor using the AMD64 architecture. The build OS is: Debian Linux 7.3.0 Compiler: gcc 4.7.2-5 Best regards, Sören Jonsson Sweden

2 1

About DMA mem and IO Server
by Taeung 23 May '14

23 May '14

Thanks Martin :-) Referencing website link which you give me , I'm trying to secure Ethernet on L4Linux. I've got eth0 and configure ip address, netmask , etc. But if I do 'ping 8.8.8.8' for test, error occur such as 'Error connecting: Network is unreachable'. I suspect that the problem is about DMA mem. As below , there is 'WARNING: phys mmio resource allocation failed' log message.. What is the problem ? May this problem be the reason why network is unreachable ? ======================== ..(omitted).. IO | Io service IO | Verboseness level: 4 IO | unused physical memory space: IO | [00000001000000-0000000fffffff] IO | [00000050000000-000000ffffffff] IO | Loading: config 'rom/imx6q.io' *IO | WARNING: phys mmio resource allocation failed** **IO | <0x1bf18>IOMEM [00000010426000-000000104a5fff 80000] non-pref (32bit) (align=7ffff flags=c002)** **IO | WARNING: phys mmio resource allocation failed** **IO | <0x1bf18>IOMEM [00000010426000-000000104a5fff 80000] non-pref (32bit) (align=7ffff flags=c002)* IO | P6Device: l4linux "" IO | P6Device: (noname) "L40009" IO | P6Device: imx6q-fec.dev0 "imx6q-fec.0" IO | <0x14678> IOMEM [00000002188000-0000000218bfff 4000] non-pref (32bit) (align=3fff flags=4002) IO | <0x1be28> IRQ [00000000000096-00000000000096 1] none (32bit) (align=0 flags=4001) IO | P6Device: dmamem "dmamem" IO | <0x1bf18> IOMEM [00000010426000-000000104a5fff 80000] non-pref (32bit) (align=7ffff flags=c002) ..(omitted).. ======================== I'd appreciate whoever give me hints. - Taeung - On 05/10/2014 06:39 PM, Martin Schröder wrote: > Hi Taeung, > this DMAMEM block is mandatory for devices writing/reading directly > into/from RAM. > > Maybe you'll have a look into another board patchset: > http://fooprotected.wordpress.com/2012/04/12/l4linux-patch-for-mv643xx-ethe… > > > and also here: > https://github.com/Ksys-labs/L4Reap/blob/master/files/gumstix-fb-l4l.io > > > > Best regards, > Martin > > > Am 09.05.2014 19:34, TaeWoong Song schrieb: >> Thanks for your advice ,Martin !! >> >> I understand what you mean. >> So, I'm modify source code according to imx6's single Ethernet. >> >> Up to now, FEC Ethernet Driver has been initialized and eth0 has been >> secured in L4Linux. >> But I didn't succeed it yet. >> >> Do I have to need to get DMAMEM ? >> Or, is it fine that I omit DMAMEM ? >> >> However, your patch has been being very helpful to me. >> I'll continue securing Ethernet in L4 Linux. >> >> - Taeung - >> >> On May 9, 2014, at 10:12 PM, Martin Schröder <mschroeder(a)web.de> wrote: >> >>> Just a short addidion: >>> I just had a short look into the freescale spec: The i.MX6 you are >>> using has only a single Ethernet, my i.MX28 has dual Ethernet. So >>> you can skip everything I wrote abot the second PHY connected to the >>> MDIO bus of the first FEC. And you can also remove all lines related >>> to the Dummy-PHY (your Question 5) and turn CONFIG_FIXED_PHY off. >>> >>> Best regards, >>> Martin >>> >>> >>> Gesendet: Mittwoch, 07. Mai 2014 um 16:57 Uhr >>> Von: "Martin Schröder" <mschroeder(a)web.de> >>> An: Taeung <treeze.taeung(a)gmail.com> >>> Betreff: Re: May I ask you questions about your path? >>> Am 07.05.2014 16:08, schrieb Taeung:> Hi, Martin :-) >>>> >>>> Sorry, I take up your time. >>> >>> no problem :-) >>> >>>> May I ask you questions about your path? >>>> >>>> Question 1. In 'imx28.io' file , what mean 'DMAMEM' and 'new-res >>>> Mmio_ram()' ? >>>> >>>> I know that 'Mmio()' need arguments which are start and end address. >>>> But, I don't know 'Mmio_ram()'. >>> >>> I already answered your question on the list :-) >>> >>> you'll find also another reference in the list-archive: >>> >>> <20111117204103.GC13416(a)os.inf.tu-dresden.de> >>> Am 17.11.2011 21:41, schrieb Adam Lackorzynski:> On Thu Nov 17, 2011 >>> at 12:49:31 +0400, Sartakov A. Vasily wrote: >>>>> So.. >>>>> usb host via ehci uses dma and i have problem in >>>>> pool_alloc_page(mm/dmapool.c): >>>>> dma_alloc_coherent (arhc/l4/mm/) returns 0, cos l4x_dma_mem_alloc >>>>> returns 0 too. >>>> >>>> I guess you need to put some 'dmamem' onto your vbus: >>>> >>>> DMAMEM => new Device() >>>> { >>>> .hid = "dmamem"; >>>> new-res Mmio_ram(<size-in-bytes>, 0); >>>> } >>>> >>>> >>>> >>>> Adam >>>> >>> >>>> Question 2. What is namespace 'shmns' ? >>>> >>>> local shmns = loader:create_namespace({shmns = "shmns"}); (line 69) >>>> shmns = shmns:mode("rw"), (line 89) >>>> >>> >>> I am using the l4shmnet network driver to connect two l4linux >>> instances by a virtual network. This driver is based on shared >>> memory, which I assign to both instaces. You'll see the other >>> reference in the linux kernel command lines where this >>> l4shmnet.add=shmns.add=shmns,maxpart=0x12/0x14 is added. >>> >>> >>>> Question 3. In fec_main.c , '#define clk_get_rate(x) 151000000' (line >>>> 312, 349) >>>> How do you know '151000000' ? >>>> Do you found in imx28 data sheet or other document ? >>> >>> I calculated it backwards. In fec_main.c you'll find "Seet MII speed >>> to 2.5 Mhz (= clk_get_rate() / 2 * phy speed)". So I grabbed the >>> divisor (read out the memory in U-Boot) and multiplied it >>> accordingly to get those 2.5 Mhz. But you could also insert some >>> kdebug("%d\n",clk_get_rate()), compile for a native linux and insert >>> this value instead :-) >>> >>>> Question 4. At line 323, why every variables is NULL ? >>> I have no L4-support for the clocing distribution (not within the >>> address space of the fec chip). So clocking the fec is done in U-Boot >>> >>>> Question 5. At line 260, what mean '.link' and '.speed', .duplex ? >>> I set up a virtual "dummy" phy on the second FEC device if this is >>> in another L4 than the first FEC. So this phy should always report >>> "link up", "100 MBit/s" and "full duplex" to the ethernet driver. >>> >>> >>> Martin >>> >> >

3 3

Doing simple I/O in clntsrv example
by Valentin Hauner 22 May '14

22 May '14

Hi! I'm having some trouble with doing simple I/O actions in the clntsrv example (/src/l4/pkg/examples/clntsrv). I want the client to enter minuend and subtrahend himself, so I've added the following code to client.cc: > printf("Please enter minuend and subtrahend: \n"); > l4_uint32_t val1, val2; > std::cin >> val1 >> val2; iostream is included at the beginning of the file. However, the linker has some serious problems: > ==> Linking ex_clntsrv-client > client.o: In function `main': > /home/hnr/l4re-core-2014022818/src/l4/pkg/examples/clntsrv/client.cc:60: undefined reference to `std::cin' > /home/hnr/l4re-core-2014022818/src/l4/pkg/examples/clntsrv/client.cc:60: undefined reference to `std::istream::operator>>(int&)' > /home/hnr/l4re-core-2014022818/src/l4/pkg/examples/clntsrv/client.cc:60: undefined reference to `std::istream::operator>>(int&)' > client.o: In function `__static_initialization_and_destruction_0': > /home/hnr/l4reb/include/contrib/libstdc++-v3/iostream:72: undefined reference to `std::ios_base::Init::Init()' > /home/hnr/l4reb/include/contrib/libstdc++-v3/iostream:72: undefined reference to `std::ios_base::Init::~Init()' > make[1]: *** [ex_clntsrv-client] Error 1 > make: *** [/home/hnr/l4reb/pkg/examples/clntsrv/OBJ-x86_586-l4f] Error 2 I did not change the Makefile, so g++ is used for compiling (and not gcc). I've added > CXX_FLAGS = -lstdc++ but that doesn't help. I'm using update-alternatives to have different versions of g++ installed simultaneously. Currently, the link points to g++-4.7. But using g++-4.4 does not solve the problem either. Thanks in advance for support!

2 6

interfaces of scheduler Fiasco
by Bouchra Elouri 21 May '14

21 May '14

hello I'm currently reading the code of schudeler fiasco.oc to have an idea about the internal and external interfaces of the scheduler. Can you tell me what exactly are the codes that I have read so I can know the scheduler interfaces (ie with which it communicates) thank you

2 1

Porting Fiasco+L4re to DaVinci DA850 - Linux time wrong
by Peter Howard 21 May '14

21 May '14

I've now got L4Linux running on top of Fiasco+L4re on the DA850. However there appears to be something wrong with the time. Time seems to be passing at a rate of 10-1 (i.e. 1 elapsed second == 10 reported seconds) in Linux. If I change the default Hz rating the L4Linux config (from 100Hz) in either direction L4Linux either hangs or slows down dramatically. If I change the period in the timer driver (in the Fiasco bsp directory) things hang earlier. For the Fiasco BSP I'm using: * timer_tick-single-vector for timer_tick_IMPL, * clock_generic for clock_IMPL, * a da850 timer driver for timer_IMPL. Can someone enlighten me as to how it should work? Thanks -- Peter Howard <pjh(a)northern-ridge.com.au>

2 3

Can you check this patch file(imx6q-fec.patch) ?
by Taeung 20 May '14

20 May '14

Hello, l4 hackers :-) To secure Ethernet on L4 Linux, I've modified source code with yeongchann and we succeeded to obtain Ethernet. we've used 'l4re-snapshot-2014022818' and Freescale i.MX6 Quad SABRE SD board (ARMv7a) I don't know whether this patch can contribute l4 project. But can you check 'imx6q-fec.patch' ? Attached patch is 1. to change UART2 to UART1 for imx6q sabresd (learned by Ahmed Ammar) and 2. to fix compile error(fiasco and l4linux) , 3. to modify source related to FEC ethernet. To put it concretely... ===== About UART for imx6q sabresd ===== (learned by Ahmed Ammar) *1) mem_layout-arm-imx.cpp* (src/kernel/fiasco/src/kern/arm/bsp/imx/mem_layout-arm-imx.cpp) * 2) uart-imx.cpp* (src/kernel/fiasco/src/kern/arm/bsp/imx/uart-imx.cpp) * 3) imx.cc* (src/l4/pkg/bootstrap/server/src/platform/imx.cc) ============================== ===== About compile error ===== *1) tb_entry_output.cc* (src/kernel/fiasco/src/kern/tb_entry_output.cc) *2) Kconfig* (src/l4linux/arch/l4/Kconfig) ======================= ** ===== For FEC ethernet ======* **1) mach_setup.c* (src/l4linux/arch/l4/kernel/arch-arm/mach_setup.c) * **2) fec.h* (src/l4linux/drivers/net/ethernet/freescale/fec.h) *3) fec_main.c* (src/l4linux/drivers/net/ethernet/freescale/fec_main.c) *4) fec_ptp.c* (src/l4linux/drivers/net/ethernet/freescale/fec_ptp.c) *5) Kconfig* (src/l4linux/drivers/net/ethernet/freescale/Kconfig) ====================== ===== For access HW on L4Linux ===== *1) imx6q.io* (src/l4/conf/examples/imx6q.io) *2) l4lx-imx6q.cfg* (src/l4/conf/examples/l4lx-imx6q.cfg) * **3) modules.list* (src/l4/conf/modules.list) =========================== I hope this is of some help to someone. - Taeung -

1 0

Fwd: Re: cannot find -lld-l4
by ba_f 18 May '14

18 May '14

Hello Hackers, Am 2014-05-14 11:23, schrieb Matthias Lange: >> /opt/gcc-linaro-arm-linux-gnueabihf-4.8-2014.03_linux/bin/arm-linux-gnueabihf-ld: cannot find -lld-l4 >> make[3]: *** [myProg] Fehler 1 > > Have you successfully build the 'ldso' package? libld-l4.so is provided > by > this package. > > Matthias. Yes, the lib seems to be there: obj/l4/arm-ca/lib/arm_armv7a/l4f/libld-l4.so obj/l4/arm-ca/pkg/ldso/ldso/OBJ-arm_armv7a-l4f/libld-l4.so obj/l4/arm-ca/config/have/ldso.h obj/l4/arm-ca/pc/ldso.pc obj/l4/arm-ca/pkg/ldso/ldso/OBJ-arm_armv7a-l4f/.ldso.s.o.d objl4/arm-ca/pkg/ldso/ldso/OBJ-arm_armv7a-l4f/ldso.s.o I also checked the 2> output from the snapshot build process, which shows a lot of Warnings, but no Error. Am 2014-05-15 01:04, schrieb Adam Lackorzynski: > Are you trying to build a program using shared libraries? Mind to share > your Makefile? Actually, i try to include libssl.a which Ivan Loskutov ported to L4re. http://os.inf.tu-dresden.de/pipermail/l4-hackers/2012/005141.html >> BTW before that missing lib error, i get a lot of "multiple definition >> of...". > > Could you show some examples of those errors please? > > Adam ./tpm_integrity.o: In function `TPM_Extend': /home/ba_f/vTPM/server/src/tpm_integrity.c:39: multiple definition of `tpm_log' ./tpm_cmd_handler.o:/home/ba_f/vTPM/server/src/tpm_marshalling.h:102: first defined here ./tpm_startup.o: In function `TPM_Startup': /home/ba_f/vTPM/server/src/tpm_startup.c:43: multiple definition of `tpm_read_from_storage' ./tpm_cmd_handler.o:/home/ba_f/vTPM/server/src/tpm_marshalling.h:103: first defined here But these warning/error must come from the build-process, because the code has already been compiled for ARM linux without any Warnings. l4re-snapshot-2014022818 Greets, ba_f

2 1

Doing simple I/O in clntsrv example
by Valentin Hauner 17 May '14

17 May '14

3 2

how to get current cpu id
by Yuxin Ren 15 May '14

15 May '14

How can I get the id of cpu(core) the current thread is running on? Thank you

3 3

OKL4 vs L4::Pistachio
by Taylor Bioniks 15 May '14

15 May '14

How does OKL4 compare with L4::Pistachio as far as speed, security, responsiveness? L4::Pistachio uses kickstart to load it, the core kernel is contained in kernel, and the physical memory manager is stored in sigma0, I'm not even sure if it has a virtual memory manager. Does OKL4 have a built in memory manager, and does it handle virtual memory? Thank you.

3 3

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

l4-hackers May 2014