Hi
The problem is solved : I upgraded gcc 4.2 and binutils 2.18. I also
had to completely purge build directory of fiasco. ovlscreen_drv works
as no assembler ipc shortcut. Thank you Adam for your help.
Regards
Marc
___
l4-hackers mailing list
l4-hacke
Hi Marc,
On Wed Nov 21, 2007 at 14:38:54 +0100, Marc CHALAND wrote:
> 2007/11/21, Adam Lackorzynski <[EMAIL PROTECTED]>:
> >
> > Are you using 2k or 4k stack in Fiasco? If 2k, try 4k.
>
> I've tried 4k without success. Should I compile all l4env ?
No, this is just a kernel matter.
> > Also, the
On Wed Nov 21, 2007 at 10:31:47 +0100, Marc CHALAND wrote:
> 2007/11/18, Adam Lackorzynski <[EMAIL PROTECTED]>:
> >
> > You did use gcc-4.1.1-something, right? Could you use some recent
> > gcc-4.2 and retest? That would be interesting.
>
> I tried gcc-4.2.2 and result is the same.
> I also tried
2007/11/18, Adam Lackorzynski <[EMAIL PROTECTED]>:
>
> You did use gcc-4.1.1-something, right? Could you use some recent
> gcc-4.2 and retest? That would be interesting.
I tried gcc-4.2.2 and result is the same.
I also tried to push some 0xdeadbeef into the stack of calling ipc
(code of l4_ipc_cal
On Thu Nov 15, 2007 at 09:54:25 +0100, Marc CHALAND wrote:
> Some news about my problem.
>
> Fiasco catches an exception (it seems to be a page fault) into
> Thread::do_ipc function (do_ipc + 0xbd). As there are many inline
> functions, I decided to remove INLINE option to fiasco kernel. And...
>
Some news about my problem.
Fiasco catches an exception (it seems to be a page fault) into
Thread::do_ipc function (do_ipc + 0xbd). As there are many inline
functions, I decided to remove INLINE option to fiasco kernel. And...
no more exception :/.
Now ovlscreen driver works perfectly.
It seems t
2007/11/8, Adam Lackorzynski <[EMAIL PROTECTED]>:
>
> What I'd like to have is a setup that I can run in Qemu. I know it's not
> easy with X in a ramdisk etc but maybe you have this already?
Sorry, we don't have a Qemu setup. However, we plan to do one...
Marc
___
On Thu Nov 08, 2007 at 12:21:53 +0100, Marc CHALAND wrote:
> 2007/11/7, Adam Lackorzynski <[EMAIL PROTECTED]>:
> >
> > I've just tried to reproduce something like this but I had no 'luck'. I
> > also do not understand how the code path can be taken with the given
> > values. I suppose your sources
2007/11/7, Adam Lackorzynski <[EMAIL PROTECTED]>:
>
> I've just tried to reproduce something like this but I had no 'luck'. I
> also do not understand how the code path can be taken with the given
> values. I suppose your sources are up to date? Is this reliably
> reproducible?
Yes, I have latest
Hi Marc,
On Wed Nov 07, 2007 at 11:05:49 +0100, Marc CHALAND wrote:
> With Nitpicker, I try to start X server with ovlscreen driver. After a
> little while, I get the following message :
> l4lx| l4x_hybrid_return: Invalid hybrid return for 23.00 (0x0688d570, e,
> 0,
> l4lx: -1, f0020d5d)
Hi,
With Nitpicker, I try to start X server with ovlscreen driver. After a
little while, I get the following message :
l4lx| l4x_hybrid_return: Invalid hybrid return for 23.00 (0x0688d570, e, 0,
l4lx: -1, f0020d5d)!
l4lx| l4x_hybrid_return: Currently running: 00.00
After some debuggi
11 matches
Mail list logo