From: Angelo Dureghello <angelo@sysam.it>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: (No subject)
Date: Thu, 4 Oct 2018 17:08:27 +0200 [thread overview]
Message-ID: <20181004150827.GA15761@jerusalem> (raw)
In-Reply-To: <CAJTo0LakckQ+=uGaP9Nf-Mg4i53=7w4FsuhGY7bC1Tv3t7HNSQ@mail.gmail.com>
Hi Burton,
On Thu, Oct 04, 2018 at 02:55:37PM +0100, Burton, Ross wrote:
> I'm curious: the data sheet for the processor you mention in 4/4 says
> that it ha 64K of RAM. Are there other processors in the range, or
> have you done incredible things?
>
64KB is the internal static ram (SRAM), that's commonly 4 to 64K
for this family (i.e. some recent arm reachs 512K).
Then there is the built-in SDRAM/DDR2 controller :)
where i connect 128MB of DDR2(SDRAM), but other boards may have more.
Linux runs fine in ColdFire family from a long time. Initially only
non-MMU uClinux, now also the mainline kernel with MMU enabled.
Regards,
Angelo
> Ross
> On Thu, 4 Oct 2018 at 14:30, Angelo Dureghello <angelo@sysam.it> wrote:
> >
> >
> > This patch serie adds initial support for m68k architecture.
> > A Linux kernel build has been tested successfully using a local
> > meta layer, or kernel-yocto.
> > --
> > _______________________________________________
> > Openembedded-core mailing list
> > Openembedded-core@lists.openembedded.org
> > http://lists.openembedded.org/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2018-10-04 15:19 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 13:29 (No subject) Angelo Dureghello
2018-10-04 13:29 ` [PATCH 1/4] siteinfo: define data for m68k Angelo Dureghello
2018-10-04 13:29 ` [PATCH 2/4] kernel-arch.bbclass: add m68k to kernel arch map Angelo Dureghello
2018-10-04 13:29 ` [PATCH 3/4] conf/machine/include: add m68k architecture definitions Angelo Dureghello
2018-10-04 22:02 ` Richard Purdie
2018-10-04 22:56 ` Khem Raj
2018-10-04 13:29 ` [PATCH 4/4] conf/machine/include: add mcf5441x cpu type tuning Angelo Dureghello
2018-10-04 13:55 ` (No subject) Burton, Ross
2018-10-04 15:00 ` Andrea Adami
2018-10-04 15:08 ` Angelo Dureghello [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-30 15:50 Stephen K Jolley
2019-02-05 21:52 [PATCH] wpa_supplicant: Changed systemd template units Richard Purdie
2019-02-07 14:48 ` (No subject) Joshua DeWeese
2018-08-02 8:44 Nathan Rossi
2018-05-03 19:55 taborskikrzysztof
2017-11-27 16:20 Volker Vogelhuber
2017-05-07 1:33 [PATCH] openssh: Atomically generate host keys Joshua Watt
2017-05-09 2:24 ` (No subject) Joshua Watt
2016-07-22 10:35 Amarnath Valluri
2014-07-16 3:26 Shan Hai
2013-01-23 15:12 Belal, Awais
2013-01-21 10:49 Mike Looijmans
2013-01-21 11:26 ` Richard Purdie
2012-12-06 9:49 Lukas Bulwahn
2012-08-05 19:48 Javier Martinez Canillas
2012-08-06 14:59 ` Richard Purdie
2012-07-17 16:16 Ross Burton
2012-07-03 21:08 Mikhail Boiko
2012-06-21 21:36 Andreas Müller
2012-02-21 22:33 Andrei Gherzan
[not found] <4a795deb3789430487146a8425c1c337@DLEE74.ent.ti.com>
2011-08-27 4:38 ` Joel A Fernandes
2011-08-27 7:11 ` Koen Kooi
2011-08-27 3:26 Joel A Fernandes
2011-08-27 7:07 ` Koen Kooi
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=20181004150827.GA15761@jerusalem \
--to=angelo@sysam.it \
--cc=openembedded-core@lists.openembedded.org \
--cc=ross.burton@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox