Avi Kivity wrote:
> Zhang, Xiantao wrote:
>>
>> Hi Avi,
>> Thanks, But seems it is very hard to implement it through a.o,
>> because all functions in this part should be relocated to another
>> separate address space in whole. If it is implemented as a
>> module(ko), we can relocate it as a
Hi Shahar,
I'd like to try that.
The documentation of vgabios is not very specific about the tools needed to
compile it, but it makes a reference to a Turbo C 2.0, so i guess that's the
bcc 16bit compiler you mention in your email.
Would it work with one of the recent versions of borland's turbo
Avi Kivity wrote:
> Neo Jia wrote:
>> On Nov 24, 2007 12:00 AM, Avi Kivity <[EMAIL PROTECTED]> wrote:
>>
>>> Neo Jia wrote:
>>>
The version of kvm I used for kvm module is
"694401697ccd822bb08019731c3ee1bb34323d8e" and the kvm-userspace is
"a57b838b49bc4e4e7439b18d0323385d53e41
Hi,
If you have time you can compile a vgabios with vbe extension that support your
resolution. Even though this resolution is not defined in the spec, the XP
driver doesn't care. I did it for 1280x800 and it seems that it should work
also for your case. The really nasty thing here is that y
Bugs item #1838069, was opened at 2007-11-25 15:58
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=1838069&group_id=180599
Please note that this message will contain a full copy
Zhang, Xiantao wrote:
That answer confuses me. kvm_arch_init() for ia64 will reside in
kvm.ko just like kvm_init(), right?
So THIS_MODULE will be the same in kvm_arch_init() and kvm_init().
So which module are you giving as argument?
>>> Sorry for confusing yo
Avi Kivity wrote:
> Zhang, Xiantao wrote:
>> Carsten Otte wrote:
>>
>>> Zhang, Xiantao wrote:
>>>
No, THIS_MODULE just stands for itself. But for IA64, we need
another module, and it will register some information to kvm
module. So, we have to keep it.
>>> That answer confus
Neo Jia wrote:
> On Nov 24, 2007 12:00 AM, Avi Kivity <[EMAIL PROTECTED]> wrote:
>
>> Neo Jia wrote:
>>
>>> The version of kvm I used for kvm module is
>>> "694401697ccd822bb08019731c3ee1bb34323d8e" and the kvm-userspace is
>>> "a57b838b49bc4e4e7439b18d0323385d53e41c7f".
>>>
>>>
>> T
Zhang, Xiantao wrote:
> Carsten Otte wrote:
>
>> Zhang, Xiantao wrote:
>>
>>> No, THIS_MODULE just stands for itself. But for IA64, we need another
>>> module, and it will register some information to kvm module. So, we
>>> have to keep it.
>>>
>> That answer confuses me. kvm_arch_in
