Hey Arnd,
On Fri, Sep 28, 2018 at 9:19 PM Arnd Bergmann wrote:
> You can probably work around it by enabling ARCH_HIGHBANK,
> which is a minimal platform with no other requirements, so it
> should only add a few milliseconds to the build.
Nice hack, thanks for the suggestion. Committed here:
htt
On Fri, Sep 28, 2018 at 6:04 PM Jason A. Donenfeld wrote:
>
> Hi Arnd,
>
> On Fri, Sep 28, 2018 at 5:59 PM Arnd Bergmann wrote:
> > Applied for 4.20 with subject line changed s/arm/ARM/, thanks!
>
> Thanks.
>
> > I think most people just build a 'defconfig' kernel, which includes
> > multiple pla
Hi Arnd,
On Fri, Sep 28, 2018 at 5:59 PM Arnd Bergmann wrote:
> Applied for 4.20 with subject line changed s/arm/ARM/, thanks!
Thanks.
> I think most people just build a 'defconfig' kernel, which includes
> multiple platforms that use ARCH_SUPPORTS_BIG_ENDIAN.
Right, that's what it looked like
On Wed, Sep 26, 2018 at 3:52 PM Jason A. Donenfeld wrote:
>
> This architecture, used for running in QEMU, runs just fine when
> compiled in big-endian mode. So enable it. This is enabled in exactly
> the same way that it is for other platforms (such as vexpress) that also
> support big-endian mod
(+ arm-soc)
On 26 September 2018 at 15:51, Jason A. Donenfeld wrote:
> This architecture, used for running in QEMU, runs just fine when
> compiled in big-endian mode. So enable it. This is enabled in exactly
> the same way that it is for other platforms (such as vexpress) that also
> support big-
This architecture, used for running in QEMU, runs just fine when
compiled in big-endian mode. So enable it. This is enabled in exactly
the same way that it is for other platforms (such as vexpress) that also
support big-endian mode in QEMU successfully.
Signed-off-by: Jason A. Donenfeld
---
Perso
6 matches
Mail list logo
