<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/arch/sh, branch linux-2.6.21.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.21.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.21.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2007-03-28T08:24:47Z</updated>
<entry>
<title>sh: Kill bogus GCC4 symbol exports.</title>
<updated>2007-03-28T08:24:47Z</updated>
<author>
<name>Paul Mundt</name>
</author>
<published>2007-03-28T08:24:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=9c5b406b9a857a67caf778f096bfc7f4e6b0401a'/>
<id>urn:sha1:9c5b406b9a857a67caf778f096bfc7f4e6b0401a</id>
<content type='text'>
__sdivsi3_i4i, __udiv_qrnnd_16, and __udivsi3_i4i don't exist
outside of the ST compiler, so kill them off.

This causes compile failures with other GCC4 compilers.

Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sh: Fix bogus regs pointer in do_IRQ().</title>
<updated>2007-03-14T04:03:35Z</updated>
<author>
<name>Paul Mundt</name>
</author>
<published>2007-03-14T04:03:35Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3afb209a43a4216ad4f1411922d47a44252926c6'/>
<id>urn:sha1:3afb209a43a4216ad4f1411922d47a44252926c6</id>
<content type='text'>
SH-3 and SH-4 were trampling the register, and SH-2 wasn't even
setting it in the first place. This ended up with some rather
broken behaviour in the sysrq show_regs().

Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sh: Fix SH-3 cache entry_mask and way_size calculation.</title>
<updated>2007-03-12T07:15:22Z</updated>
<author>
<name>Paul Mundt</name>
</author>
<published>2007-03-12T07:15:22Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ffe1b4e9f436fd7bb784f3bf7ee963c149fbca5f'/>
<id>urn:sha1:ffe1b4e9f436fd7bb784f3bf7ee963c149fbca5f</id>
<content type='text'>
The code for performing the calculation was only in the SH-4 probe
path, move it out to the common path so the other parts get this
right too.

Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sh: Fix PCI BAR address-space wraparound.</title>
<updated>2007-03-12T05:50:49Z</updated>
<author>
<name>Hideo Saito</name>
</author>
<published>2007-03-12T05:50:49Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=bb68660943fc0dc2a5fa634243f3c6b7fb715626'/>
<id>urn:sha1:bb68660943fc0dc2a5fa634243f3c6b7fb715626</id>
<content type='text'>
When a SH7751R system includes a card that has wide range space
like a graphics card, the pci-pci bridge controller can't set the
correct address range.

For example, when *lower_limit is 0xfd000000 and bar_size is
0x4000000, in the following code at arch/sh/drivers/pci/pci-auto.c,
0x0 is set in bar_value.

pciauto_setup_bars()
{
...
                bar_value = ((*lower_limit - 1) &amp; ~(bar_size - 1)) + bar_size;
...
                *lower_limit = bar_value + bar_size;
}

As a result, 0x4000000 is set in *lower_limit, but this value is wrong.

The following patch avoids this problem by checking the range of the
value and refusing to update the BAR if the calculated value ends up
being bogus.

Signed-off-by: Hideo Saito &lt;saito@densan.co.jp&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sh: Kill off I/O cruft for R7780RP.</title>
<updated>2007-03-05T11:19:57Z</updated>
<author>
<name>Paul Mundt</name>
</author>
<published>2007-03-05T11:19:57Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=ccd45ad405bcb1504bd923bd0487902374c942c8'/>
<id>urn:sha1:ccd45ad405bcb1504bd923bd0487902374c942c8</id>
<content type='text'>
We don't have any use for these machvec fixups anymore, kill them all
off and go with the generic instead.

Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sh: Revert lazy dcache writeback changes.</title>
<updated>2007-03-05T10:46:47Z</updated>
<author>
<name>Paul Mundt</name>
</author>
<published>2007-03-05T10:46:47Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=39e688a94b94eaba768b1494e19e96f828fc2688'/>
<id>urn:sha1:39e688a94b94eaba768b1494e19e96f828fc2688</id>
<content type='text'>
These ended up causing too many problems on older parts,
revert for now..

Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sh: Enable SM501 support for RTS7751R2D.</title>
<updated>2007-03-05T05:13:26Z</updated>
<author>
<name>Paul Mundt</name>
</author>
<published>2007-03-01T09:47:08Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c87a7111349891043cb0a62b0ba745264d4b600a'/>
<id>urn:sha1:c87a7111349891043cb0a62b0ba745264d4b600a</id>
<content type='text'>
This enables the SM501 drivers for the R2D board. Additional
work needs to be done to migrate off of the VoyagerGX cchip
code to make use of the rest of the mfd infrastructure.

Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sh: Use L1_CACHE_BYTES for .data.cacheline_aligned.</title>
<updated>2007-03-05T05:13:26Z</updated>
<author>
<name>Paul Mundt</name>
</author>
<published>2007-03-01T06:56:31Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=87e29cacb7d09c81b09224bec395f970df958af4'/>
<id>urn:sha1:87e29cacb7d09c81b09224bec395f970df958af4</id>
<content type='text'>
Previously this was using a hardcoded 32, use L1_CACHE_BYTES for
cacheline alignment instead.

Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sh: Fix kernel thread stack corruption with preempt.</title>
<updated>2007-03-05T05:13:26Z</updated>
<author>
<name>Hideo Saito</name>
</author>
<published>2007-02-28T09:35:42Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=e6bcf562e58662b9765748d346e4c076b20e3aa5'/>
<id>urn:sha1:e6bcf562e58662b9765748d346e4c076b20e3aa5</id>
<content type='text'>
When I run a preemptive kernel-2.6.20 for SH7780, a created
kthread(pdflush) can not exit by do_exit() in kernel_thread_helper. I
think that the created kthread should have a room for 'struct pt_regs'
space on the stack top, because __switch_to() will refer to the space as
follows using 'regs = task_pt_regs(prev)' and next condition may be true.

Signed-off-by: Hideo Saito &lt;saito@densan.co.jp&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
<entry>
<title>sh: Fix sigmask trampling in signal delivery.</title>
<updated>2007-03-05T05:13:25Z</updated>
<author>
<name>Ryusuke Sakato</name>
</author>
<published>2007-02-23T04:22:56Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c8bfa1fdc84af7b5e3c7f825a9f0bc6e8a19f5d5'/>
<id>urn:sha1:c8bfa1fdc84af7b5e3c7f825a9f0bc6e8a19f5d5</id>
<content type='text'>
There was a missing return in do_signal() that caused the saved
sigmask to be written back after having successfully delivered
the signal.

Signed-off-by: Ryusuke Sakato &lt;sakato@hsdv.com&gt;
Signed-off-by: Paul Mundt &lt;lethal@linux-sh.org&gt;
</content>
</entry>
</feed>
