WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Future of xenbits Linux trees

To: Kamala Narasimhan <Kamala.Narasimhan@xxxxxxxxxx>
Subject: Re: [Xen-devel] Future of xenbits Linux trees
From: Genki Kuroda <sfsugar@xxxxxxxxx>
Date: Fri, 5 Jun 2009 22:26:17 -0700
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 05 Jun 2009 22:26:50 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=Oi5UEWPfUw7vVAeXTX8WYXco/qIhBOXeYeLBkNlif7U=; b=jD+AC6R3CUbn11QEEVKmrFtUwgCP3AYdSfWx3DVb6N+I9NZ2BYclFk5eFLKkE5zVEi PezSdUdWlF69VKWec5/NRjWn0KBV144c9LOrm50ElU/NnQLsCEuGOA9jcRQ1OGjI9hCy KlbS295HV/L27TNcVq+O5IHaokmXb6UM+n064=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=eiTUnEQi8O4Wl6vI3jWFVW4w2MMo0WkeHlVl+vwIJINCR1BOGkPchcywvM7UHD+mvn WIodq9i/q+HwXhsMPolkux4d0yreTY7Jf/XCq6NfCZSvibnjpDWWC9fp4W2mIjYVVKb2 FiJQSe/+hOiJkOpCGrMZ5zcs5JmpNep+JgDn8=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <5997D0BE578D47409D1EBD41DFD341F4777BD62E44@xxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <53978.85469.qm@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <9c7090f40906051605kcd3e359ie7d430d417809d34@xxxxxxxxxxxxxx> <5997D0BE578D47409D1EBD41DFD341F4777BD62E43@xxxxxxxxxxxxxxxxxxxxxxxxx> <9c7090f40906051948r3781986apa8d8f34019c3133c@xxxxxxxxxxxxxx> <5997D0BE578D47409D1EBD41DFD341F4777BD62E44@xxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Kamala,

I encountered the wmi build issues after applying the linux-2.6.27-pq.git
I have no idea on what happens before applying the linux-2.6.27-pq.git

All I did was:

$ git clone http://xenbits.xen.org/git-http/xenclient/linux-2.6.27.git
$ cd linux-2.6.27
$ git clone http://xenbits.xen.org/git-http/xenclient/linux-2.6.27-pq.git
.git/patches
$ guilt-push -a
$ make --> wmi build issues.

GK

On Fri, Jun 5, 2009 at 7:53 PM, Kamala
Narasimhan<Kamala.Narasimhan@xxxxxxxxxx> wrote:
> Just to clarify - You mean you encounter wmi build issues mentioned below 
> with XenClient Linux 2.6.27 even when you *don't* apply the xen-acpi-wmi 
> patch from XenClient Linux 2.6.27 patch queue?
>
> Kamala
>
>> -----Original Message-----
>> From: Genki Kuroda [mailto:sfsugar@xxxxxxxxx]
>> Sent: Friday, June 05, 2009 10:48 PM
>> To: Kamala Narasimhan
>> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>> Subject: Re: [Xen-devel] Future of xenbits Linux trees
>>
>> Hi, Kamala,
>>
>> Thank you for the information.
>> I didn't apply the patch, and I don't have any intention to apply the
>> patch for this issue.
>>
>> GK
>>
>> On Fri, Jun 5, 2009 at 7:17 PM, Kamala
>> Narasimhan<Kamala.Narasimhan@xxxxxxxxxx> wrote:
>> > The xen-acpi-wmi patch in XenClient linux 2.6.27 patch queue is tied
>> to XenClient.  I didn't expect this patch to be used outside the scope
>> of XenClient which is why you encounter the below issues.
>> >
>> > Could you please momentarily exclude the patch before pushing the
>> rest or revert it if already applied and then build that branch?  Going
>> forward, I will create a XenClient flavor of wmi.c that won't step on
>> the base wmi implementation and configure the two to be mutually
>> exclusive.
>> >
>> > Kamala
>> >
>> >> -----Original Message-----
>> >> From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-
>> >> bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Genki Kuroda
>> >> Sent: Friday, June 05, 2009 7:06 PM
>> >> To: Boris Derzhavets
>> >> Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
>> >> Subject: Re: [Xen-devel] Future of xenbits Linux trees
>> >>
>> >> Hello, Boris,
>> >>
>> >> I had the same error, but I was able to compile after commenting out
>> >> the "HACK ALERT" section in /drivers/acpi/ec.c
>> >> More information seems to be in wmi.c.
>> >>
>> >> Who is taking care of this kind of issue? This is my first post...
>> >>
>> >> Here is the patch to show where I commented out.
>> >>
>> >> diff –git a/drivers/acpi/ec.c b/drivers/acpi/ec.c
>> >> index 2359480..b2c0221 100644
>> >> — a/drivers/acpi/ec.c
>> >> +++ b/drivers/acpi/ec.c
>> >> @@ -387,6 +387,7 @@ static int acpi_ec_read(struct acpi_ec *ec, u8
>> >> address, u8 * data)
>> >> /* HACK ALERT
>> >> * Please refer to wmi.c for an explanation on why we added this
>> hack.
>> >> */
>> >> +/*
>> >> if ( in_query_wmi_event_data == TRUE ) {
>> >> if ( address == 0×2b ) {
>> >> wmi_event_data_index = 0;
>> >> @@ -398,6 +399,7 @@ static int acpi_ec_read(struct acpi_ec *ec, u8
>> >> address, u8 * data)
>> >> wmi_event_data_index++;
>> >> }
>> >> }
>> >> +*/
>> >>
>> >> return result;
>> >> }
>> >>
>> >>
>> >> --
>> >> Genki Kuroda
>> >> E-mail: genkikuroda@xxxxxxxxx
>> >> Website: http://mulps.wordpress.com/
>> >>
>> >> On Fri, Jun 5, 2009 at 12:53 AM, Boris
>> >> Derzhavets<bderzhavets@xxxxxxxxx> wrote:
>> >> > Kernel: arch/x86/boot/vmlinuz is ready  (#2)
>> >> > ERROR: "wmi_install_notify_handler" [drivers/misc/hp-wmi.ko]
>> >> undefined!
>> >> > ERROR: "wmi_remove_notify_handler" [drivers/misc/hp-wmi.ko]
>> >> undefined!
>> >> > ERROR: "wmi_has_guid" [drivers/misc/hp-wmi.ko] undefined!
>> >> > ERROR: "wmi_has_guid" [drivers/misc/acer-wmi.ko] undefined!
>> >> > WARNING: modpost: Found 3 section mismatch(es).
>> >> > To see full details build your kernel with:
>> >> > 'make CONFIG_DEBUG_SECTION_MISMATCH=y'
>> >> > make[1]: *** [__modpost] Error 1
>> >> > make: *** [modules] Error 2
>> >> >
>> >> > Boris.
>> >>
>> >> _______________________________________________
>> >> 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