[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m1abwetgkn.fsf@ebiederm.dsl.xmission.com>
Date: Wed, 09 May 2007 04:52:08 -0600
From: ebiederm@...ssion.com (Eric W. Biederman)
To: "H. Peter Anvin" <hpa@...or.com>
Cc: yhlu <yhlu.kernel@...il.com>,
Jeremy Fitzhardinge <jeremy@...p.org>, vgoyal@...ibm.com,
Gerd Hoffmann <kraxel@...hat.com>,
Jeff Garzik <jeff@...zik.org>, patches@...-64.org,
linux-kernel@...r.kernel.org,
virtualization <virtualization@...ts.linux-foundation.org>,
Rusty Russell <rusty@...tcorp.com.au>, Andi Kleen <ak@...e.de>,
Ingo Molnar <mingo@...e.hu>
Subject: Re: [patches] [PATCH] [21/22] x86_64: Extend bzImage protocol for relocatable bzImage
"H. Peter Anvin" <hpa@...or.com> writes:
> yhlu wrote:
>> so the kexec tools need to scan the pci devices list, and find out how
>> to set real_mode.isVGA and orig_video_mode, also need to parse the
>> comand line about vga console.
>
> BTW, welcome to the hell of bypassing setup.
Well in this case things are so very much better then attempting to
us setup.S it isn't a real option.
In general BIOS calls just don't work reliably after linux has
been running for a while.
As for YH's point it does look like there are a few ways
to poke the linux kernel to see what is happening.
We can look in /proc/ioports and see what has reserved
the video resources. That should give us a reasonable
estimate of the video adapter. We can do an ioctl to
the console and see how many lines and columns we have.
Reusing boot_params could be nice but if we have the information
available in other ways digging it out that way is quite possibly
better.
Eric
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists