From: Marek Vasut <marex@denx.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] bitbake: Oldest kernel for nios2 is 3.19
Date: Sun, 08 May 2016 20:14:56 +0200 [thread overview]
Message-ID: <572F8220.3020500@denx.de> (raw)
In-Reply-To: <CAMKF1sq_Ugh8uFONQA5xdxyYgiCXbJEUaf3FyrRdy+=iDYR1=w@mail.gmail.com>
On 05/08/2016 08:13 PM, Khem Raj wrote:
> I will just fold it into my series.
OK, thanks :)
> On Sun, May 8, 2016 at 10:55 AM, Marek Vasut <marex@denx.de> wrote:
>> On 05/08/2016 07:31 PM, Khem Raj wrote:
>>> I was just trying to avoid patch conflict :)
>>
>> If you want me to repost updated patch, just let me know, but the fix
>> will be really trivial in this case ;-)
>>
>>> On Sun, May 8, 2016 at 10:19 AM Marek Vasut <marex@denx.de
>>> <mailto:marex@denx.de>> wrote:
>>>
>>> On 05/08/2016 07:06 PM, Khem Raj wrote:
>>> >
>>> >> On May 8, 2016, at 6:00 AM, Marek Vasut <marex@denx.de
>>> <mailto:marex@denx.de>> wrote:
>>> >>
>>> >> The oldest kernel version for nios2 is 3.19.0, set it so, otherwise
>>> >> qemu-nios2 -r ${OLDEST_KERNEL} fails with "FATAL: kernel too old"
>>> >> message from glibc.
>>> >>
>>> >> Signed-off-by: Marek Vasut <marex@denx.de <mailto:marex@denx.de>>
>>> >> Cc: Richard Purdie <richard.purdie@linuxfoundation.org
>>> <mailto:richard.purdie@linuxfoundation.org>>
>>> >> ---
>>> >> meta/conf/bitbake.conf | 1 +
>>> >> 1 file changed, 1 insertion(+)
>>> >>
>>> >> diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
>>> >> index 1c4175f..2f5db22 100644
>>> >> --- a/meta/conf/bitbake.conf
>>> >> +++ b/meta/conf/bitbake.conf
>>> >> @@ -405,6 +405,7 @@ SDKPATHNATIVE = "${SDKPATH}/sysroots/${SDK_SYS}"
>>> >>
>>> >> OLDEST_KERNEL = "2.6.32"
>>> >> OLDEST_KERNEL_aarch64 = "3.14"
>>> >> +OLDEST_KERNEL_nios2 = “3.19"
>>> >
>>> > if you don’t need it on krogoth, then I would suggest to hold this
>>> patch for master since
>>> > I have a series which upgrades glibc to 2.24 and 2.24 needs 3.x
>>> minimum
>>> >
>>> > see
>>> >
>>> >
>>> https://github.com/kraj/openembedded-core/commit/1be5ebb2e1e2d39936d13ce158db29954bc6dabe
>>>
>>> I don't mind either way. I need 3.19, not 3.2 though, so your patch does
>>> not help me if I understand it correctly.
>>>
>>> >> STAGING_KERNEL_DIR = "${TMPDIR}/work-shared/${MACHINE}/kernel-source"
>>> >> STAGING_KERNEL_BUILDDIR =
>>> "${TMPDIR}/work-shared/${MACHINE}/kernel-build-artifacts"
>>> >>
>>> >> --
>>> >> 2.7.0
>>> >>
>>> >> --
>>> >> _______________________________________________
>>> >> Openembedded-core mailing list
>>> >> Openembedded-core@lists.openembedded.org
>>> <mailto:Openembedded-core@lists.openembedded.org>
>>> >> http://lists.openembedded.org/mailman/listinfo/openembedded-core
>>> >
>>>
>>>
>>> --
>>> Best regards,
>>> Marek Vasut
>>>
>>
>>
>> --
>> Best regards,
>> Marek Vasut
--
Best regards,
Marek Vasut
next prev parent reply other threads:[~2016-05-08 18:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-08 13:00 [PATCH] bitbake: Oldest kernel for nios2 is 3.19 Marek Vasut
2016-05-08 17:06 ` Khem Raj
2016-05-08 17:19 ` Marek Vasut
2016-05-08 17:31 ` Khem Raj
2016-05-08 17:55 ` Marek Vasut
2016-05-08 18:13 ` Khem Raj
2016-05-08 18:14 ` Marek Vasut [this message]
2016-05-10 10:21 ` Ruslan Bilovol
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=572F8220.3020500@denx.de \
--to=marex@denx.de \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox