All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/5] linux-yocto: consolidated pull request
Date: Sat, 2 May 2015 23:52:22 -0400	[thread overview]
Message-ID: <55459B76.4090502@windriver.com> (raw)
In-Reply-To: <1430557216.18360.38.camel@linuxfoundation.org>

On 2015-05-02 5:00 AM, Richard Purdie wrote:
> On Fri, 2015-05-01 at 19:30 -0400, Bruce Ashfield wrote:
>> On 2015-05-01 6:59 PM, Richard Purdie wrote:
>>> On Thu, 2015-04-30 at 21:34 -0400, Bruce Ashfield wrote:
>>>> Here is the latest consolidated pull request for the supported linux-yocto
>>>> kernels.
>>>>
>>>>    - We have a refresh of the 3.14-rt support
>>>>    - bluetooh configuration changes for common-pc/qemux86
>>>>    - braswell BSP features and fixes
>>>>    - Introduction of the 4.1-rc1 -dev kernel (and associated perf fix).
>>>>
>>>> I've built and booted these on my local machines and qemu, and
>>>> everything was sane.
>>>>
>>>> The -dev kernel obviously isn't something for deployment yet, but
>>>> it builds, and forms the base for follow up config changes, features
>>>> and development work. I built and booted core-image-kernel dev with
>>>> the 4.1 changes in place.
>>>
>>> The autobuilder showed up this for an x32 build :/.
>>
>> Can one of the intel folks have a look at this ? I won't be able to get
>> to it until Tuesday at the earliest.
>
> I had a look into this. The issue is that this has been applied:
>
> http://git.yoctoproject.org/cgit.cgi/linux-yocto-3.19/commit/?h=standard/base&id=423e98721e048f6c7b925a75448f6c4ecb2b5b69
>
> but it needs:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=ce793486e23e0162a732c605189c8028e0910e86
>
> and the ioapic driver also appears to need:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=ecf5636dcd59cd5508641f995cc4c2bafedbb995
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/patch/?id=62d1141ff34e35de496ba06491c8e854b23b3f3e
>
>
> which meant I also had to add:
>
> struct resource_win {
> 	struct resource res;		/* In master (CPU) address space */
> 	resource_size_t offset;		/* Translation offset for bridge */
> };
>
> to drivers/acpi/ioapic.c to make it compile which appears to be related to:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=a49170b552423a3e85fc4f0d778c707402ee4863
>
> which depends on a number of patches from around that time which change acpi/resource.c:
>
> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/log/drivers/acpi/resource.c
>
> (from 2015/2/3)
>
> At this point I'm out my depth on how you want to fix this but it does
> appear related to the Braswell changes.
>
> To be clear qemux86 and qemux86-64 don't build at all with this series.
> I'll see if I can just drop the Braswell parts.

I did reproduce the issue here as well, so with any luck, I can sneak
enough time to have this fixed for Monday after all.

Bruce

>
> Cheers,
>
> Richard
>



  parent reply	other threads:[~2015-05-03  3:52 UTC|newest]

Thread overview: 59+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01  1:34 [PATCH 0/5] linux-yocto: consolidated pull request Bruce Ashfield
2015-05-01  1:34 ` [PATCH 1/5] linux-yocto/3.14: refresh -rt support Bruce Ashfield
2015-05-01  1:34 ` [PATCH 2/5] linux-yocto: add core bluetooth support to qemux86* and common-pc* Bruce Ashfield
2015-05-01  1:34 ` [PATCH 3/5] linux-yocto/3.19: Braswell support and bug fixes Bruce Ashfield
2015-05-01  1:34 ` [PATCH 4/5] perf: fix build (and feature tests) for 4.1-rcX Bruce Ashfield
2015-05-01  1:34 ` [PATCH 5/5] linux-yocto-dev: introduce 4.1-rc development kernel Bruce Ashfield
2015-05-01 22:59 ` [PATCH 0/5] linux-yocto: consolidated pull request Richard Purdie
2015-05-01 23:30   ` Bruce Ashfield
2015-05-02  8:13     ` Martin Jansa
2015-05-03  2:50       ` Bruce Ashfield
2015-05-06 14:42         ` Martin Jansa
2015-05-06 14:58           ` Bruce Ashfield
2015-05-06 15:33             ` Martin Jansa
2015-05-06 15:44               ` Richard Purdie
2015-05-06 16:07                 ` Martin Jansa
2015-05-06 17:46                   ` Bruce Ashfield
2015-05-06 21:32                     ` Richard Purdie
2015-05-06 22:49                       ` Martin Jansa
2015-05-07 15:33                         ` Bruce Ashfield
2015-05-07  6:33               ` Khem Raj
2015-05-02  9:00     ` Richard Purdie
2015-05-03  2:53       ` Bruce Ashfield
2015-05-03  3:52       ` Bruce Ashfield [this message]
2015-05-03 10:48         ` Richard Purdie
2015-05-03 21:30 ` Richard Purdie
2015-05-04  4:36   ` Bruce Ashfield
2015-05-04 15:01   ` Bruce Ashfield
  -- strict thread matches above, loose matches on Subject: below --
2023-02-01 16:28 bruce.ashfield
2020-11-19 19:17 Bruce Ashfield
2020-05-29  1:29 Bruce Ashfield
2020-05-03 15:44 Bruce Ashfield
2020-05-04  8:30 ` Richard Purdie
2020-05-04 12:56   ` Bruce Ashfield
2020-03-24 23:04 Bruce Ashfield
2016-07-27 16:57 Bruce Ashfield
2016-06-21 15:20 Bruce Ashfield
2016-04-13 16:12 Bruce Ashfield
2015-03-24 18:57 Bruce Ashfield
2015-03-25  9:26 ` Richard Purdie
2015-03-25 12:13   ` Bruce Ashfield
2015-03-25 13:26     ` Bruce Ashfield
2015-03-25 13:52       ` Richard Purdie
2013-08-23 18:08 Bruce Ashfield
2013-08-23 21:30 ` Bruce Ashfield
2013-08-24  6:33 ` Saul Wold
2013-08-24 13:34   ` Bruce Ashfield
2013-08-24 13:45     ` Bruce Ashfield
2013-08-24 13:50       ` Saul Wold
2013-08-24 13:53         ` Bruce Ashfield
2013-08-24 14:47         ` Bruce Ashfield
2013-08-24 14:59         ` Bruce Ashfield
2013-08-24 16:05         ` Bruce Ashfield
2012-02-05  6:31 Bruce Ashfield
2012-02-08  4:09 ` Saul Wold
2012-01-11 18:52 Bruce Ashfield
2012-01-17 19:28 ` Saul Wold
2011-01-10 17:30 Bruce Ashfield
2011-01-10 21:05 ` Richard Purdie
2011-01-13  6:01 ` Saul Wold

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=55459B76.4090502@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.