Hello,
I have been experimenting a little with L4/Fiasco.OC and have been trying to
gradually build up my skills by looking at Fiasco.OC-UX. However, there are a
few things that aren't really very clear to me from looking at the
documentation.
Looking at the L4Re and Fiasco documentation, it a
On Sunday 17. May 2015 22.41.58 Adam Lackorzynski wrote:
>
> On Mon May 11, 2015 at 11:38:42 +0200, Paul Boddie wrote:
> >
> > Having got this far, running "make ux" with the necessary options gave me
> > the following error:
> >
> > openpty: No
Another year, another look at Fiasco-OC! ;-)
I've been looking again at Fiasco-OC.UX and trying to make sense of the
documentation. In particular, I'd like to be able to get the framebuffer
examples working with the UX graphical console, but it isn't clear to me what
I need to do.
One thing I
On Monday 18. January 2016 00.33.57 Adam Lackorzynski wrote:
>
> On Thu Jan 14, 2016 at 23:07:43 +0100, Paul Boddie wrote:
> >
> > Copying the different x86-fb files into one of my existing
> > MODULE_SEARCH_PATH directories did seem to resolve the above immediate
> &
On Wednesday 20. January 2016 00.13.58 Adam Lackorzynski wrote:
> On Mon Jan 18, 2016 at 16:45:58 +0100, Paul Boddie wrote:
> >
> > In that case, I wanted to prevent a package from being automatically
> > built (the intervm package that seems to be part of the virtualisation
On Thursday 21. January 2016 23.59.16 Adam Lackorzynski wrote:
> On Wed Jan 20, 2016 at 16:40:38 +0100, Paul Boddie wrote:
> >
> > ...I start UX using the following command:
> >
> > make O=mybuild ux E=x86-fb-example MODULES_LIST=conf/examples/x86-fb.list
>
&g
Hello again,
Emboldened by my recent modest success, and taking a look at the previously-
mentioned MIP32 port of Fiasco.OC and L4Re [*], which doesn't really seem to
have any community involved with it, I wondered whether there might be some
general documentation about adding board support file
On Tuesday 2. February 2016 14.44.34 Nourhan Mohamed wrote:
>
> I wanted to build a simple character device module for L4Linux on ARM
> device. However, I don't know who should I compile it for the L4Linux
> version (version 4.3.0). Can you please help me with what files should I
> download to cr
Hello,
I finally got round to looking at L4/Fiasco.OC again, and having previously
looked at the MIPS32 port that was made available on GitHub...
https://github.com/MIPS/fiasco-l4re
...I have been attempting to cross-compile Fiasco and L4Re using the l4re.org
sources. Getting Fiasco to cross-c
On Monday 13. June 2016 00.41.12 Adam Lackorzynski wrote:
> Hi Paul,
>
> On Sun Jun 12, 2016 at 01:19:26 +0200, Paul Boddie wrote:
> > ...I have been attempting to cross-compile Fiasco and L4Re using the
> > l4re.org sources. Getting Fiasco to cross-compile was mostly a ma
On Tuesday 14. June 2016 00.16.35 Adam Lackorzynski wrote:
> On Mon Jun 13, 2016 at 12:50:07 +0200, Paul Boddie wrote:
> >
> > I'm compiling in a Debian unstable chroot on i386. Are you still using
> > i386 to build with? Recent experiences with other projects indicate
On Wednesday 15. June 2016 23.30.47 Adam Lackorzynski wrote:
> On Tue Jun 14, 2016 at 00:42:11 +0200, Paul Boddie wrote:
> > On Tuesday 14. June 2016 00.16.35 Adam Lackorzynski wrote:
> > > On Mon Jun 13, 2016 at 12:50:07 +0200, Paul Boddie wrote:
> > > > I'm co
On Monday 20. June 2016 23.01.51 Adam Lackorzynski wrote:
> On Thu Jun 16, 2016 at 00:10:50 +0200, Paul Boddie wrote:
> >
> > make O=mybuild config
>
> Do you have linux-libc-dev:amd64 installed? If not, please do.
Is this necessary if I'm using the i386 host archite
On Wednesday 22. June 2016 00.24.59 Adam Lackorzynski wrote:
>
> The build system is building host tooling for both 32 and 64 bit
> binaries as x86-based host systems will run both variants quite happily
> nowadays. The goal was to allow using (older) 32bit-only cross compilers
> on 64bit systems
Hello,
I've been trying to write some drivers in L4Re, starting out with a GPIO
driver for a currently-unsupported board, and I think I have mostly understood
the concepts involved. Fortunately, there are already a couple of drivers to
borrow ideas from...
pkg/io/io/server/src/drivers/gpio/bcm
On Wednesday 5. July 2017 22.53.35 Matthias Lange wrote:
>
> On 07/04/2017 11:11 PM, Paul Boddie wrote:
> >
> > It appears that if I just declare the device appropriately in my board's
> > hw_devices.io file, I should be able to get a handle for it using code
>
Hello,
I've been trying to get Fiasco.OC and L4Re booting on the MIPS Creator CI20,
starting out by building the "hello" example.
The first obstacle was actually seeing the serial output, where the board
appears to be configured to output to UART4 in the bootstrap package, but
booting from an
Following up to myself...
On Thursday 13. July 2017 19.22.32 Paul Boddie wrote:
>
> But now I appear to experience a panic in sigma0 as it starts up, with the
> message...
>
> Warning: Sigma0 raised an exception --> HALT
[...]
> The EPC indeed appears to reference s
On Friday 14. July 2017 17.39.15 Sarah Hoffmann wrote:
>
> > The problem here is that the .cpload directive (operating on t9/$25)
> > doesn't have a known value of t9 to work with, it would seem.
> > Consequently, the calculations in the generated code work with a value
> > that isn't initialised.
Following up to myself again...
On Friday 14. July 2017 01.11.38 Paul Boddie wrote:
>
[Boot log on the CI20]
> MOE: Hello world
>
> And that is then the end of output.
So, I found I'd got ahead of myself here. Noting that the CI20 has 1GB RAM, I
changed the mk/platforms/
On Saturday 15. July 2017 00.11.58 Paul Boddie wrote:
>
> However, I'm not managing to actually see the example start. I get the
> following output:
>
> MOE: Hello world
> MOE: found 245048 KByte free memory
> MOE: found RAM from 1000 to 1000
> MOE: allocated
And some more...
On Sunday 16. July 2017 02.24.03 Paul Boddie wrote:
>
> But with the --l4re-dbg option set to "all", after this output...
>
> L4Re: load binary 'rom/hello'
> L4Re: Start server loop
>
> ...I notice this continuously recurring message
On Tuesday 18. July 2017 08.58.14 Sarah Hoffmann wrote:
>
> There is a bug in the Fiasco where it sends the wrong message size.
> Please apply the attached patch to Fiasco. Afterwards you should get
> more useful error messages in your L4 applications when it throws
> exceptions.
Yes, this fixes
On Tuesday 18. July 2017 16.56.08 Paul Boddie wrote:
>
> So, I applied the Fiasco patch and then looked at the above file, checking
> the objdump output for the l4re binary. With the patch applied, the page
> fault did not occur endlessly, and with a change to the above file simila
On Wednesday 19. July 2017 19.40.23 Paul Boddie wrote:
>
> It always seems to involve an address of 0x8, which seems rather bizarre.
> Again, I think I must be missing something fundamental and must only be
> seeing the consequences.
So, I adjusted the kernel code, putting back in
On Friday 21. July 2017 00.06.27 Adam Lackorzynski wrote:
> On Thu Jul 20, 2017 at 22:10:48 +0200, Paul Boddie wrote:
> >
> > While handling this page fault, there appears to be another page fault in
> > the kernel (at 0x80019c8c). This latter fault can't be handled (a
On Thursday 6. July 2017 01.05.58 Paul Boddie wrote:
> On Wednesday 5. July 2017 22.53.35 Matthias Lange wrote:
> >
> > That's not the whole story. Devices declared in e.g. hw_devices.io
> > describe physical (real) devices and their resources. The device handle
> &
On Friday 21. July 2017 20.19.09 Daniel (Xiaolong) Wang wrote:
>
> I’m testing L4re on a customized I.MX6 Solo-X-4 board. I found that the
> fiasco kernel (the simple hello world example built into an uimage) cannot
> be load by the U-boot. It shows “data abort". The reason I guess it is due
> to
Hello again,
Having looked at the l4vbus_gpio functions and struggled with providing
suitable devices, I decided to take the simpler approach and just ask for the
I/O memory of the devices and access that directly. However, this didn't prove
as straightforward as anticipated, either.
The aim w
On Tuesday 25. July 2017 23.47.26 Adam Lackorzynski wrote:
>
> There's no mechanism here that handles MMIO region sizes smaller than
> page size. Rather, l4io_request_iomem and friends to not handle
> addresses with offsets very well. Obviously I'll fix this.
> For now, please just use page-aligne
On Wednesday 11. October 2017 15.33.58 Manolis Ragkousis wrote:
>
> Finally I have a question, Are you accepting patches for L4 and L4Linux?
> I could make my git patches more presentable and send them here if you
> want, to be added to your upstream repo.
I would be interested to know about this
On Monday 16. October 2017 00.48.38 Adam Lackorzynski wrote:
> On Sat Oct 14, 2017 at 17:09:46 +0200, Paul Boddie wrote:
> > On Wednesday 11. October 2017 15.33.58 Manolis Ragkousis wrote:
> > > Finally I have a question, Are you accepting patches for L4 and
> > > L
Hello,
A quick reply as it is rather late...
On Monday 23. October 2017 00.55.53 Adam Lackorzynski wrote:
> On Mon Oct 16, 2017 at 15:35:22 +0200, Paul Boddie wrote:
> > On Monday 16. October 2017 00.48.38 Adam Lackorzynski wrote:
> > >
> > > You're talking a
Sorry for the delayed reply! Other things have been getting in the way, and
some mild illness certainly hasn't helped matters.
On Wednesday 25. October 2017 00.42.59 Adam Lackorzynski wrote:
>
> On Mon Oct 23, 2017 at 01:50:47 +0200, Paul Boddie wrote:
> >
> > I ha
On Wednesday 1. November 2017 00.38.23 Adam Lackorzynski wrote:
>
[Cache detail querying]
> I just modified the code to have a fixed value and that worked for me as
> a quick hack. I don't think the value will ever change for a particular
> CPU. But it's still a hack and there's a smarter way de
Hello,
I recently looked at the collection of patches accumulated when trying to get
the CI20 support to a functioning state, and I think I've brought them up to
date with the latest upstream repository version (r75). In doing so, I've also
tried to break them up into distinct parcels of functi
On Friday 15. December 2017 20.04.11 Paul Boddie wrote:
>
> I recently looked at the collection of patches accumulated when trying to
> get the CI20 support to a functioning state, and I think I've brought them
> up to date with the latest upstream repository version (r75). In
On Wednesday 20. December 2017 16.52.45 Paul Boddie wrote:
>
> However, another problem has emerged when trying to build L4Re. It appears
> that something changed between r72 and r73, and now, when I try and build
> L4Re, I get a linker error as described in the following Debia
Sorry to follow up on myself again...
On Thursday 21. December 2017 01.55.51 Paul Boddie wrote:
> On Wednesday 20. December 2017 16.52.45 Paul Boddie wrote:
> > However, another problem has emerged when trying to build L4Re. It
> > appears that something changed between r72 and r73
On Monday 8. January 2018 00.37.41 Adam Lackorzynski wrote:
>
> Is it ok if you have visibility("hidden") instead of internal?
No, it would seem that all other visibility types produce the same error. In
fact, the only thing that seems to prevent an error is to qualify the function
signature as
On Tuesday 9. January 2018 00.46.53 Adam Lackorzynski wrote:
> On Mon Jan 08, 2018 at 01:14:09 +0100, Paul Boddie wrote:
> >
> > I'm aiming to follow up with the binutils maintainers about this, but I
> > just wondered if any of this sounded problematic or familiar.
On Tuesday 9. January 2018 01.02.58 Paul Boddie wrote:
>
> So, I am assuming that the compiler gets confused by the freestanding
> assembly language definition of the function, and the object goes missing
> in some way that then leads to the error. Of course, the above introd
Hello,
More awkward news from Debian on i386! I was looking to build the "Linux
Usermode Platform" variant of Fiasco-OC on i386 (well, Pentium 4) and
encountered a couple of issues.
Firstly, "struct ucontext" is mentioned in src/kern/ux/usermode.cpp but has
been deprecated in favour of "uconte
As promised, my other error report...
With Fiasco-OC built, I concentrated on building L4Re for i386, but this led
to me encountering this rather frustrating error:
[l4util] ==> Linking to shared libl4util.so
/home/paulb/L4/UX-75/src/l4/mk/lib.mk:139: recipe for target 'libl4util.so'
failed
m
On Tuesday 30. January 2018 00.00.37 Adam Lackorzynski wrote:
> On Mon Jan 29, 2018 at 23:40:15 +0100, Paul Boddie wrote:
> >
> > [l4util] ==> Linking to shared libl4util.so
> >
> > /home/paulb/L4/UX-75/src/l4/mk/lib.mk:139: recipe for target
> &
On Tuesday 30. January 2018 00.32.30 Adam Lackorzynski wrote:
> On Mon Jan 29, 2018 at 22:36:34 +0100, Paul Boddie wrote:
> >
> > Secondly, linking of the kernel fails due to symbol conflicts between the
> > minilibc functionality and glibc:
> >
> > /usr/lib/g
On Wednesday 10. January 2018 00.48.03 Adam Lackorzynski wrote:
>
> Adding the .global to the asm block makes thread2 a global symbol which
> I'd like not to have here (contrary to L4UTIL_THREAD_FUNC). Just doing
> "static void thread2()" gives warnings because there is no
> implementation. Looks
On Monday 5. February 2018 00.02.47 Adam Lackorzynski wrote:
> On Fri Feb 02, 2018 at 16:45:13 +0100, Paul Boddie wrote:
> >
> > There seems to be a "kernel" UART, but the userspace seems to have the
> > configuration details in l4/pkg/bootstrap/server/src/platfo
On Monday 5. February 2018 01.43.55 Paul Boddie wrote:
>
> No, but the serial output isn't being done reliably in a physical sense, so
> that might be my fault rather than anything the software is doing. Is there
> some kind of assembly language file I should be looking at
Hello,
I've been trying to coerce L4Re and Fiasco.OC to work with the Ben NanoNote,
which is related to the MIPS Creator CI20 that is (mostly - see earlier
discussions) supported by this software. There are a few challenges involved,
such as avoiding MIPS32r2 instructions that the NanoNote's So
On Tuesday 6. March 2018 00.46.29 Adam Lackorzynski wrote:
>
> All what you write sounds good. In any case the eret must restore state
> including setting the right interrupt state. Are you getting timer
> interrupts when sigma0 shall run, or is there silence? Is ESC working to
> get into jdb?
Th
On Wednesday 7. March 2018 00.27.34 Adam Lackorzynski wrote:
>
> The asm code sets cp0_status upon exit which includes enabling
> interrupts. Are you sure you're not getting any timer interrupts when
> supposedly running inside sigma0? (Flipping some pixels in the timer
> handler...)
You beat to
On Wednesday 7. March 2018 01.22.46 Paul Boddie wrote:
>
> Currently, I have reason to believe that an exception occurs causing the
> sigma0 thread to terminate, but it's getting late and my debugging
> efficiency is suffering. I think that when the thread terminates, it has
>
Hello,
Accompanying my patches for the MIPS Creator CI20 (Ingenic JZ4780), I have
some patches that get Fiasco.OC booting on the Ben NanoNote (Ingenic JZ4720).
Currently, I can get a task running that shows some data on the screen. More
details about the Ben NanoNote can be found here:
http://
On Monday 12. March 2018 18.28.50 Paul Boddie wrote:
>
> Accompanying my patches for the MIPS Creator CI20 (Ingenic JZ4780), I have
> some patches that get Fiasco.OC booting on the Ben NanoNote (Ingenic
> JZ4720). Currently, I can get a task running that shows some data on the
&g
On Tuesday 13. March 2018 00.50.43 Paul Boddie wrote:
>
> Now all I have to do is to try and get fb-drv working and then I can run
> the spectrum example. But I've updated the patches in the unlikely case
> that anyone else is really interested.
>
> http://www.
As promised, I wrote up my experiences porting L4Re and Fiasco.OC to the Ben
NanoNote:
https://blogs.fsfe.org/pboddie/?p=2147
There are, in fact, nine articles describing the process, which I accept might
be a bit too much reading for the casual inquirer, especially as the narrative
wanders fr
Hello again,
I have been implementing input drivers for the keypad/keyboard provided by the
Ben NanoNote and Letux 400 notebook computer, and although I appear to have
implemented something that works (tested using specialised example code),
using the existing OMAP3 keypad code as a guide (in p
On Monday 23. April 2018 09.54.55 Matthias Lange wrote:
>
> On [18-04-2018 01:34], Paul Boddie wrote:
> >
> > http://blogs.fsfe.org/pboddie/?p=2175
> >
> > I hope that some of the information I have shared is useful to others and
> > perhaps encourages so
On Thursday 26. April 2018 08.23.21 Matthias Lange wrote:
>
> On [23-04-2018 12:23], Paul Boddie wrote:
> >
> > I don't have a GitHub account, but I did wonder whether the content of my
> > patches would be acceptable as currently formulated.
>
> There is at
Hello,
I have been busy writing libraries and programs for L4Re and recently had to
think about the size of the payloads I have been deploying. It appears that in
the build system, one can use MODE=shared to build dynamically-linked
programs, and there is a shared version of the hello example i
On Monday 14. May 2018 21.18.04 Adam Lackorzynski wrote:
>
> You can set LD_DEBUG=1 in the environment of your program to make the
> dynamic loader tell you something. LD_TRACE_LOADED_OBJECTS=1 might also
> be of help. Add enviroment variable settings after the program's
> cmdline: ...:start({ ...
On Monday 14. May 2018 21.25.40 Adam Lackorzynski wrote:
> On Mon Apr 23, 2018 at 01:28:59 +0200, Paul Boddie wrote:
> >
> > Is it possible to integrate my input drivers to things like Mag, which
> > seems to use input events, or to fbterminal or other things? I haven't
On Monday 14. May 2018 22.06.06 Paul Boddie wrote:
> On Monday 14. May 2018 21.18.04 Adam Lackorzynski wrote:
> > You can set LD_DEBUG=1 in the environment of your program to make the
> > dynamic loader tell you something. LD_TRACE_LOADED_OBJECTS=1 might also
> > be of
On Monday 14. May 2018 21.18.04 Adam Lackorzynski wrote:
>
> You can set LD_DEBUG=1 in the environment of your program to make the
> dynamic loader tell you something. LD_TRACE_LOADED_OBJECTS=1 might also
> be of help. Add enviroment variable settings after the program's
> cmdline: ...:start({ ...
On Wednesday 16. May 2018 00.37.32 Paul Boddie wrote:
>
> But I cannot figure out how to have the client create the interrupt and
> send it to the server, which would be a prerequisite for implementing the
> necessary interrupt mechanism for events, as far as I can tell. Presenting
&g
On Wednesday 23. May 2018 00.21.23 Paul Boddie wrote:
>
[L4_IPC_SEMSGCUT ("Cut send message") condition]
> I think I figured out what causes this particular error condition: the
> Registry_server class needs parameterising with Br_manager_hooks instead of
> the defa
On Wednesday 9. May 2018 01.22.29 Paul Boddie wrote:
>
> My aim will be to distill the patches to the essentials to support these
> systems in Fiasco.OC and L4Re. I think that some of the patch files more or
> less encapsulate these essential changes (those having the topics "
On Wednesday 13. June 2018 16.02.39 Alexander Boettcher wrote:
> Hi l4-hackers,
>
> we are happy to announce the release of Sculpt TC [0], a Genode based
> incarnation of a microkernel based operating system. It is the second
> out of four Sculpt OS releases planned in 2018 [1].
It is certainly i
On Friday 8. June 2018 00.32.04 Adam Lackorzynski wrote:
> On Sun May 20, 2018 at 00:47:02 +0200, Paul Boddie wrote:
> >
> > So, with the help of fbterminal (mentioned in my last message), I managed
> > to get some debugging information out of the loader:
> >
&g
On Friday 15. June 2018 00.17.49 Alexander Boettcher wrote:
> On 13.06.2018 17:30, Paul Boddie wrote:
> > That said, it has taken a while for me to navigate the L4Re documentation
> > in a half-way effective fashion, so I rather get the impression that I
> > might not
On Thursday 14. June 2018 15.38.33 Paul Boddie wrote:
>
> Is there some way of interpreting the "PFA" value or getting more
> information about where the exception really occurs?
Well, I got some off-list help/encouragement (many thanks!) and put in some
debugging stateme
On Sunday 17. June 2018 01.07.44 Paul Boddie wrote:
>
> With these details, and using objdump to dump all the programs and
> libraries, I discovered that it comes from the _ftext section of
> libld-l4.so:
>
> 2f5c: 8f998250lw t9,-32176(gp)
>
On Wednesday 27. June 2018 00.43.33 Paul Boddie wrote:
>
> Global entries:
>Address Access Initial Sym.Val. TypeNdx Name
> 00025f80 -32176(gp) FUNCUND __register_frame_info
>
> Here, we see the offending entry and what the program app
Hello,
I thought I'd try and get L4Re and the UX variant of Fiasco.OC working again.
Various errors with the actual compiler - not typical compilation errors -
have previously occurred, but system updates come along every so often and I
saw that new revisions of L4Re/Fiasco.OC have also arrived
On Friday 3. August 2018 15.36.50 Adam Lackorzynski wrote:
>
> On Fri Aug 03, 2018 at 00:26:45 +0200, Paul Boddie wrote:
> >
> > I know that the ldscripts have been changed, but I struggle to see how
> > the above relates to them or whether they are even involved in thi
On Friday 3. August 2018 15.49.56 Paul Boddie wrote:
> On Friday 3. August 2018 15.36.50 Adam Lackorzynski wrote:
> > On Fri Aug 03, 2018 at 00:26:45 +0200, Paul Boddie wrote:
> > > I know that the ldscripts have been changed, but I struggle to see how
> > > the above
On Saturday 4. August 2018 01.25.00 Paul Boddie wrote:
>
> A quick update, then. Quickly testing with revision 76 on Debian stable
> with binutils 2.28-5, I was able to launch the framebuffer-example in UX.
>
> However, updating to revision 80 under the same configuration, I get
On Tuesday 7. August 2018 23.00.25 Adam Lackorzynski wrote:
>
> Issue has been fixed by now. Was a mistake in the linkerscript
> where earlier ld versions did not complain.
Thanks once again for following up! This is possibly useful to know for other
reasons, too, of course. I'll try and confirm
On Tuesday 7. August 2018 23.47.44 Paul Boddie wrote:
> On Tuesday 7. August 2018 23.00.25 Adam Lackorzynski wrote:
> > Issue has been fixed by now. Was a mistake in the linkerscript
> > where earlier ld versions did not complain.
>
> Thanks once again for following up! This
Hello,
As this list can attest, I previously spent a bit of time diving into the way
dynamic linking is supported by L4Re to get shared mode programs working. This
turned out to have a relatively simple fix related to symbols employed by GCC-
generated code.
But during this exercise, I gained s
On Friday 14. September 2018 05.58.09 Andrew Warkentin wrote:
>
> Yes, I guess that would work, but you still have the problem of a
> rather complex language runtime being part of the TCB, which you don't
> get with an OS based on safer native code.
I am very fond of dynamic languages which usual
On Friday 14. September 2018 19.04.10 Andrew Warkentin wrote:
> On 9/14/18, Paul Boddie wrote:
> >
> > It is interesting to consider Nemesis, which evolved into Xen, in this
> > regard:
> >
> > https://en.wikipedia.org/wiki/Nemesis_(operating_system)
> &g
Sorry to hold off responding for so long!
On Monday 17. September 2018 16.54.14 Andrew Warkentin wrote:
>
> UX/RT will use a split architecture for its VFS, where read(),
> write(), and seek() will call kernel IPC APIs to communicate with the
> server directly, and all other filesystem-related fu
Hello,
I have been trying to implement a pager in L4Re where the pager employs a
memory region of limited size to satisfy map requests for a dataspace
occupying a larger virtual memory region. Upon receiving a map request, the
pager identifies the dimensions of the flexpage to be sent to the ta
On Monday 18. March 2019 08.35.56 Philipp Eppelt wrote:
>
> AFAIK, you cannot unmap a page during a page fault reply.
I had looked into this and couldn't see a way of returning items that would
provide the necessary information for unmapping previously mapped pages. I
imagine that one could spe
On Monday 18. March 2019 13.38.36 Philipp Eppelt wrote:
>
> Actually, there is a unmap flag which allows you to unmap all child
> mappings of a memory fpage. So assume you have three address spaces, A,
> B, and C, and A maps a page FP to B as FP' and B maps FP' to C as FP".
>
> So if B decides to
On Monday 18. March 2019 17.09.02 Paul Boddie wrote:
>
> Many thanks for showing me the appropriate mechanism!
And in case anyone casually reading the list is interested, I wrote up some of
my experiences investigating dataspaces and related concepts in L4Re:
http://blogs.fsfe.org/pbod
Hello,
I have been looking at trying out L4Linux in UX mode as a first step towards
its use on "native" Fiasco, and I seem to be experiencing a problem with
launching the Linux kernel itself.
I have followed the instructions from these pages:
https://l4linux.org/download.shtml
https://l4linux.
On Wednesday 3. April 2019 07.56.32 Adam Lackorzynski wrote:
>
> On Thu Mar 28, 2019 at 23:28:17 +0100, Paul Boddie wrote:
> >
> > In order to try and identify the problem, I used the following command:
> >
> > addr2line -e ~/L4/L4Linux/l4linux/mybuild/vmlinux 0
On Tuesday 28. May 2019 18.45.15 Lei Zhou wrote:
> HI,I'm looking for the information and procedure how to compile and
> deploy L4Re on Raspberry PI. Any feedbacks would be greatly appreciated!
I guess you should start here:
https://l4re.org/download.html
https://l4re.org/build.html
https:/
On Wednesday 29. May 2019 08.39.11 Matthias Lange wrote:
>
> On [28-05-2019 21:21], Lei Zhou wrote:
> > Thanks Paul for your prompt response. I will give it try and see how it
> > goes.Regards, Lei
> I just want to add two things to Paul's very good description.
>
> First, have you checked
On Wednesday 29. May 2019 15.20.01 Matthias Lange wrote:
>
> The issue we have with "standard" cross toolchains is the libgcc they are
> shipping. It is compiled for ARMv7 and contains instructions that are
> unknown / illegal on ARMv6k. The mean thing is, that our build system tells
> GCC via "-m
Hello,
In attempting to investigate building L4Re/Fiasco.OC for the Raspberry Pi
Zero, I encountered an unusual problem: unusual because, I suppose, most
people do not try and cross-build on architectures other than x86(-64).
When performing the initial L4Re build directory initialisation step.
On Wednesday 29. May 2019 18.27.03 Paul Boddie wrote:
>
> P.S. I have a selfish interest in following this as I could imagine also
> trying out L4Re on the Raspberry Pi at some point. I guess that the
> framebuffer isn't currently supported though.
Well, I got round to trying th
On Tuesday 11. June 2019 00.08.59 Adam Lackorzynski wrote:
>
> If it just reboots in the middle of a rather normal C function, then
> it's likely some instruction that has been generated there and not
> understood by the CPU. Could you maybe use u-boot as it shows a register
> dump when something
On Tuesday 11. June 2019 00.18.43 Paul Boddie wrote:
> On Tuesday 11. June 2019 00.08.59 Adam Lackorzynski wrote:
> > If it just reboots in the middle of a rather normal C function, then
> > it's likely some instruction that has been generated there and not
> > unders
On Tuesday 11. June 2019 23.32.43 Adam Lackorzynski wrote:
> On Tue Jun 11, 2019 at 02:00:00 +0200, Paul Boddie wrote:
> >
> > U-Boot> mmc dev 0
> > switch to partitions #0, OK
> > mmc0 is current device
> > U-Boot> fatload mmc 0:1 ${kernel_addr_r} hello.ra
On Thursday 13. June 2019 17.48.59 Adam Lackorzynski wrote:
> On Wed Jun 12, 2019 at 00:34:02 +0200, Paul Boddie wrote:
> >
> > Perhaps take a look at the following:
> >
> > http://www.boddie.org.uk/downloads/armv6_hello.elf
> > http://www.boddie.org.uk/downloa
On Monday 17. June 2019 00.08.27 Adam Lackorzynski wrote:
>
> I do not see anything particular special either. The floating point
> instructions are in the libc/*printf, so are not affected here.
> I could only continue with a binary search style of looking where it
> breaks, with "while(1);" as p
1 - 100 of 172 matches
Mail list logo
