Hi again, I've been constantly uploading changes into the git repositoy the past days.
Now the second stage boot loader that gets loaded before the kernel when using MkLinux Booter finally modifies the flat device tree to pass ramdisk parameters, kernel command line, memory and display device configuration to the kernel. No more hacking inside the kernel that way. Also there are two new build targets: MachKernel and MachKernel.initrd. Using these two one can build exculsively Mach Kernel images, with ramdisk attached or without. The process of building Mach Kernel images is now integrated into the standard kernel image building process - although a rather hacky way. However until now neither booting via ramdisk nor via hard disk works on my PB1400. In the hard disk case it might be that my old Debian Sarge installation isn't compatible with linux 2.6.30 but in the ramdisk case I get a DATA ACCESS exception, related to kernel memory paging. Some tips regarding these errors? I Could need some help with that! Yet to do is choosing between device trees inside the second stage boot loader according to the machine type (Gestalt ID). Cheers, Tobias ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Nubus-pmac-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nubus-pmac-users
