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 19:48:19 -0700
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 05 Jun 2009 19:48:49 -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=JClDxxjcYqjRMm81fmhD346CjMHP746WWJ7vR52kF3M=; b=dWfrlCYCxbOz8uy/jzNyvSPBh46TfNJvpHURdRNuLoyYPXuQCX+eISKMOOj9EGkRjA nlFrwBhbPZIRQAvgETAz4KvWmVTfJZY8uSLdXznwk/necPbErhSLgGVktzKnT1OKl3De eWdDB5qsupixfnro6CmcIc8CwXK2Ut/PqL1sY=
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=s0bSQwj1yCG+uEKLFWrlMs/sfmqDBt25LL4Fjn6w802smzgXGdBCGM536loAxkOEU/ Kbsmf+r16zide/4Bp9/KquWfCdN7Uz3/eVgYhtE05hdoLSSxG/NfVGDQ2niKWsGWOyUY 6gzUJnCPb9rg5auGsthOM5RSFxiZ2rFpcBKKo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <5997D0BE578D47409D1EBD41DFD341F4777BD62E43@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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