From: Maxim Kuvyrkov <maxim@codesourcery.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Greg Ungerer <gerg@snapgear.com>,
Linux/m68k <linux-m68k@vger.kernel.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>,
uClinux development list <uclinux-dev@uclinux.org>
Subject: Re: M68k tree updates
Date: Sat, 05 Dec 2009 21:53:10 +0300 [thread overview]
Message-ID: <4B1AAC16.5030107@codesourcery.com> (raw)
In-Reply-To: <10f740e80912041157j41984f4ay6ca2e56d70ac08e2@mail.gmail.com>
Geert Uytterhoeven wrote:
> On Mon, Nov 30, 2009 at 14:43, Maxim Kuvyrkov <maxim@codesourcery.com> wrote:
>> Geert Uytterhoeven wrote:
>>> It took me a while, but finally I managed to update
>>> http://git.kernel.org/?p=linux/kernel/git/geert/linux-m68k.git again.
>> ...
>>> If anything is missing, please tell me. Thx!
>> How about the NPTL patch (0001-Add-NPTL-support-for-m68k.patch,
>> http://marc.info/?l=linux-m68k&m=125447760017098&w=2)?
>
> As you're adding syscalls (which are shared with m68knommu), I'll have
> to ask whether
> you will make it work on nommu, too?
Yes, that's quite straight-forward so I'll try to post the patch tomorrow.
>
> Furthermore, when building for Sun3:
>
> arch/m68k/kernel/sys_m68k.c:706: warning: passing argument 1 of
> 'kunmap' from incompatible pointer type
> arch/m68k/kernel/sys_m68k.c:714: warning: passing argument 1 of
> 'kunmap' from incompatible pointer type
>
> Which looks like a problem with the Sun 3 version of pte_unmap().
Right. Sun3's implementation assumes that one can cast between (pte_t
*) and pgtable_t interchangeably; fwiw, I don't know if this is the case.
>
> I'm gonna add it to the m68k tree though, unless someone complains.
Thanks!
>
>> Also, this trivial fix (0004-Fix-m68k-s-asm-swab.h-for-ColdFire.patch,
>> http://marc.info/?l=linux-m68k&m=125447494213740&w=2) can go in.
>
> I want to run this one by the nommu people as well...
To illustrate the problem more clearly, here is the code that the patch
fixes:
#if defined (__mcfisaaplus__) || defined (__mcfisac__)
static inline __attribute_const__ __u32 __arch_swab32(__u32 val)
{
__asm__("byterev %0" : "=d" (val) : "0" (val));
return val;
}
#define __arch_swab32 __arch_swab32
#elif !defined(__uClinux__)
static inline __attribute_const__ __u32 __arch_swab32(__u32 val)
{
__asm__("rolw #8,%0; swap %0; rolw #8,%0" : "=d" (val) : "0" (val));
return val;
}
#define __arch_swab32 __arch_swab32
#endif
As far as I know, all non-ColdFire CPUs support rolw instruction, so
enabling it for uClinux should not be a problem. Regarding the ColdFire
CPUs, none of the CF ISAs include rolw, so the patch fixes the case of
building the kernel for MMU Linux ISA_B CPU, e.g., mcf547x/8x family.
--
Maxim Kuvyrkov
CodeSourcery
maxim@codesourcery.com
(650) 331-3385 x724
next prev parent reply other threads:[~2009-12-05 18:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-25 21:20 M68k tree updates Geert Uytterhoeven
2009-11-25 21:20 ` Geert Uytterhoeven
2009-11-30 13:43 ` Maxim Kuvyrkov
2009-11-30 13:43 ` Maxim Kuvyrkov
2009-12-04 19:57 ` Geert Uytterhoeven
2009-12-05 18:53 ` Maxim Kuvyrkov [this message]
2009-12-07 6:42 ` Greg Ungerer
2009-12-06 19:25 ` Maxim Kuvyrkov
2009-12-06 19:25 ` Maxim Kuvyrkov
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=4B1AAC16.5030107@codesourcery.com \
--to=maxim@codesourcery.com \
--cc=geert@linux-m68k.org \
--cc=gerg@snapgear.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=uclinux-dev@uclinux.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.