Menu
▾
▴
elysium-cvs
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
(10) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|---|
|
From: Kasper V. L. <ve...@da...> - 2000-02-22 10:06:17
|
Hi, I've commited the kernel patch done by Adam - basic PCT support is now available. /Kasper ------------------------------------------------------------------- Kasper Verdich Lund, Computer Science Department, Aarhus University Office: 34P.218 | Phone: (+45) 8942 5680 Email: ve...@da... | WWW: http://www.daimi.au.dk/~verdich |
|
From: Kasper V. L. <ve...@da...> - 2000-02-16 18:39:23
|
Hi guys, I've added user-level IRQ handling stuff to the Elysium kernel. The 'init' module shows how to hook the interrupt generated from an IRQ - in this particular case IRQ 1 (keyboard) - and I'll be implementing a keyboard driver in a few days. Before this week is over we'll have a primitive shell up and running :-) We still need to work on PCT (protected control transfer) - anyone? /Kasper |
|
From: Kasper V. L. <ve...@da...> - 2000-02-16 07:38:04
|
Hi guys,
I've imported the initial source code for the init process. Browse the
CVS repository to find it. It doesn't do anything useful - yet - but it
shows you how to write code on top of the Elysium kernel. If you build a
GRUB bootdisk and specify the following:
kernel= (fd0)/elysium.kernel.tgz
module= (fd0)/elysium.init.tgz
and copy the appropriate files (elysium.{init,kernel}.tgz) from the
right directories (/{kernel,init}/bin) you'll have something similar to
the bootdisk image available from the Elysium web site. You should know
that on the bootdisk image I've built two different init processes to
illustrate that multitasking indeed works.
/Kasper
|
|
From: Kasper V. L. <ve...@da...> - 2000-02-04 22:17:15
|
Things are really working out well tonight :-) ... I've managed to add a (primitive) scheduler to the Elysium kernel. It's driven by the timer interrupt (IRQ 0), and seems to work. I'll do more extensive testing later. /Kasper |
|
From: Kasper V. L. <ve...@da...> - 2000-02-04 18:59:06
|
I've added some basic support for processes. Have a look at the files
process.{c,h}.
/Kasper
|
|
From: Kasper V. L. <ve...@da...> - 2000-02-04 14:26:27
|
I've added support for paging to the Elysium kernel. The function 'memory_init()' now initializes a base page directory, and CR3 is set to point to this page directory before paging is finally enabled. Notice that writing to read-only pages - even from kernel mode - will cause page faults. /Kasper |
|
From: Kasper V. L. <ve...@da...> - 2000-02-04 13:25:04
|
I've renamed pmap.{c,h} to memory.{c,h}. The 'memory' files will contain
all routines for safely multiplexing the physical memory. Likewise I
expect to put all routines for cpu multiplexing - primarily scheduling -
in the files cpu.{c,h}. All smp code should go in smp.{c,h} and not in
cpu.{c,h}.
/Kasper
|
|
From: Kasper V. L. <ve...@da...> - 2000-02-03 21:22:11
|
I've added some pmap (physical map) routines to the kernel. These are: pmalloc() - allocate a page pfree() - free a page pmap_init() - initialise the pmap The pmap support is by no means done yet, since the pages cannot be protected. Furthermore it might be useful to have several free lists - e.g. one for memory below 16mb (for DMA), one for memory between 16mb and 256mb (for kernel/application use), and one for memory above 256mb (for application use). /Kasper |
|
From: Kasper V. L. <ve...@da...> - 2000-02-03 09:52:23
|
I've improved the multiboot_validate() code - reducing the generated code of the kernel by 48 bytes. Also I've added a new header file: align.h, which is useful for aligning (up or down) values to a specified alignment. /Kasper |
|
From: Kasper V. L. <ve...@da...> - 2000-02-01 20:23:56
|
I've added debug print routines to the kernel. Uncomment a line in kernel/GNUmakefile to compile with these debug routines. Kernel code size with debug routines = 3598 bytes. Kernel code size without debug routines = 2680 bytes. /Kasper |
