<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/arch/m68k/coldfire, branch linux-3.18.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.18.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-3.18.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2018-05-30T05:47:40Z</updated>
<entry>
<title>m68k: set dma and coherent masks for platform FEC ethernets</title>
<updated>2018-05-30T05:47:40Z</updated>
<author>
<name>Greg Ungerer</name>
</author>
<published>2018-03-28T07:12:18Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=2231cc411a037eee7afc91904661cdb3a2f672d7'/>
<id>urn:sha1:2231cc411a037eee7afc91904661cdb3a2f672d7</id>
<content type='text'>
[ Upstream commit f61e64310b75733d782e930d1fb404b84699eed6 ]

As of commit 205e1b7f51e4 ("dma-mapping: warn when there is no
coherent_dma_mask") the Freescale FEC driver is issuing the following
warning on driver initialization on ColdFire systems:

WARNING: CPU: 0 PID: 1 at ./include/linux/dma-mapping.h:516 0x40159e20
Modules linked in:
CPU: 0 PID: 1 Comm: swapper Not tainted 4.16.0-rc7-dirty #4
Stack from 41833dd8:
        41833dd8 40259c53 40025534 40279e26 00000003 00000000 4004e514 41827000
        400255de 40244e42 00000204 40159e20 00000009 00000000 00000000 4024531d
        40159e20 40244e42 00000204 00000000 00000000 00000000 00000007 00000000
        00000000 40279e26 4028d040 40226576 4003ae88 40279e26 418273f6 41833ef8
        7fffffff 418273f2 41867028 4003c9a2 4180ac6c 00000004 41833f8c 4013e71c
        40279e1c 40279e26 40226c16 4013ced2 40279e26 40279e58 4028d040 00000000
Call Trace:
        [&lt;40025534&gt;] 0x40025534
 [&lt;4004e514&gt;] 0x4004e514
 [&lt;400255de&gt;] 0x400255de
 [&lt;40159e20&gt;] 0x40159e20
 [&lt;40159e20&gt;] 0x40159e20

It is not fatal, the driver and the system continue to function normally.

As per the warning the coherent_dma_mask is not set on this device.
There is nothing special about the DMA memory coherency on this hardware
so we can just set the mask to 32bits in the platform data for the FEC
ethernet devices.

Signed-off-by: Sasha Levin &lt;alexander.levin@microsoft.com&gt;
Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>m68k/coldfire: remove second asm/mcfclk.h inclusion in m54xx.c</title>
<updated>2014-09-28T23:18:36Z</updated>
<author>
<name>Fabian Frederick</name>
</author>
<published>2014-09-16T18:43:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1089c552fb50a4693bddb6ec00e58d4e7998ce55'/>
<id>urn:sha1:1089c552fb50a4693bddb6ec00e58d4e7998ce55</id>
<content type='text'>
asm/mcfclk.h was included twice.

Signed-off-by: Fabian Frederick &lt;fabf@skynet.be&gt;
Signed-off-by: Greg Ungerer &lt;gerg@uclinux.org&gt;
</content>
</entry>
<entry>
<title>m68knommu: fix size of address field for 5272 interrupt controller</title>
<updated>2014-09-28T23:18:36Z</updated>
<author>
<name>Greg Ungerer</name>
</author>
<published>2014-08-28T04:39:45Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ecb6bdcde2474c8c954179b74fd3df3ad84fba75'/>
<id>urn:sha1:ecb6bdcde2474c8c954179b74fd3df3ad84fba75</id>
<content type='text'>
Picked up by the 0-day buidler:

All warnings:
&gt;&gt; arch/m68k/coldfire/intc-5272.c:46:20: warning: large integer implicitly truncated to unsigned type [-Woverflow]
     /*MCF_IRQ_EINT1*/ { .icr = MCFSIM_ICR1, .index = 28, .ack = 1, },
...

The problem stems from the changes to make all ColdFire register addresses
absolute, in commit d72a5abb ("make remaining ColdFire 5272 register
definitions absolute"). That change did not take into account that the
addresses were stored as offsets in the irqmap of the intc-5272.c code.
Make the field that now stores register addresses big enough to hold
addresses.

Signed-off-by: Greg Ungerer &lt;gerg@uclinux.org&gt;
</content>
</entry>
<entry>
<title>m68k: fix crufty ColdFire intro comments</title>
<updated>2014-09-28T23:18:34Z</updated>
<author>
<name>Greg Ungerer</name>
</author>
<published>2014-08-19T01:55:24Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ece9ae6515727d56ca21a8c925965b731a88b43b'/>
<id>urn:sha1:ece9ae6515727d56ca21a8c925965b731a88b43b</id>
<content type='text'>
Quite a few of the ColdFire specific support files have a pathname in the
title comments of the file. These files have moved around a bit over the
years, and most are no longer accurate. Remove the pathname and fix the
comments to include at least a short description of the files contents.

Signed-off-by: Greg Ungerer &lt;gerg@uclinux.org&gt;
Acked-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;
</content>
</entry>
<entry>
<title>m68k: move coldfire platform code</title>
<updated>2014-09-28T23:18:34Z</updated>
<author>
<name>Greg Ungerer</name>
</author>
<published>2014-08-19T01:39:09Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=f86b9e03837beafb4b48d53a76ee4b88559226de'/>
<id>urn:sha1:f86b9e03837beafb4b48d53a76ee4b88559226de</id>
<content type='text'>
Move the m68k ColdFire platform support code directory to be with the
existing m68k platforms. Although the ColdFire is not a platform as such,
we have always kept all its support together. No reason to change that
as this time.

Signed-off-by: Greg Ungerer &lt;gerg@uclinux.org&gt;
Acked-by: Geert Uytterhoeven &lt;geert@linux-m68k.org&gt;
</content>
</entry>
</feed>
