From: Arnd Bergmann <arnd@arndb.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-arm-kernel@lists.infradead.org
Cc: Madhavi Manchala <madhavi.linux@gmail.com>,
linux-arch@vger.kernel.org, gregkh@suse.de,
prasadjoshi124@gmail.com,
uClinux development list <uclinux-dev@uclinux.org>
Subject: Re: Support for ARM940T core Samsung S3C2510A MCU under Linux
Date: Sat, 19 Mar 2011 21:14:04 +0100 [thread overview]
Message-ID: <201103192114.05164.arnd@arndb.de> (raw)
In-Reply-To: <AANLkTimPoEi+XLUJgza-b_gXbd4kCGpF93MySAR0ZRvT@mail.gmail.com>
On Saturday 19 March 2011, Geert Uytterhoeven wrote:
> On Sat, Mar 19, 2011 at 10:53, Madhavi Manchala <madhavi.linux@gmail.com> wrote:
> > I have one basic question about the architecture files in Linux
> > kernels. We have a board with Samsung S3C2510A MCU (ARM940T core)
> > which is a no-mmu based CPU. I heard that "there was not a lot of ARM
> > no-mmu support at the moment" from Ben Dooks.
> >
> > So, I started developing the architecture files for my Samsung
> > S3C2510A MCU (ARM940T core) by looking at the existing S3C2410A
> > (ARM920 core) architecture files. Is this my porting (developing the
> > architecture files) correct?
> >
> > How can I port the Linux on to my board which has a Samsung S3C2510A
> > MCU (ARM940T core) which is a NO-MMU based CPU?
> >
> > Please suggest me. It would be appreciated your help / suggestions.
>
> I think the uClinux mailing list (CCed) is a more appropriate mailing list for
> your questions.
It depends. Any questions regarding the ARM kernel should be on the
arm-linux-kernel (also CCed now), since the nommu support is merged
with the mainline kernel.
uClinux seems to be rather focused on m68knommu (coldfire) these days,
and contains both a kernel and user space. The last uClinux release
containst some changes for Samsung platforms (s3c24a0, s3c3410,
s3c44b0x and s5c7375). It's probably a good idea to look at that
code for reference, but I would suggest integrating the code for
your platform in the upstream tree directly.
I could not find a git tree for uClinux that contains any recent
kernel. Does that exist?
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Support for ARM940T core Samsung S3C2510A MCU under Linux
Date: Sat, 19 Mar 2011 21:14:04 +0100 [thread overview]
Message-ID: <201103192114.05164.arnd@arndb.de> (raw)
In-Reply-To: <AANLkTimPoEi+XLUJgza-b_gXbd4kCGpF93MySAR0ZRvT@mail.gmail.com>
On Saturday 19 March 2011, Geert Uytterhoeven wrote:
> On Sat, Mar 19, 2011 at 10:53, Madhavi Manchala <madhavi.linux@gmail.com> wrote:
> > I have one basic question about the architecture files in Linux
> > kernels. We have a board with Samsung S3C2510A MCU (ARM940T core)
> > which is a no-mmu based CPU. I heard that "there was not a lot of ARM
> > no-mmu support at the moment" from Ben Dooks.
> >
> > So, I started developing the architecture files for my Samsung
> > S3C2510A MCU (ARM940T core) by looking at the existing S3C2410A
> > (ARM920 core) architecture files. Is this my porting (developing the
> > architecture files) correct?
> >
> > How can I port the Linux on to my board which has a Samsung S3C2510A
> > MCU (ARM940T core) which is a NO-MMU based CPU?
> >
> > Please suggest me. It would be appreciated your help / suggestions.
>
> I think the uClinux mailing list (CCed) is a more appropriate mailing list for
> your questions.
It depends. Any questions regarding the ARM kernel should be on the
arm-linux-kernel (also CCed now), since the nommu support is merged
with the mainline kernel.
uClinux seems to be rather focused on m68knommu (coldfire) these days,
and contains both a kernel and user space. The last uClinux release
containst some changes for Samsung platforms (s3c24a0, s3c3410,
s3c44b0x and s5c7375). It's probably a good idea to look at that
code for reference, but I would suggest integrating the code for
your platform in the upstream tree directly.
I could not find a git tree for uClinux that contains any recent
kernel. Does that exist?
Arnd
next prev parent reply other threads:[~2011-03-19 20:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-19 9:53 Support for ARM940T core Samsung S3C2510A MCU under Linux Madhavi Manchala
2011-03-19 10:46 ` Geert Uytterhoeven
2011-03-19 20:14 ` Arnd Bergmann [this message]
2011-03-19 20:14 ` Arnd Bergmann
2011-03-21 11:37 ` Greg Ungerer
2011-03-21 11:37 ` Greg Ungerer
2011-03-21 12:20 ` Arnd Bergmann
2011-03-21 12:20 ` Arnd Bergmann
2011-03-22 11:09 ` Greg Ungerer
2011-03-22 11:09 ` Greg Ungerer
-- strict thread matches above, loose matches on Subject: below --
2011-03-18 15:54 Madhavi Manchala
2011-03-21 11:27 ` Greg Ungerer
2011-03-22 12:43 ` Madhavi Manchala
2011-03-22 13:12 ` Arnd Bergmann
2011-03-22 13:12 ` Arnd Bergmann
2011-03-23 12:07 ` Greg Ungerer
2011-03-23 12:36 ` Madhavi Manchala
2011-03-23 13:18 ` Greg Ungerer
2011-03-17 9:18 Madhavi Manchala
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=201103192114.05164.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=geert@linux-m68k.org \
--cc=gregkh@suse.de \
--cc=linux-arch@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=madhavi.linux@gmail.com \
--cc=prasadjoshi124@gmail.com \
--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.