*sigh*
---------- Forwarded message ---------- From: spooq spoooq@gmail.com Date: Apr 11, 2006 11:12 PM Subject: Re: attempted fix for asm in oskit cpuid.c To: Ronald Aigner ra3@os.inf.tu-dresden.de
I see dietlibc's printf is not given a good review on http://www.and.org/vstr/printf_comparison...
On 4/11/06, spooq spoooq@gmail.com wrote:
Ok, I'll start using one of those. Is there any real difference between the two?
Id also like to know what would need to be done to port L4Env to a new arm-based arch, eg video card driver (not supported by existing linux driver), touchscreen, mmu. Is there a list somewhere of interfaces that need to be implemented?
btw, just spooq is fine
-- spooq
On 4/11/06, Ronald Aigner ra3@os.inf.tu-dresden.de wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Hello spoo(o)q,
spooq wrote on 10.04.2006 19:36 this:
I tried to fix some errors in cpuid.c ... wouldnt rely on it, my asms not very good and I havent tested it beyond seeing that it compiles. Basically it just makes the asm respect gcc using the ebx as a pic reg. Not sure about the \n\t stuff, it made it work tho.
Nice job. However, oskit is no longer supported as a libc for L4Env applications. Please use either dietlibc or uclibc.
Thanks, keep it up. Ron.
Mit freundlichen Gruessen / with regards ra3 @ inf.tu-dresden.de http://os.inf.tu-dresden.de/~ra3/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux)
iD8DBQFEPCGivCdOf9l7ipgRAv9RAKCEMCFLEx1o0ehBLG+f5J+6I9/dIgCgwjdV SzC8KfKBWcPvexF8A8vzadw= =1wJw -----END PGP SIGNATURE-----
On Tue Apr 11, 2006 at 23:14:08 +0100, spooq wrote:
On 4/11/06, spooq spoooq@gmail.com wrote:
Ok, I'll start using one of those. Is there any real difference between the two?
From a users point of view not really. They both work equally well.
Id also like to know what would need to be done to port L4Env to a new arm-based arch, eg video card driver (not supported by existing linux driver), touchscreen, mmu. Is there a list somewhere of interfaces that need to be implemented?
There's no such list. For a new platform you basically have to add or adapt interrupt, timer, mmu, uart etc. drivers in the kernel. User space needs to be taught some platform information but that's it basically. A video card driver is some user thing. I have l4con and dope running but that's it when one doesn't have keyboard/mouse. And touchscreen sounds like there's a special application anyway.
Adam
Adam Lackorzynski wrote:
On Tue Apr 11, 2006 at 23:14:08 +0100, spooq wrote:
[uclibc vs. dietlibc]
Ok, I'll start using one of those. Is there any real difference between the two?
From a users point of view not really. They both work equally well.
One more comment on this: We currently use both version internally in our group, but recently decided to switch to uclibc because of licencing issues (GPL vs. LGPL).
So, in the long run you should bet on uclibc here.
Cheers, Martin
l4-hackers@os.inf.tu-dresden.de