<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/arch/powerpc/Makefile, branch linux-4.8.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.8.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-4.8.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2016-08-10T13:01:53Z</updated>
<entry>
<title>powerpc/Makefile: Use cflags-y/aflags-y for setting endian options</title>
<updated>2016-08-10T13:01:53Z</updated>
<author>
<name>Michael Ellerman</name>
</author>
<published>2016-08-09T12:43:46Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=164af597ce945751e2dcd53d0a86e84203a6d117'/>
<id>urn:sha1:164af597ce945751e2dcd53d0a86e84203a6d117</id>
<content type='text'>
When we introduced the little endian support, we added the endian flags
to CC directly using override. I don't know the history of why we did
that, I suspect no one does.

Although this mostly works, it has one bug, which is that CROSS32CC
doesn't get -mbig-endian. That means when the compiler is little endian
by default and the user is building big endian, vdso32 is incorrectly
compiled as little endian and the kernel fails to build.

Instead we can add the endian flags to cflags-y/aflags-y, and then
append those to KBUILD_CFLAGS/KBUILD_AFLAGS.

This has the advantage of being 1) less ugly, 2) the documented way of
adding flags in the arch Makefile and 3) it fixes building vdso32 with a
LE toolchain.

Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;
</content>
</entry>
<entry>
<title>powerpc/sparse: Pass endianness to sparse</title>
<updated>2016-07-14T10:44:03Z</updated>
<author>
<name>Daniel Axtens</name>
</author>
<published>2016-07-12T00:54:51Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=62c2c5cf387beb4bbf45045c3041dc9cfb40e5df'/>
<id>urn:sha1:62c2c5cf387beb4bbf45045c3041dc9cfb40e5df</id>
<content type='text'>
Explicitly give sparse an endianness in the Makefile, so that it
doesn't get confused.

Normally we have #ifdef one and #else the other, so it doesn't usually
matter, but we have been bitten by it before, and indeed this patch
fixes a number of sparse errors.

Suggested-by: Arnd Bergmann &lt;arnd@arndb.de&gt;
Signed-off-by: Daniel Axtens &lt;dja@axtens.net&gt;
Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;
</content>
</entry>
<entry>
<title>powerpc: Avoid -maltivec when using clang integrated assembler</title>
<updated>2016-07-05T13:58:53Z</updated>
<author>
<name>Anton Blanchard</name>
</author>
<published>2015-11-25T23:45:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9ddf0075f9184f1e1dabf7bfea6397b00ee17e46'/>
<id>urn:sha1:9ddf0075f9184f1e1dabf7bfea6397b00ee17e46</id>
<content type='text'>
Check the assembler supports -maltivec by wrapping it with
call as-option.

Signed-off-by: Anton Blanchard &lt;anton@samba.org&gt;
Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;
</content>
</entry>
<entry>
<title>Merge branch 'next' of git://git.kernel.org/pub/scm/linux/kernel/git/scottwood/linux into next</title>
<updated>2016-03-14T09:05:14Z</updated>
<author>
<name>Michael Ellerman</name>
</author>
<published>2016-03-14T09:05:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=a1b5344620a3e6291afaf7542714ba9c391ef1c7'/>
<id>urn:sha1:a1b5344620a3e6291afaf7542714ba9c391ef1c7</id>
<content type='text'>
Freescale updates from Scott:

"Highlights include 8xx optimizations, 32-bit checksum optimizations,
86xx consolidation, e5500/e6500 cpu hotplug, more fman and other dt
bits, and minor fixes/cleanup."
</content>
</entry>
<entry>
<title>powerpc/86xx: Switch to kconfig fragments approach</title>
<updated>2016-03-12T01:19:12Z</updated>
<author>
<name>Alessio Igor Bogani</name>
</author>
<published>2016-02-22T09:26:14Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=43de32c5630f712b3ab06f22db96a6eeb8bfafdd'/>
<id>urn:sha1:43de32c5630f712b3ab06f22db96a6eeb8bfafdd</id>
<content type='text'>
Signed-off-by: Alessio Igor Bogani &lt;alessio.bogani@elettra.eu&gt;
Signed-off-by: Scott Wood &lt;oss@buserror.net&gt;
</content>
</entry>
<entry>
<title>powerpc/ftrace: Add Kconfig &amp; Make glue for mprofile-kernel</title>
<updated>2016-03-07T03:53:56Z</updated>
<author>
<name>Torsten Duwe</name>
</author>
<published>2016-03-03T04:27:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8c50b72a3b4f1f7cdfdfebd233b1cbd121262e65'/>
<id>urn:sha1:8c50b72a3b4f1f7cdfdfebd233b1cbd121262e65</id>
<content type='text'>
Firstly we add logic to Kconfig to allow a user to choose if they want
mprofile-kernel. This has to be user-selectable because only some
current toolchains support it. If we enabled it unconditionally we would
prevent some users from building the kernel entirely.

