From ffjeld at common-lisp.net  Thu Mar  6 19:26:50 2008
From: ffjeld at common-lisp.net (Frode Vatvedt Fjeld)
Date: 06 Mar 2008 20:26:50 +0100
Subject: [movitz-devel] New assembler
Message-ID: <2hr6enirgl.fsf@vserver.cs.uit.no>

I've been writing a new assembler, which is now integrated with
movitz. This replaces the assembler in the ia-x86 package and CVS
module, so this no longer has to be loaded at all. The new assembler
is considerably leaner and meaner, and I think more than doubles
compilation speed.

The new assembler resides in movitz/asm.lisp (architecture independent
code) and movitz/asm-x86.lisp. The latter implements (dis)assembly of
x86 instructions in 16, 32, and 64-bit mode. 64-bit mode has not been
used or tested much yet, and probably contains some bugs. It should be
possible to hook in some asm-foo.lisp, although to get movitz going
you'd need a new compiler-foo.lisp etc. also.

-- 
Frode Vatvedt Fjeld



From mbealby at gmail.com  Thu Mar  6 20:32:27 2008
From: mbealby at gmail.com (Martin Bealby)
Date: Thu, 06 Mar 2008 20:32:27 +0000
Subject: [movitz-devel] Re: Partition Parsing
In-Reply-To: <Pine.LNX.4.64.0803062100190.23250@Psilocybe.Update.UU.SE>
	(Andreas Davour's message of "Thu\,
	6 Mar 2008 21\:02\:27 +0100 \(CET\)")
References: <87ablra79i.fsf@cerebellum.bealbywm.plus.com>
	<Pine.LNX.4.64.0803062100190.23250@Psilocybe.Update.UU.SE>
Message-ID: <87ejanr3tw.fsf@tombstone.bealbywm.plus.com>

Andreas Davour <ante at Update.UU.SE> writes:

> A question. How is the partition table supposed to look like? I've been trying
> to read a partition table with the new functions and if there is a table at
> all, they all look the same even though the partition sizes and details should
> be different. Am I just showing my ignorance of how partition tables are
> supposed to work?

The ATA code supports four separate drives (master and slave for two
controllers) and 'caches' the partitions in *ata-partitions*.

For example, to read the partition of the first master drive ('-hda'
parameter in qemu) call (ata-read-partition-table (+ata-controller0+ 0))

This will read the partition table and store it in memory.  Partition
tables can contain up to four primary partitions (this code doesn't
currently support extended partitions) and these are stored in a
list. Effectively, *ata-partitions* should be a list of lists of lists
:)

Once the cache is filled, calling ata-get-partition-data with the
controller number (0 or 1), drive number (0 for master, 1 for slave) and
partition number (0 to 3) will return the raw hex partition description.

This is designed to be passed to the other partition functions such as
ata-partition-active-p, ata-partition-type, ata-partition-start-offset
and ata-partition-size to retrieve useful data.

For more information regarding partition tables themselves please see:
http://www.osdev.org/wiki/Partition_Table

Hope this helps,
Martin


From ffjeld at common-lisp.net  Fri Mar 21 12:52:02 2008
From: ffjeld at common-lisp.net (Frode Vatvedt Fjeld)
Date: 21 Mar 2008 13:52:02 +0100
Subject: [movitz-devel] Macros in Movitz run-time, etc.
Message-ID: <2hfxuktf2l.fsf@vserver.cs.uit.no>

I'd just like to mention that I've recently added macros to the movitz
run-time (and eval). That is, macros in general should work as you
expect at the REPL, and the "macro-function" and "macroexpand"
functions should work according to spec. Notable macros that work are
do, dotimes, dolist, and destructuring-bind. Notable not-working-yet
macros are loop, defclass, and defmethod (i.e. macros that require
extensive machinery beyond the syntax layer).

The macro-expanders are compiled (at create-image time, like normal
functions). This increases the time and output size of create-image
somewhat, but the default kernel still clocks in well below the size
of a floppy image (1.44 MB).

Furthermmore, a number of special operators have been added/improved
in the run-time eval. I expect eval to be reasonably complete soonish.

Finally, the compiling of macros triggered a few compiler bugs that
have now been weeded out (also increasing compiler speed).

-- 
Frode Vatvedt Fjeld



From happyarch at gmail.com  Sun Mar 23 03:28:58 2008
From: happyarch at gmail.com (l l)
Date: Sun, 23 Mar 2008 12:28:58 +0900
Subject: [movitz-devel] movitz on usb?
Message-ID: <768a59a70803222028o73daa185w25d2fa41169d81b0@mail.gmail.com>

Hi,

Can i install movitz on usb memory stick?

TIA


From ffjeld at common-lisp.net  Sun Mar 23 11:49:18 2008
From: ffjeld at common-lisp.net (Frode Vatvedt Fjeld)
Date: 23 Mar 2008 12:49:18 +0100
Subject: [movitz-devel] Re: movitz on usb?
References: <768a59a70803222028o73daa185w25d2fa41169d81b0@mail.gmail.com>
Message-ID: <2h8x09u0ch.fsf@vserver.cs.uit.no>

"l l" <happyarch at gmail.com> writes:

> Can i install movitz on usb memory stick?

If you can get GRUB to boot off of it, it should work. Movitz is
"multiboot" compliant.

-- 
Frode Vatvedt Fjeld



From happyarch at gmail.com  Sun Mar 23 13:54:29 2008
From: happyarch at gmail.com (l l)
Date: Sun, 23 Mar 2008 22:54:29 +0900
Subject: [movitz-devel] Re: movitz on usb?
In-Reply-To: <2h8x09u0ch.fsf@vserver.cs.uit.no>
References: <768a59a70803222028o73daa185w25d2fa41169d81b0@mail.gmail.com>
	<2h8x09u0ch.fsf@vserver.cs.uit.no>
Message-ID: <768a59a70803230654n24648b70xf8e4f84319c7fe74@mail.gmail.com>

Thanks for the reply.

I think i could boot movitz
http://forums.fedoraforum.org/forum/showthread.php?t=163346

TIA

23 Mar 2008 12:49:18 +0100, Frode Vatvedt Fjeld <ffjeld at common-lisp.net>:
> "l l" <happyarch at gmail.com> writes:
>
>  > Can i install movitz on usb memory stick?
>
>
> If you can get GRUB to boot off of it, it should work. Movitz is
>  "multiboot" compliant.
>
>
>  --
>  Frode Vatvedt Fjeld
>
>  _______________________________________________
>  movitz-devel site list
>  movitz-devel at common-lisp.net
>  http://common-lisp.net/mailman/listinfo/movitz-devel
>


From yoni at rabkins.net  Sun Mar 30 20:08:38 2008
From: yoni at rabkins.net (Yoni Rabkin)
Date: Sun, 30 Mar 2008 23:08:38 +0300
Subject: [movitz-devel] SBCL directory hack
Message-ID: <87myog560p.fsf@rabkins.net>


I use these two patches as a shortcut to giving `create-image' the correct directory.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: add-global-variable-lpd-to-movitz.patch
Type: text/x-diff
Size: 552 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/movitz-devel/attachments/20080330/a8b07a64/attachment.patch>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: bind-default-pathname-defaults-during-make-movitz-image.patch
Type: text/x-diff
Size: 997 bytes
Desc: not available
URL: <https://mailman.common-lisp.net/pipermail/movitz-devel/attachments/20080330/a8b07a64/attachment-0001.patch>
-------------- next part --------------

-- 
   "Cut your own wood and it will warm you twice"