public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Angelo Dureghello <angelo@sysam.it>
To: linux-m68k@vger.kernel.org
Cc: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Subject: Re: my contribution
Date: Wed, 10 Feb 2016 12:04:15 +0100	[thread overview]
Message-ID: <56BB192F.7010306@sysam.it> (raw)
In-Reply-To: <56BB0803.9090100@physik.fu-berlin.de>

Hi Adrian,

On 10/02/2016 10:50, John Paul Adrian Glaubitz wrote:
> On 02/10/2016 10:29 AM, Geert Uytterhoeven wrote:
>>> Join debian-68k@lists.debian.org:
>>>
>>>> https://lists.debian.org/debian-68k/
>>>
>>> And help fixing packages that don't build on m68k.
>>
>> IIRC, Debian/m68k doesn't run on Coldfire m5307.
>
> Oops, I missed that part. I thought he was talking about m68k
> in general. Can ColdFire systems still be bought new?
>

Well, afaik, about ColdFire cpu's, there is a product-life table in 
Freescale (now NXP) for each model. Some older coldfire cpu's are 
entering in the production "stop", even if you can still find them on 
many resellers.
But the most recent as mcf5441x should have still 10 years of availability.

> Adrian
>

Best regards
Angelo Dureghello

  reply	other threads:[~2016-02-10 11:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09 22:14 my contribution Angelo Dureghello
2016-02-09 22:40 ` John Paul Adrian Glaubitz
2016-02-10  9:29   ` Geert Uytterhoeven
2016-02-10  9:34     ` Philippe De Muyter
2016-02-10  9:50     ` John Paul Adrian Glaubitz
2016-02-10 11:04       ` Angelo Dureghello [this message]
2016-02-10  9:51   ` Angelo Dureghello
2016-02-10 11:51     ` Greg Ungerer
2016-02-10 12:00       ` Angelo Dureghello

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=56BB192F.7010306@sysam.it \
    --to=angelo@sysam.it \
    --cc=glaubitz@physik.fu-berlin.de \
    --cc=linux-m68k@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox