**** BEGIN LOGGING AT Tue Apr 09 02:59:58 2013
Apr 09 06:28:07 <txor> Hi!
Apr 09 06:28:16 <txor> lindi-, What is FR?
Apr 09 07:07:19 <txor> A simple question: What implications have that I/O registers are mapped along the memory address space? Does the OS needs to deal with this?
Apr 09 08:48:27 <lindi-> txor: freerunner
Apr 09 08:49:42 <TAsn> freerunning!
Apr 09 09:10:47 <txor> lindi-, Ah! It's a proof of concept for porting a WiFi driver to eCos.
Apr 09 09:11:13 <lindi-> txor: does eCos already run under qemu?
Apr 09 09:15:22 <txor> lindi-, Yes, it runs under qemu. A x86 version.
Apr 09 09:15:33 <lindi-> txor: but not ARM qemu?
Apr 09 09:15:59 <txor> I didn't tried it.
Apr 09 09:16:22 <lindi-> sounds like a very bad idea to try to port something to ARM without first verifying everything in an emulator
Apr 09 09:22:54 <txor> lindi-, really? ^^ Maybe you are right, but in eCos exists support for s3c2440 board that is a cousin of s3c2442b from FR. I get eCos running, but some things doesn't work...
Apr 09 09:23:53 <txor> Now I am trying to configure MMU in a right way.
Apr 09 09:24:44 <txor> lindi-, I am adadpting the s3c2440 template.
Apr 09 09:32:31 <PaulFertser> txor: sometimes it's easier to work with an emulator, sometimes it's harder, sometimes it's the same, it all depends.
Apr 09 09:32:48 <PaulFertser> txor: but if it's running already, why do you want to mess with the mmu?
Apr 09 09:33:59 <gena2x|work> wifi in qemu? hm...
Apr 09 09:34:47 <txor> PaulFertser, I don't need to page the memory at OS level? What about the I/O registers spreaded over all the memory?
Apr 09 09:34:50 <PaulFertser> gena2x|work: bringing up other parts might be easier with qemu, i'm not sure.
Apr 09 09:35:16 <PaulFertser> txor: are you writing a userspace driver?
Apr 09 09:35:39 <PaulFertser> txor: isn't eCos providing some abstraction for memory mapping already?
Apr 09 09:38:07 <txor> PaulFertser, I think it provides a memory mapping mechanisms but the ones I am using are designed for the other board and I think that they are not matching exactly with the actual memory layout.
Apr 09 09:38:32 <txor> PaulFertser, ar6000 and its dependencies lives in userspace?
Apr 09 09:39:04 <txor> PaulFertser, Anyway I will need to run some userspace programs, like tests and demo ones.
Apr 09 09:39:54 <PaulFertser> txor: with the kernel we use ar6000 is a kernel driver of course.
Apr 09 09:40:10 <PaulFertser> txor: normal userspace apps do not care about memory mappings and mmu.
Apr 09 09:43:36 <txor> PaulFertser, Maybe I am getting wrong with mmu... Maybe what I want is a reasonable memory layout.
Apr 09 09:44:27 <PaulFertser> txor: what is your current memory layout and why you think it's unreasonable? :)
Apr 09 09:44:32 <txor> What about of RAM and ROM sections for an embedded? Where its the rightest place to put it?
Apr 09 09:46:16 <txor> PaulFertser, Hehe I really don't know, for now I am putting the ROM section at 0x33f80000, RAM was already in 0x0...
Apr 09 09:48:34 <txor> PaulFertser, One thing that I does not understand yet: Doesn't the memory mapped registers (like UCON2 0x50008004) will be miswrited if I use that region of memory?
Apr 09 09:55:43 <PaulFertser> txor: your kernel should provide you means to properly and easily access physical addresses.
Apr 09 09:59:23 <txor> Ok, thanks all!
Apr 09 10:35:45 <GNUtoo-x60> JaMa, lastest staging fails to launch the wizard
**** ENDING LOGGING AT Wed Apr 10 02:59:58 2013