Hi,
Ronald G Minnich wrote:
On Fri, 2 Jun 2000, Matthew Sullivan wrote:
Just a thought - ignore me if it's daft - loadlin takes command line params and passes them to the kernel - why not use the same method...?
not daft as far as I can tell. I am getting too hung up on PARAM. The biggest problem is the kernel expects all this stuff to be on the empty_zero_page. linuxbios boot code doesn't know where in the kernel that is -- because linux setup code (arch/i386/boot/*.S) copies stuff from 0x90000 and other places to the empty_zero_page.
I am assuming you mean:
/* * This is set up by the setup-routine at boot-time */ #define EXT_MEM_K (*(unsigned short *)0x90002) #define DRIVE_INFO (*(struct drive_info *)0x90080) #define SCREEN_INFO (*(struct screen_info *)0x90000) #define RAMDISK_SIZE (*(unsigned short *)0x901F8) #define ORIG_ROOT_DEV (*(unsigned short *)0x901FC) #define AUX_DEVICE_INFO (*(unsigned char *)0x901FF)
extracted from: Loadlin:padjust.c - stolen from: arch/i386/boot/compressed/misc.c
.... you cannot use these addresses...?
/ Mat
PS I have been following the list but only loosly and have not been able to take a look at the code (or even use my dev machine) for a couple of months now - so I maybe way off course... feel free to point me in the right direction :-)
-- Yours
Matthew
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- More Computer Terminology -=-=-=-=-=-=-=-=-=-=-=-=- Cursor: A computer user who is abusive to his machine.