Arguably it would be nice if we could detect if mprofile-kernel was
available, and use it then. However that would violate the principle of
least surprise because a user having choosen options such as live
patching, would then see them quietly disabled at build time.

We also make the user selectable option negative, ie. it disables when
selected, so that allyesconfig continues to build on old toolchains.

Once we've decided we do want to use mprofile-kernel, we then add a
script which checks it actually works. That is because there are
versions of gcc that accept the flag but don't generate correct code.

Due to the way kconfig works, we can't error out when we detect a
non-working toolchain. If we did a user would never be able to modify
their config and run oldconfig - because the check would block oldconfig
from running. Instead we emit a warning and add a bogus flag to CFLAGS
so that the build will fail.

Signed-off-by: Torsten Duwe &lt;duwe@suse.de&gt;
Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;
</content>
</entry>
<entry>
<title>powerpc/cell: Drop CONFIG_TUNE_CELL in favour of CONFIG_CELL_CPU</title>
<updated>2015-10-19T08:51:18Z</updated>
<author>
<name>Michael Ellerman</name>
</author>
<published>2015-10-13T08:17:07Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bed08b7e1fa41eac214acb17b7aa20a0e5c4b4e6'/>
<id>urn:sha1:bed08b7e1fa41eac214acb17b7aa20a0e5c4b4e6</id>
<content type='text'>
The TUNE_CELL option allows you to build a kernel that runs on multiple
CPUs but is tuned (ie. optimised) to run on Cell CPUs. Now days no one
is building a distro in that fashion, and any users who are building
custom kernels for their Cell machines are better off building with
CONFIG_CELL_CPU, which builds a kernel that only runs on Cell and
therefore can be optimised even more aggresively.

Dropping the option also avoids confusing other users, who are presented
with an option to tune for Cell when they are not building for a Cell
CPU at all.

Suggested-by: Thomas Huth &lt;thuth@redhat.com&gt;
Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;
</content>
</entry>
<entry>
<title>powerpc: Add ppc64le_defconfig</title>
<updated>2015-10-01T06:52:03Z</updated>
<author>
<name>Michael Ellerman</name>
</author>
<published>2015-09-23T05:40:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2adc48a691866fbb3134dd3abd77647a8b5a9307'/>
<id>urn:sha1:2adc48a691866fbb3134dd3abd77647a8b5a9307</id>
<content type='text'>
Based directly on ppc64_defconfig using merge_config.

Signed-off-by: Michael Ellerman &lt;mpe@ellerman.id.au&gt;
</content>
</entry>
<entry>
<title>Merge branch 'kbuild' of git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild</title>
<updated>2015-09-08T21:12:19Z</updated>
<author>
<name>Linus Torvalds</name>
</author>
<published>2015-09-08T21:12:19Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=dab3c3cc4f44273ccf2d7ff57c0a4f5bd45c0528'/>
<id>urn:sha1:dab3c3cc4f44273ccf2d7ff57c0a4f5bd45c0528</id>
<content type='text'>
Pull core kbuild updates from Michal Marek:
 - modpost portability fix
 - linker script fix
 - genksyms segfault fix
 - fixdep cleanup
 - fix for clang detection

* 'kbuild' of git://git.kernel.org/pub/scm/linux/kernel/git/mmarek/kbuild:
  kbuild: Fix clang detection
  kbuild: fixdep: drop meaningless hash table initialization
  kbuild: fixdep: optimize code slightly
  genksyms: Regenerate parser
  genksyms: Duplicate function pointer type definitions segfault
  kbuild: Fix .text.unlikely placement
  Avoid conflict with host definitions when cross-compiling
</content>
</entry>
<entry>
<title>kbuild: Fix clang detection</title>
<updated>2015-09-04T11:14:10Z</updated>
<author>
<name>Michal Marek</name>
</author>
<published>2015-08-19T15:36:41Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=5631d9c429857194bd55d7bcd8fa5bdd1a9899a3'/>
<id>urn:sha1:5631d9c429857194bd55d7bcd8fa5bdd1a9899a3</id>
<content type='text'>
We cannot detect clang before including the arch Makefile, because that
can set the default cross compiler. We also cannot detect clang after
including the arch Makefile, because powerpc wants to know about clang.
Solve this by using an deferred variable. This costs us a few shell
invocations, but this is only a constant number.

Reported-by: Behan Webster &lt;behanw@converseincode.com&gt;
Reported-by: Anton Blanchard &lt;anton@samba.org&gt;
Signed-off-by: Michal Marek &lt;mmarek@suse.com&gt;
</content>
</entry>
</feed>
