RE: [Xen-devel] vesafb

["Kaushik Barde" <Kaushik_Barde@xxxxxxxxxxx>]

I Agree with Kier. 

And from our experience (Phoenix) BIOS reserved areas usually aren't
clobbered (except for a vendor specific BIOS/system customizations)

I am also not sure about why can't we create Dom0 interface changes?

Like I presented in my email earlier, is following ok?

////
void __init __start_xen(multiboot_info_t *mbi)
{
    char __cmdline[] = "", *cmdline = __cmdline;

   .....

/* Create initial domain 0. */
    dom0 = domain_create(0, 0);
    if ( (dom0 == NULL) || (alloc_vcpu(dom0, 0, 0) == NULL) )
        panic("Error creating domain 0\n");

    dom0->is_privileged = 1;

    /* Post-create hook sets security label. */
    acm_post_domain0_create(dom0->domain_id);

    /* Grab the DOM0 command line. */
    cmdline = (char *)(mod[0].string ? __va(mod[0].string) : NULL);
    if ( cmdline != NULL )
        {
         parse_vga_commandline(..);
        }
   .....
}

void parse_vga_commandline(..)
{
        init_vga_mode();

}

void Init_vga_mode()
{
        // your code..
        // detect the card, query BIOS and sets up best possible mode
}
////



-----Original Message-----
From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Keir Fraser
Sent: Tuesday, May 08, 2007 3:39 AM
To: Jan Beulich
Cc: ron minnich; Ian Pratt; xen-devel@xxxxxxxxxxxxxxxxxxx; Jayant
Mangalampalli
Subject: Re: [Xen-devel] vesafb

On 8/5/07 10:56, "Jan Beulich" <jbeulich@xxxxxxxxxx> wrote:

>> 1. Doing it from dom0 would require interface changes we don't have
yet
> 
> And in my opinion we never should (based on bad experience in NetWare
with
> switching back to real mode).

That's kind of surprising. As long as the BIOS code and data areas
haven't
been clobbered I would expect no problems. Are interrupts and NMIs a
hassle?

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel