You can disable all the wmi-XCI patch by openning the series file
(.git/patches/master/serie)
and comment out the entry for this patch at the end of the file. Then
you do a guilt-pop -a && guilt-push -a.
2009/6/6 Genki
Kuroda <
sfsugar@xxxxxxxxx>:
> 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>
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxhttp://lists.xensource.com/xen-devel
Home