Re: kexec and frame buffer

2005-08-12 Thread Eric W. Biederman
Luca Falavigna <[EMAIL PROTECTED]> writes: > Luca Falavigna ha scritto: >> Eric W. Biederman ha scritto: >> Anyway I believe you also want to look at include/linux/tty.h at the screen_info structure. I believe that is where all of that information is passed. >> >> I noticed. Maybe

Re: kexec and frame buffer

2005-08-12 Thread Luca Falavigna
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Luca Falavigna ha scritto: > Eric W. Biederman ha scritto: > >>>Anyway I believe you also want to look at include/linux/tty.h >>>at the screen_info structure. I believe that is where >>>all of that information is passed. > > I noticed. Maybe if we

Re: kexec and frame buffer

2005-08-12 Thread Luca Falavigna
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Luca Falavigna ha scritto: Eric W. Biederman ha scritto: Anyway I believe you also want to look at include/linux/tty.h at the screen_info structure. I believe that is where all of that information is passed. I noticed. Maybe if we fill struct

Re: kexec and frame buffer

2005-08-12 Thread Eric W. Biederman
Luca Falavigna [EMAIL PROTECTED] writes: Luca Falavigna ha scritto: Eric W. Biederman ha scritto: Anyway I believe you also want to look at include/linux/tty.h at the screen_info structure. I believe that is where all of that information is passed. I noticed. Maybe if we fill struct

Re: kexec and frame buffer

2005-08-07 Thread Luca Falavigna
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eric W. Biederman ha scritto: > Anyway I believe you also want to look at include/linux/tty.h > at the screen_info structure. I believe that is where > all of that information is passed. I noticed. Maybe if we fill struct x86_linux_param_header with

Re: kexec and frame buffer

2005-08-07 Thread Luca Falavigna
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eric W. Biederman ha scritto: Anyway I believe you also want to look at include/linux/tty.h at the screen_info structure. I believe that is where all of that information is passed. I noticed. Maybe if we fill struct x86_linux_param_header with

Re: kexec and frame buffer

2005-08-06 Thread Eric W. Biederman
Luca Falavigna <[EMAIL PROTECTED]> writes: > Eric W. Biederman ha scritto: >> So without doing passing --real-mode the vga= parameter currently >> cannot work. The vga= parameter is processed by vga.S which >> make BIOS calls and we bypass all of the BIOS calls. > Actually that file is video.S

Re: kexec and frame buffer

2005-08-06 Thread Luca Falavigna
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eric W. Biederman ha scritto: > So without doing passing --real-mode the vga= parameter currently > cannot work. The vga= parameter is processed by vga.S which > make BIOS calls and we bypass all of the BIOS calls. Actually that file is video.S > So

Re: kexec and frame buffer

2005-08-06 Thread Luca Falavigna
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Eric W. Biederman ha scritto: So without doing passing --real-mode the vga= parameter currently cannot work. The vga= parameter is processed by vga.S which make BIOS calls and we bypass all of the BIOS calls. Actually that file is video.S So you

Re: kexec and frame buffer

2005-08-06 Thread Eric W. Biederman
Luca Falavigna [EMAIL PROTECTED] writes: Eric W. Biederman ha scritto: So without doing passing --real-mode the vga= parameter currently cannot work. The vga= parameter is processed by vga.S which make BIOS calls and we bypass all of the BIOS calls. Actually that file is video.S Oops.

Re: kexec and frame buffer

2005-08-04 Thread Eric W. Biederman
Luca Falavigna <[EMAIL PROTECTED]> writes: > I made three experiments regarding kexec with frame buffer support (vesafb). > For > each of them I gathered dmesg messages from original and relocated kernel, in > order to easily compare them later on. These tests were run on a

kexec and frame buffer

2005-08-04 Thread Luca Falavigna
I made three experiments regarding kexec with frame buffer support (vesafb). For each of them I gathered dmesg messages from original and relocated kernel, in order to easily compare them later on. These tests were run on a virtual machine in order to provide the same environment for each

kexec and frame buffer

2005-08-04 Thread Luca Falavigna
I made three experiments regarding kexec with frame buffer support (vesafb). For each of them I gathered dmesg messages from original and relocated kernel, in order to easily compare them later on. These tests were run on a virtual machine in order to provide the same environment for each

Re: kexec and frame buffer

2005-08-04 Thread Eric W. Biederman
Luca Falavigna [EMAIL PROTECTED] writes: I made three experiments regarding kexec with frame buffer support (vesafb). For each of them I gathered dmesg messages from original and relocated kernel, in order to easily compare them later on. These tests were run on a virtual machine in order