headers
Tsai, Tung-Chieh | 2 Dec 16:12
Picon

building bootstrap

Dear All,

  I'm try  to port Fiasco to an ARM platform, and I'm confused by
the memory address settup in bootstrap package.
  What is the relationship between DEFAULT_RELOC_$(ARCH),
MOD_ADDR, and RAM_BASE ?
  In the setting of Integratorcp, they're :
    DEFAULT_RELOC_arm = 0x0140,0000
    RAM_BASE = 0x0
    MOD_ADDR = 0x0150,0000
(I wonder if this work on real integratorcp board ? Although QEMU
just put 2 memory with the same size on 0x0 and 0x8000,0000, is the
real one will remap all it's memory to 0x0 ?)

Because I see DEFAULT_RELOC_arm+RAM_BASE is used to be
 start address and in IMAGE_MODE, RAM_BASE+MOD_ADDR
is used to be _mod_addr, So I guess RAM_BASE manes where the
physical ram start, and DEFAULT_RELOC_arm, MOD_ADDR are
realative to RAM_BASE, which are used to control start address of
bootstrap image and specify where modules move to.

With these assumption, it will work unitl find_kip(), `fail to find kernel
info page.'  And then I found the address in regions are strange, only
address in bootstrap and multiboot info seems correct, others seems
irrelevant to RAM_BASE, looks like started at 0x0.

I guess there is some setting I miss. Could anyone give some advice about
it ?

Best Regards,
(Continue reading)

Permalink | Reply | 3 comments |
headers
Adam Lackorzynski | 2 Dec 22:52
Picon
Favicon

Re: building bootstrap

Hi,

On Tue Dec 02, 2008 at 23:12:56 +0800, Tsai, Tung-Chieh wrote:
>   I'm try  to port Fiasco to an ARM platform, and I'm confused by
> the memory address settup in bootstrap package.
>   What is the relationship between DEFAULT_RELOC_$(ARCH),
> MOD_ADDR, and RAM_BASE ?
>   In the setting of Integratorcp, they're :
>     DEFAULT_RELOC_arm = 0x0140,0000
>     RAM_BASE = 0x0
>     MOD_ADDR = 0x0150,0000
> (I wonder if this work on real integratorcp board ? Although QEMU
> just put 2 memory with the same size on 0x0 and 0x8000,0000, is the
> real one will remap all it's memory to 0x0 ?)

I never had a real integrator board myself, so I don't know.
Nevertheless it should not be problem to change the addresses.

> Because I see DEFAULT_RELOC_arm+RAM_BASE is used to be
>  start address and in IMAGE_MODE, RAM_BASE+MOD_ADDR
> is used to be _mod_addr, So I guess RAM_BASE manes where the
> physical ram start, and DEFAULT_RELOC_arm, MOD_ADDR are
> realative to RAM_BASE, which are used to control start address of
> bootstrap image and specify where modules move to.

It's exactly like this. RAM_BASE is the start of the RAM,
DEFAULT_RELOC_arm is the relative address (to RAM_BASE) where bootstrap
is linked to and MOD_ADDR is the relative address (to RAM_BASE) where
the modules will be moved to.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Adam Chang | 4 Dec 07:34
Picon

Problem with Building L4Linux-2.6

Dear all:

   I'm trying to build L4Linux ,so I followed the tutorial on this
website http://os.inf.tu-dresden.de/L4/LinuxOnL4/build-2.6.shtml
   but I have encountered some difficulties.

   First I got Fiasco, L4Env, L4Linux from SVN, and the following is
the steps that I tried to build L4Linux:
   1. make -C l4 O=/my-user-build-dir oldconfig
   2. make -C l4 O=/my-user-build-dir config
       unset Compilers and Tools  ---> Build doc directories
   3. cd l4
       make O=/my-user-build-dir
   4. Compile Fiasco
   5. Go to the l4linux-2.6 directory
       make menuconfig
       set L4 tree build directory
       unset some features like SMP, HPET, highmem, MTRR, MCE,
PARAVIRT, KEXEC, APM, HUGETLBFS
   6. make
       Then the following is a error message

       ERROR: CONFIG_VM86 must not be enabled.

     But I check the file in l4linux-2.6 directory ./arch/l4/Kconfig,
CONFIG_VM86 must be enabled, but the error message said that must be
enabled, so I was confused.

     Then ,I got Fiasco, L4Env, L4Linux from snapshot ,
http://os.inf.tu-dresden.de/opentc/download.xml
(Continue reading)

Permalink | Reply | 1 comment |
headers
Adam Lackorzynski | 5 Dec 00:09
Picon
Favicon

Re: Problem with Building L4Linux-2.6

Hi Adam,

On Thu Dec 04, 2008 at 14:34:57 +0800, Adam Chang wrote:
>    I'm trying to build L4Linux ,so I followed the tutorial on this
> website http://os.inf.tu-dresden.de/L4/LinuxOnL4/build-2.6.shtml
>    but I have encountered some difficulties.
> 
>    First I got Fiasco, L4Env, L4Linux from SVN, and the following is
> the steps that I tried to build L4Linux:
>    1. make -C l4 O=/my-user-build-dir oldconfig
>    2. make -C l4 O=/my-user-build-dir config
>        unset Compilers and Tools  ---> Build doc directories
>    3. cd l4
>        make O=/my-user-build-dir
>    4. Compile Fiasco
>    5. Go to the l4linux-2.6 directory
>        make menuconfig
>        set L4 tree build directory
>        unset some features like SMP, HPET, highmem, MTRR, MCE,
> PARAVIRT, KEXEC, APM, HUGETLBFS
>    6. make
>        Then the following is a error message
> 
>        ERROR: CONFIG_VM86 must not be enabled.
> 
>      But I check the file in l4linux-2.6 directory ./arch/l4/Kconfig,
> CONFIG_VM86 must be enabled, but the error message said that must be
> enabled, so I was confused.

Why does the Kconfig say it must be enabled? Its just enabled by
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ihor Kuz | 9 Dec 07:36
Picon
Favicon

CAmkES: component-based development for L4


NICTA is happy to announce the first open source release of CAmkES.

CAmkES provides an easier way to develop OKL4-based software and  
systems.

It is a component-based software development and runtime framework  
for OKL4, allowing microkernel-based systems to be modelled and built  
as a set of interacting software components. These software  
components have explicit interaction interfaces and a system design  
that explicitly details the connections between the components.

The development framework provides:
* a language to describe component interfaces, components, and whole  
component-based systems;
* a tool that processes these descriptions to combine programmer- 
provided component code with generated scaffolding and glue code to  
build a complete, bootable, system image;
* full integration in the OKL4 environment and build system.

Find out more about CAmkES, download it, and try it out here:

http://www.ertos.nicta.com.au/software/camkes/

On behalf of the CAmkES team,

Ihor

--

-- 
Ihor Kuz
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gabi Voiculescu | 10 Dec 13:54
Picon
Favicon

building a toolchian with hard float support

Hello.

I have to create a toolchain with hard fpu support for arm1176's VFPv2.

That's because, by looking at the ARM documentation I don't see how I can perform mathematic operations on the FPU (like FABSx, FADDx without using these mnemonics), (as it is the case for fpu load/store operations), so as far as see, I have to build a toolchain that recognized these mnemonics.

I dont' know where to start.

Has anybody used a script like crosstools for this? I hope by creating a new dat file with proper GCC and GLIBC argumets I could do the job myself, but I have no idea what would those arguments be or where to find them:
GCC += ?? --with-float=hard --fpu=vfpv2  --cpu=arm1176jzf ??
GLIBC += ??

Where can I find what gcc version might include support for my hard fpu? I tried the man pages in gcc-4.1.2 and gcc-3.4.4 without success and I can't figure out where to look for this on gnu.org.

Can you point me in the righ t direction to use.




_______________________________________________
l4-hackers mailing list
l4-hackers <at> os.inf.tu-dresden.de
http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Permalink | Reply | 2 comments |
headers
Adam Lackorzynski | 10 Dec 22:44
Picon
Favicon

Re: building a toolchian with hard float support

Hi,

On Wed Dec 10, 2008 at 04:54:25 -0800, Gabi Voiculescu wrote:
> I have to create a toolchain with hard fpu support for arm1176's VFPv2. 
> 
> That's because, by looking at the ARM documentation I don't see how I can perform
> mathematic operations on the FPU (like FABSx, FADDx without using these mnemonics), (as it is the case for
fpu load/store operations), so as far as see, I have to build a toolchain that recognized these mnemonics.
> 
> I dont' know where to start. 
> 
> Has anybody used a script like crosstools for this? I hope by creating a new dat file with proper GCC and
GLIBC argumets I could do the job myself, but I have no idea what would those arguments be or where to find them:
> GCC += ?? --with-float=hard --fpu=vfpv2  --cpu=arm1176jzf ??
> GLIBC += ??
> 
> Where can I find what gcc version might include support for my hard fpu? I tried the man pages in gcc-4.1.2
and gcc-3.4.4 without success and I can't figure out where to look for this on gnu.org.
>
> Can you point me in the right direction to use.

Codesourcery is known to have recent pre-built ARM compilers including
libc etc.:
http://www.codesourcery.com/gnu_toolchains/arm

Adam
--

-- 
Adam                 adam <at> os.inf.tu-dresden.de
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/
Permalink | Reply | 1 comment |
headers
Gabi Voiculescu | 11 Dec 10:03
Picon
Favicon

Re: building a toolchian with hard float support


Thank you, Adam, I did not think of that posibility.

I will give it a shot.

Gabi Voiculescu 

--- On Wed, 12/10/08, Adam Lackorzynski <adam <at> os.inf.tu-dresden.de> wrote:

> From: Adam Lackorzynski <adam <at> os.inf.tu-dresden.de>
> Subject: Re: building a toolchian with hard float support
> To: l4-hackers <at> os.inf.tu-dresden.de
> Date: Wednesday, December 10, 2008, 11:44 PM
> Hi,
> 
> On Wed Dec 10, 2008 at 04:54:25 -0800, Gabi Voiculescu
> wrote:
> > I have to create a toolchain with hard fpu support for
> arm1176's VFPv2. 
> > 
> > That's because, by looking at the ARM
> documentation I don't see how I can perform
> > mathematic operations on the FPU (like FABSx, FADDx
> without using these mnemonics), (as it is the case for fpu
> load/store operations), so as far as see, I have to build a
> toolchain that recognized these mnemonics.
> > 
> > I dont' know where to start. 
> > 
> > Has anybody used a script like crosstools for this? I
> hope by creating a new dat file with proper GCC and GLIBC
> argumets I could do the job myself, but I have no idea what
> would those arguments be or where to find them:
> > GCC += ?? --with-float=hard --fpu=vfpv2 
> --cpu=arm1176jzf ??
> > GLIBC += ??
> > 
> > Where can I find what gcc version might include
> support for my hard fpu? I tried the man pages in gcc-4.1.2
> and gcc-3.4.4 without success and I can't figure out
> where to look for this on gnu.org.
> >
> > Can you point me in the right direction to use.
> 
> Codesourcery is known to have recent pre-built ARM
> compilers including
> libc etc.:
> http://www.codesourcery.com/gnu_toolchains/arm
> 
> 
> 
> Adam
> -- 
> Adam                 adam <at> os.inf.tu-dresden.de
>   Lackorzynski         http://os.inf.tu-dresden.de/~adam/
> 
> _______________________________________________
> l4-hackers mailing list
> l4-hackers <at> os.inf.tu-dresden.de
> http://os.inf.tu-dresden.de/mailman/listinfo/l4-hackers
Permalink | Reply | 0 comments |
headers
Adam Chang | 11 Dec 19:21
Picon

Problem of running L4Linux

Dear all:
   I have succeeded in building L4Linux, and then I tried to boot
Fiasco and run L4Linux on VMware.When I tried to download your version
of GRUB bootloader on SVN, it said "At revision 422", not downloaded
something. So where can I download the source code of your version of
GRUB bootloader? And is there some documentation of running L4Linux on
Fiasco?
Thanks!

Best Regards.
Adam Chang

--

-- 
Adam Hung-Hsiang Chang
windbread <at> gmail.com
+886-987-335398
Wireless Networking and Embedded Systems Lab
Graduate Institute of Networking and Multimedia
National Taiwan University
Permalink | Reply | 5 comments |
headers
Adam Lackorzynski | 11 Dec 22:44
Picon
Favicon

Re: Problem of running L4Linux

Hi,

On Fri Dec 12, 2008 at 02:21:15 +0800, Adam Chang wrote:
>    I have succeeded in building L4Linux, and then I tried to boot
> Fiasco and run L4Linux on VMware.When I tried to download your version
> of GRUB bootloader on SVN, it said "At revision 422", not downloaded
> something. So where can I download the source code of your version of
> GRUB bootloader?

It's available as a patch with a bit of docu at
http://os.inf.tu-dresden.de/~adam/grub/
Latest version is this one:
http://os.inf.tu-dresden.de/~adam/grub/0.97/grub-0.97-os.7.diff.gz

> And is there some documentation of running L4Linux on Fiasco?

Like this?
http://os.inf.tu-dresden.de/L4/LinuxOnL4/use-2.6.shtml

Adam
--

-- 
Adam                 adam <at> os.inf.tu-dresden.de
  Lackorzynski         http://os.inf.tu-dresden.de/~adam/
Permalink | Reply | 4 comments |

Gmane