tions are already answered somewhere then I'd be more
> than happy with a link.
>
> Cheers,
> Thomas
>
> ___
> l4-hackers mailing list
> l4-hackers@os.inf.tu-dresden.de
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-
l error: asm/rwsem.h: No such file or directory
> compilation terminated.
> make[3]: *** [arch/l4/kernel/asm-offsets.s] Error 1
> make[2]: *** [prepare0] Error 2
> make[1]: *** [sub-make] Error 2
> make: *** [all] Error 2
>
>
>
> Maybe someone has an idea.
>
> My development platform:
> G
sfully.
> It would be nice if you update the L4Android Website ("Create ISO
> Image") and the configs repository.
>
> Regards
> Giorgio
>
> ___
> l4-hackers mailing list
> l4-hackers@os.inf.tu-dresden.de
> http://os.
nueabi)
> - OS: Ubuntu 11.04 x86
>
> [1] http://pastebin.com/95M7iiPv
> [2] http://pastebin.com/eYvM65ij
>
>
> ___
> l4-hackers mailing list
> l4-hackers@os.inf.tu-dresden.de
> http://os.inf.t
build/tool/gendep/32
>
> LD_HAS_HASH_STYLE_OPTION=y
>
> LDVERSION=220
>
> include /home/mdlemay2/tmp/l4re/l4/build/.config.indep
>
>
>
> Here is my Fiasco (r36) configuration file:
>
>
>
> #
>
> # Automatically generated make config: don
org/download/download.html Thanks.
I now uploaded the images. Make sure to boot L4Android with
androidboot.harware=l4android on the cmdline.
Matthias.
>
> Best regards,
> Michael LeMay
> http://m.lemays.org
>
>
> -----Original Message-
> From: Matthias Lange [mailto:mla
4.
>
> Regards Tobi
>
>
> ___
> l4-hackers mailing list
> l4-hackers@os.inf.tu-dresden.de
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
--
Dipl.-Inf. Matthias Lange
Security in Telecommunications
TU Berlin / Telekom Innovation Laboratories
E
helps as a starting point but could not help me with the problems I'm
> having right now.
>
> Best regards Tobi
>
> ___
> l4-hackers mailing list
> l4-hackers@os.inf.tu-dresden.de
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
via AHCI
* RTC and Hpet support
Karma is released under the terms of the Gnu General Public License
Version 2.
[0] http://karma-vmm.org
[1] http://os.int.tu-dresden.de/fiasco
[2] http://www.isti.tu-berlin.de/security_in_telecommunications
[3] http://os.inf.tu-dresden.de
--
Dipl.-Inf. Matthias
On 05/16/2012 07:59 AM, 석현철 wrote:
> I made the bootable ISO image.
Just burn the image to a CD and boot your PC from CDROM.
Matthias.
--
Dipl.-Inf. Matthias Lange
Security in Telecommunications
TU Berlin / Telekom Innovation Laboratories
Ernst-Reuter-Platz 7, 10587 Berlin
Phone: +49 -
with Pandaboard, I don't know if
> I'm using the right device configuration (in the form of a .devs file) for
> the I/O server of L4Re.
You should have a look into the Pandaboard TRM and gather the right MMIO
regions needed for MMC etc. Then connect those to the vbus for the
nly SDHCI. Maybe I still missed
> something.
> Are there resources other than MMIO regions and IRQs that have to be
> configured for the I/O server?
Probably you need some GPIO pins. Have a look into the Pandaboard TRM.
Matthias.
--
Dipl.-Inf. Matthias Lange
Security in Telecommunicat
assign registers that affect global
> configuration of the platform (e.g., the system control registers), although
> I don't think it is appropriate to assign such registers to only one OS.
You can write a L4Re server which configures those registers. Then L4Android
can access those r
ce ...
Did you miss to copy the l4re binary?
Matthias.
--
Dipl.-Inf. Matthias Lange
Security in Telecommunications
TU Berlin / Telekom Innovation Laboratories
Ernst-Reuter-Platz 7, 10587 Berlin
Phone: +49 - 30 - 8353 58 553
Mobile: +49 - 160 - 587 28 07
Web: http://www.t-labs.tu
this?
Maybe you should start reading the master thesis on how OpenBSD was ported to
Fiasco.OC (Porting OpenBSD to Fiasco [1]).
Matthias.
[1]
http://www.isti.tu-berlin.de/security_in_telecommunications/menue/teaching/diplomamasterbachelor_theses/finished_theses/
--
Dipl.-Inf. Matthias Lange
>
> Best Regards
> ___
> l4-hackers mailing list
> l4-hackers@os.inf.tu-dresden.de
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
--
Dipl.-Inf. Matthias Lange
Security in Telecommunications
TU Berlin / Telekom Innovation Labo
uot;lspci" show something meaningful?
Matthias.
>
> Best Regards
>
>
>
> From: Matthias Lange
> To: Wajidali Whowe
> Cc: "l4-hackers@os.inf.tu-dresden.de"
> Sent: Monday, August 6, 2012 11:48 AM
> Subject: Re: Etherne
tunately terrible:
> "lspci: /sys/bus/pci/devices: No such file or directory"
Can you test this with a small (current) busybox ramdisk first? Make sure to
mount /proc and /sys and then run "mdev -s".
Matthias.
>
>
> Best Regards,
>
>
>
>
> ___
4Linux log. Can you post the result of "grep PCI .config" and
"grep E1000 .config" from your L4Linux config?
Matthias.
--
Dipl.-Inf. Matthias Lange
Security in Telecommunications
TU Berlin / Telekom Innovation Laboratories
Ernst-Reuter-Platz 7, 10587 Berlin
Phone: +49 -
Would it be possible to find out the specific definitions for the Traps? For
> instance does Trap number (in our case 13) tell about the reasons?
Yes. Trap #13 on x86 is a general protection fault. See Intel's IA-32 Software
Developer Manual 3A, chapter 6 for more details.
Matthias.
gt;
>
>
> ___
> l4-hackers mailing list
> l4-hackers@os.inf.tu-dresden.de
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
>
>
> ___
>
his part?
You need something like this in your lua script
hid = l:new_channel()
(for L4Linux)
ev = hid::svr()
(for mag)
ev = hid;
Don't forget to enable the input server with l4-input-srv.enable=1 on the
command line.
Matthias.
--
Dipl.-Inf. Matthias Lange
Security in Telecommu
ot;rom/vmlinuz.android mem=256M l4-input-srv.enable=1 console=ttyLvx
> ramdisk=rom/openwrt-x86-alix2-rootfs.tar.gz root=1:0 ramdisk_size=32768
> l4x_rd=rom/openwrt-x86-alix2-rootfs.tar.gz init=/etc/preinit");
>
>
> Best Regards,
>
>
>
>
usb?
Matthias.
--
Dipl.-Inf. Matthias Lange
Security in Telecommunications
TU Berlin / Deutsche Telekom Laboratories
Ernst-Reuter-Platz 7, 10587 Berlin
Phone: +49 - 30 - 8353 58 553
Mobile: +49 - 160 - 587 28 07
Web: http://www.fgsect.de
___
l4-hackers m
{
> caps = linux_caps,
> },
> "rom/vmlinuz mem=256M console=ttyLv0 root=1:0 ramdisk_size=32768
> l4x_rd=rom/drops-rd.rd init=/bin/sh");
>
>
> local mag_caps = {
> mag = l:new_channel(),
> svc = l:new_channel(),
> };
>
> l:start({
>
dresden.de
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
--
Dipl.-Inf. Matthias Lange
Security in Telecommunications
TU Berlin / Deutsche Telekom Laboratories
Ernst-Reuter-Platz 7, 10587 Berlin
Phone: +49 - 30 - 8353 58 553
Mobile: +49 - 160 - 587 28 07
Web: http://www.fgsect.de
___
e
> `/usr/lib/gcc/x86_64-linux-gnu/4.4.5/crtendS.o' is incompatible with i386
> output
> make[8]: *** [libl4sys.so] Error 1
Have you installed gcc-multilib and g++-multilib? You need those on a 64bit
host.
Matthias.
--
Dipl.-Inf. Matthias Lange
Security in Telecommunications
TU Berl
On 12.03.2013, at 06:04, fiasco wrote:
> I want to know whether the l4re and fiasco.oc have some practical application
> which is open source. I want to build some useful pkg application for demo.
> The example like "Hello, world" is too small.
L4Linux [1] should be a reasonable workload. You c
e are
> .pc files like libdrivers-input.pc etc.what do they work?
Basically the make system takes care of resolving the dependencies. The Control
files give make a hint of inter-package dependencies.
Matthias.
--
Dipl.-Inf. Matthias Lange
Security in Telecommunications
TU Berlin / D
erate the device. The
microkernel only provides isolation (=address space), communication (=IPC) and
scheduling. Device interrupts are transformed into IPC by the microkernel and
forwarded to a registered thread.
Matthias.
--
Dipl.-Inf. Matthias Lange
Security in Telecommunications
k accordingly. You can find a few hints in the
moe source code.
Best,
Matthias.
--
Dipl.-Inf. Matthias Lange
Security in Telecommunications
TU Berlin / Deutsche Telekom Laboratories
Ernst-Reuter-Platz 7, 10587 Berlin
Phone: +49 - 30 - 8353 58
On 29.07.2013, at 14:05, Bob Stewart wrote:
> Let me more precise now that I'm on the machine I was trying to build on.
>
> Following the directions on the L4 Runtime Environment page, I completed
> steps 1, 2 and 3. On step 4, configuring the build tree, I selected my target
> architecture an
On Tue, Oct 01, 2013 at 02:50:42PM +0200, Joel Nider wrote:
> Hi,
>
> >> ? ==> Linking bootstrap32.elf
> >> /usr/bin/ld: skipping incompatible
> >> /usr/lib/gcc/x86_64-linux-gnu/4.6/libgcc.a when searching for -lgcc
> >> /usr/bin/ld: cannot find -lgcc
> >> collect2: ld returned 1 exit status
> >>
Hi,
On Tue, Dec 10, 2013 at 09:51:10AM +0100, Viswa Sekar wrote:
> Hello Sir,
>
> I am on a project on porting l4 fiasco.oc to power pc architecture.
> i am totally new to this.
> kindly provide me documentation/information on the same.
> it will be very useful.
Fiasco has already been ported to
hias.
>
> kindly help me.
>
> thanks in advance
>
>
> On Tue, Dec 10, 2013 at 3:59 PM, Matthias Lange
> mailto:mla...@sec.t-labs.tu-berlin.de>>
> wrote:
>
> Hi,
>
> On Tue, Dec 10, 2013 at 09:51:10AM +0100, Viswa Sekar wrote:
> > Hel
On 28 Feb 2014, at 11:30, Peter Hanzel wrote:
>
> Hello.
>
> I have compiled Fiasco.OC and L4Re for Raspberry PI.
> It boots ok with UART output.
> Now I want to add framebuffer device and output to monitor.
>
> Is this a work in progress or is it already implemented? or to be implemented?
Cur
Hi,
On Thu, Mar 13, 2014 at 06:00:52PM +0900, Irvanda Kurniadi wrote:
> Case closed.
>
> I found that the __assert_fail is not supported in uclibc. Then, I tried to
> change __assert_fail with __assert and it works. But I'm still curious
> about using glibc in L4re. I try to compile my program us
tthias.
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129.
Geschäftsführer: Dr.-Ing. Michael Hohmuth
___
l4-hackers mailing list
l4-hackers@os.inf.tu-dresden.d
ave to create the image manually by issueing
make elfimage E=
in you l4re obj directory.
Matthias.
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129.
Geschäftsführer: Dr.-Ing
Hi,
> On 21 Mar 2014, at 20:27, Alexis Fajardo Moya wrote:
>
> Hello,
> I'm trying to do the same procedure than Waldo. I have fiasco
> compiled in a configured buildir; the same for l4re. I'm using the
> arm-2012.03 toolchain.
>
> When I execute inside l4re builddir the command
Hi,
> On 21 Mar 2014, at 11:33, Taeung wrote:
>
> Hello, l4 hacker.
>
>
> I'm trying to boot "Hello world / L4/ Fiasco" on Freescale i.MX6 Quad SABRE
> SD board(Cortex-A9, ARMv7).
>
> I'm using 'u-boot' and 'uImage'.
> So, i build uimage by "make uimage E=hello ~...".
> And i've try to booti
device. This includes (maybe
not a complete list):
- enable PCI-support in Linux
- select the vPCI L4Linux driver
- enable AHCI driver in Linux
- put correct PCI-devices to L4Linux's vbus
Matthias.
> 3. Whatever packages which is put in a ramdisk, is it no matter ?
> If I
Hi,
> On 25 Mar 2014, at 11:34, Erry Pradana Darajati
> wrote:
>
> Hello L4 Hackers,
> i am doing a project that involve L4 and Pandaboard Rev.B1
> So far, i am successful to boot Fiasco with L4Re in it. And now, i'm moving
> on to boot the L4Linux to Pandaboard
>
> I'm following the tuts fro
directly in your l4re obj
directory? Don't forget to set QEMU_OPTIONS as you need.
Matthias.
>
> ...and that was all. No "Hello world".
> After that I kill the qemu process.
>
> What 's the problem with my procedure?
>
> Sorry for the huge amoun
you can do that. But you also need to pass-through the physical MMC
device to L4Linux (or implement a virtual one). Depending on your platform
this may be a little bit more involved.
Matthias.
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkon
On Thu, Mar 27, 2014 at 08:50:22AM -0400, Alexis Fajardo Moya wrote:
> Hello,
>
> On 27/03/14 05:02, Matthias Lange wrote:
> >What's strange here is, that bootstrap is not moving modules 1 and 2. Are you
> >using the latest snapshot? Which version of qemu are you u
> On 27 Mar 2014, at 15:03, Alexis Fajardo Moya wrote:
>
> Hi,
> El 27/03/14 09:59, Matthias Lange escribió:
>>
>> Also, which cross toolchain are you using?
> I'm using the Code Sourcery toolchain version 2012.03
This one is ok.
Matthias.
__
erview.shtml
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129.
Geschäftsführer: Dr.-Ing. Michael Hohmuth
___
l4-hackers mailing list
l4-hackers@os.inf.tu-dre
.
First you need to identify the native Linux driver for the SD controller. Then
you need to identify all the resources (IO memory, GPIO pins, IRQs, clocks,
...) the driver requires. Then you need to make those resources available to
L4Linux. Most likely you have to define a custom L4Linux ARM platform a
xpired in the queue.
>
> *Laughter* :) Can't handle the truth?
>
> No, but why don't you add my address, then?
Why don't you subscribe yourself like everyone else?
> And - if I'm not subscribed, how come *I* get all the
> mail?
Because netiquette recommends
Hi,
On 18.04.2014, at 13:24, Taeung wrote:
> Hello, Adam and L4 Hackers.
> Thanks for answering.
>
> When I run 'ifconfig', nothing have happened.
> I guess that the cause is /etc folder in ramdisk is not enough to run 'init'.
>
> Would you mind if I ask you another question ?
>
> Must also
> -- vim:set ft=lua:
>
> local lxname = "vmlinuz";
> if L4.Info.arch() == "arm" then
> lxname = "vmlinuz.arm";
> end
>
> L4.default_loader:start(
> { caps = {
> log = L4.Env.log:m("rws"),
>
t;
> BTW before that missing lib error, i get a lot of "multiple
> definition of...".
>
> Any ideas?
> I use Debian 7 32bit.
>
>
> Thanks
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dre
hackers@os.inf.tu-dresden.de
> > http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
> >
> ___
> l4-hackers mailing list
> l4-hackers@os.inf.tu-dresden.de
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
--
M
er__api.html
> thank you
> ___
> l4-hackers mailing list
> l4-hackers@os.inf.tu-dresden.de
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH.
make [1]: *** [bootstrap] Error 2
>make: *** [pkg] Error 2
You need to install gcc-multilib and g++-multilib. The build system cannot
find the 32bit version of libgcc.a.
Matthias.
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: D
Hi,
On 26.05.2014, at 19:57, Yuxin Ren wrote:
> Where is the code around kernel entry, including both l4Re and kernel?
Please have a look at the files named 'entry*' in the Fiasco src directory.
Matthias.
> What is the register format of system call in Fiasco?
>
> Thanks a lot.
> Best
>
frame.cpp.
> Utcb const *iutcb, Utcb *outcb: ??
The UTCB is used to pass and return data between kernel and user (in case of
a system call) or between IPC partners.
If you have other questions in the future please use the l4-hackers mailing
list!
Matthias.
--
Matthias Lange, matthias.la...
w_test0
>
> the same setup was tested successfully under qemu
>
> i appreciate any help
>
> thanks in advance
>
>
> ___
> l4-hackers mailing list
> l4-hackers@os.inf.tu-dresden.de
> http://os.inf.tu-dresden.de/mail
0x1006452
> >
> > This looks like io does not like to hand out the framebuffer memory.
> > Any change when specifying, for example, -m 0x114 ?
> > Does io say something noteworthy, possibly with some -v options
> > supplied?
> >
> >
> >
> > Adam
>
quot;;
>>> Res.io(0x3b0, 0x3bf); -- MDA
>>> Res.io(0x3c0, 0x3df); -- EGA/VGA
>>> Res.io(0x1ce, 0x1d0); -- Vbox
>>> Res.io(0x402, 0x402); -- QEMU Debug Port
>>> Res.mmio(0xa, 0xb);
>>> },
>>>
>
| libio: Warning: Query of 'vbus' failed!
> but it runs, so I don't really know what I am doing wrong. There is no
> complete example that I have found with either libio or sigma0, so I
> need some hints on this, please.
As far as I can see from your configs you missed
x27; vbus in io like you want (e.g. prodb_bus = vbus_prodb). Your
application then has to allocate a vbus capability and has to look for
'prodb_bus' in its capability space.
Matthias.
> },
> log = { "app", "green" },
>},
>"rom/app&
At least
gcc 4.6 is required to build Fiasco and L4Re.
Matthias.
> What Can I do to fix the problem ?
>
> Regards,
> Rima
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129.
Geschäftsführer: Dr.-In
Hi,
> On 21.07.2014, at 18:22, cem akpolat wrote:
>
> Hi,
>
> There is also issues while booting lx_ginger.iso (from l4android.org), it
> stems from the lx_ginger.cfg file.
>
>
> akpolat@akpolatX240:~/Desktop$ qemu-system-x86_64 -cdrom lx_ginger.iso -m 512
> -serial stdio
>
> Welcome to Fi
Hi,
what is the actual problem you encounter? I cannot spot any problem from the
(incomplete?) log.
Matthias.
> On 21.07.2014, at 17:11, cem akpolat wrote:
>
> Dear all,
>
>
> I compiled l4android in the light of the explanation under l4android.org,
> however, I encountered the failure or
t; log = L4.Env.log:m("rws");
> vbus = io_caps.ginger_bus;
> rtc = rtc_caps.rtc;
> rom = L4.Env.rom;
> -- fb = con_caps.con:create(L4.Proto.Goos);
> fb = mag_caps.svc:create(L4.Proto.Goos, "g=640x480,10,10");
> };
>
> L4.default_loader:start(
(v01 BOCHS BXPCAPIC 0001 BXPC
> > 0001)
> > io |
> > /home/akpolat/mysvn/l4android/l4android/src/src/l4/pkg/acpica/lib-acpi/src/osl-basic.cc:344:AcpiOsPhysicalTableOverride(0xbffb89,
> > 0x80007d08, 0x80007d0c): UNINPLEMENTED
> > io | ACPI: HPET 0
_L4LinuxARM.elf -serial stdio
According to the qemu documentation the PBX-A9 target provides a maximum of
1024M of RAM. However, Fiasco and L4Re can only use 512M if I remember
correctly.
Matthias.
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept G
RT,server"
Matthias.
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129.
Geschäftsführer: Dr.-Ing. Michael Hohmuth
___
l4-hackers mailing list
l4-hackers@
can call 'make
-jX S=YOUR_PKG_NAME'. Note that the latter will not check and rebuild the pkg's
dependencies.
Matthias.
[0] http://os.inf.tu-dresden.de/L4Re/doc/
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernk
ccessibility to debugging connectors and very likely a usable
> boot-loader with regard to loading images (network, USB).
Matthias.
[0] http://www.accuvant.com/blog/building-a-nexus-4-uart-debug-cable
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 -
Hello Christian,
On 10/28/2014 08:46 AM, Christian Helmuth wrote:
> Hello Matthias,
>
> On Mon, Oct 27, 2014 at 10:30:03AM +0100, Matthias Lange wrote:
>> Given the Nexus S was built by Samsung the USB port seems promising.
>> However, there is a third option us
ntext.
>
> So, is there any schedule policy about Task?
No. In L4-speak a task is just an address space. Each task has at least
one thread which carries the activity.
Matthias.
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sit
onsoles?
You should have a look into the 'cons' package. It is a console
multiplexer and allows you to interact with multiple clients over one UART.
Matthias.
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dr
ory `/media/chiqiVstorage/l4resnap/src/l4'
> make: *** [qemu] Error 2"
>
> where did i go wrong ?
You need to add /media/chiqiVstorage/l4resnap/src/l4/conf/examples to
your MODULE_SEARCH_PATH.
Best,
Matthias.
> Sorry for the basic question. Any answer and response is really
gt; omap4460?
> Is anyone has experience with it?
>
> Best,
> Zachary
>
>
> ___
> l4-hackers mailing list
> l4-hackers@os.inf.tu-dresden.de
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
>
--
Matthias Lan
Hi,
On 12/15/2014 12:55 PM, Andre Puschmann wrote:
> On 12/15/2014 10:53 AM, Matthias Lange wrote:
>> Hi,
>>
>> L4Re (kernel and userland) do support the OMAP4460 on the Pandaboard and
>> L4Linux/L4Android can be compiled with ARMv7 support. However we do not
>&
Module (scm). There is a 16-bit register for each pin
but unfortunately these registers are not in a particular order. So we
need an offset table to find the correct register for each pin. The
corresponding part for each GPIO chip of the offset table is specified
via the 'scm_offset' para
Hi,
> On 23.12.2014, at 15:29, Erry Pradana Darajati wrote:
>
> >> 1. I want to QEMU to accept input from keyboard to emulate and study how to
> >> use an configure of IO. I study this as a part of my main goal to access
> >> GPIOs of Pandaboard. Well, in my last email i stated that i already in
Hi,
> On 26.12.2014, at 10:22, Zachary wrote:
>
> Hi,
>
> Alexander Tarasikov gmail.com> writes:
>> Genode does have the framebuffer driver (which even supports DSI panels on
> phones and tablets), input and block driver and works very well. I had quite
> nice results running multiple instance
ny of your suggestion
> and answer
>
> P.S : I am attaching my current main program just in case. And i still
> access it directly. without
>
> main2.c : http://pastebin.com/eZKqy1LE
> omap44x2.c : http://pastebin.com/0hupnnyR
> arm-omap4.devs : http://pastebin.com/
col
family for sockets. Fiasco.OC does not provide a POSIX/UNIX API, so
there is no socket() or alike system call.
Maybe you can give a little bit of background of your use case, so that
we can steer you into the right direction.
Matthias.
--
Matthias Lange, matthias.la...@kernkonzept.com, +
*No fpage received*
> *MOE: cmdline: moe --init=rom/clntsrv-server*
> *MOE: Starting: rom/clntsrv-server *
> *MOE: loading 'rom/clntsrv-server'*
> *Could not register my service, is there a 'calc_server' in the caps table?*
> *MOE: task 1565571 exited with 1*
>
On 01/16/2015 04:12 AM, Zachary wrote:
> Matthias Lange kernkonzept.com> writes:
>
>> On pandaboard.org you will find the Omap4 reference manual. This contains
> all the bits and pieces you need.
>> Writing a framebuffer driver for the Pandaboard includes multiple ste
iable the features mentioned above. But
> I could not find the location of the above features in the menu-based
> window.
You can always search in the configuration dialog using '/'.
Matthias.
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept
ion is to generic to answer. Maybe you can describe
your use-case in more detail?
Matthias.
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129.
Geschäftsführe
l panic - not syncing: Attempted to kill init!
> > exitcode=0x000b
> >
> > panic: going to sleep forever, bye
> > l4linux | panic: going to sleep forever, bye
>
>
>
> Adam
> --
> Adam a...@os.inf.tu-dresden.
On 01/22/2015 03:09 AM, Zachary wrote:
> Matthias Lange kernkonzept.com> writes:
>
>>
>> I think the fb-drv package is a good starting point. However you can put
>> your driver into its own package if you like. To plugin nicely with the
>> existing parts of
lution?
Best,
Matthias.
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129.
Geschäftsführer: Dr.-Ing. Michael Hohmuth
___
l4-hackers mailing list
l4-hackers@os
user space component.
Matthias.
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129.
Geschäftsführer: Dr.-Ing. Michael Hohmuth
___
l4-hackers mailing list
ly from a ned script"?
Matthias.
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129.
Geschäftsführer: Dr.-Ing. Michael Hohmuth
___
l4-hackers mailing
>
>
> ___
> l4-hackers mailing list
> l4-hackers@os.inf.tu-dresden.de
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
>
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88
___
> l4-hackers mailing list
> l4-hackers@os.inf.tu-dresden.de
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
>
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129.
Geschäftsf
unable to mount the root file
system. You need to find out which filesystem is on your ramdisk and
compile support for it into the L4Linux kernel.
Matthias.
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden,
;
You need to give L4Linux the log capability
caps = {
log = L4.Env.log:m("rws"),
},
Also see the examples in l4/conf/examples.
Matthias.
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129
pile it and copy it to your
ramdisk (or whatever filesystem your L4Linux has access to).
Matthias.
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129.
Geschäftsführe
e name of your ramdisk.
You also need to mount the ramdisk via a loopback device using '-o loop'.
Matthias.
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129.
Gesc
fault_loader:start(
> { caps = {
> log = L4.Env.log:m("rws"),
> vbus = vbus_l4linux;
> },
> l4re_dbg = L4.Dbg.Warn,log = { "l4linux", "yellow" },
> },
> "rom/" .. lxname .. " mem=256M console=ttyLv0 l4x_rd=ro
mplish but if I assume that you boot
from SD card you need to configure the bootloader (u-boot?) to
automatically boot your L4Re image.
Matthias.
--
Matthias Lange, matthias.la...@kernkonzept.com, +49 - 351 - 41 88 86 14
Kernkonzept GmbH. Sitz: Dresden. Amtsgericht Dresden, HRB 31129.
Geschäfts
1 - 100 of 205 matches
Mail list logo
