[Qemu-devel] guidance regarding GSOC

[Qemu-devel] guidance regarding GSOC

[Faqeer ALI]

[-- Attachment #1: Type: text/plain, Size: 714 bytes --]


Dear Sir,


I am a graduate student at MAJU university Islamabad Pakistan, as a course project I have already worked with qemu and openmoko.

During this summers, I would be glad to work with qemu.

I need some guidance, I have downloaded the qemu sources, 
  And as per "Convert Monitor commands to the QObject API" or "Improve/Simplify the QObject API" projects, I only found the qobject.h in the sources, can you please give me little details, so that I could start working on it.
Regards
Faqeer Ali

 		 	   		  
_________________________________________________________________
Hotmail: Trusted email with Microsoft’s powerful SPAM protection.
http://clk.atdmt.com/GBL/go/210850552/direct/01/

[-- Attachment #2: Type: text/html, Size: 1024 bytes --]

Re: [Qemu-devel] guidance regarding GSOC

[Luiz Capitulino]

On Fri, 26 Mar 2010 11:09:44 +0000
Faqeer ALI <faqeerali@hotmail.com> wrote:

> 
> Dear Sir,
> 
> 
> I am a graduate student at MAJU university Islamabad Pakistan, as a course project I have already worked with qemu and openmoko.
> 
> During this summers, I would be glad to work with qemu.
> 
> I need some guidance, I have downloaded the qemu sources, 

 Did you use git for that or did you download a tarball?

>   And as per "Convert Monitor commands to the QObject API" or "Improve/Simplify the QObject API" projects, I only found the qobject.h in the sources, can you please give me little details, so that I could start working on it.

 You can find two examples of QObject conversion in the following
commits: 588b383, d96fd29. But note that the difficulty of the
conversion can vary. Some are just error handling, like 81a1b45.

 The problem with the current QObject API is that conversions can
get complex, like do_pci_info(). We'd like to find ways to it
simpler, if possible.