public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: angelo <angelo70@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] coldfire support
Date: Thu, 25 Feb 2010 12:16:56 +0100	[thread overview]
Message-ID: <4B865C28.9060500@gmail.com> (raw)
In-Reply-To: <a90206391002242227m71c45097tacf8da5ffdaf6ac@mail.gmail.com>

Hi all,

so unfortunately (for me), MCF5307 is still not supported.
I took a fast look inside these supported models, to start up a new 5307 
support,
but every starting point, for the specific 5307 internal memory layout, 
is too different, and can't have the time to accomplish it now.

Hope that someday it will be added also.

greetings,
Angelo



TC Liew wrote:
> Thirumalai,
>
> These ColdFire processors (MCF52277, MCF5235, MCF5249, MCF5253,
> MCF5271, MCF5272, MCF5275, MCF5282, MCF5329, MCF5373, MCF5445x, and
> MCF547x_8x) are supported by u-boot.
>
> Like Wolfgang Wegner mentioned, you can download the ToolChain at
> http://www.codesourcery.com/sgpp/lite/coldfire.
>
> As for the Linux, we use different repository site.
> http://www.bitshrine.org/gpp/
>
> Regards,
> TsiChung
>
> On Mon, Feb 22, 2010 at 5:00 AM, Thirumalai
> <thirumalai.p@datapatterns.co.in> wrote:
>   
>> Hi denx,
>>    I just want to know whether the coldfire processor is supported by
>> u-boot and what toolchains need to be used for compilation. Whether ELDK
>> will support or not ?
>>
>> Thank you
>> Thirumalai
>>
>> _______________________________________________
>> U-Boot mailing list
>> U-Boot at lists.denx.de
>> http://lists.denx.de/mailman/listinfo/u-boot
>>
>>     
> _______________________________________________
> U-Boot mailing list
> U-Boot at lists.denx.de
> http://lists.denx.de/mailman/listinfo/u-boot
>   

      reply	other threads:[~2010-02-25 11:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-22 11:00 [U-Boot] coldfire support Thirumalai
2010-02-22 12:08 ` Wolfgang Wegner
2010-02-25  6:27 ` TC Liew
2010-02-25 11:16   ` angelo [this message]

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=4B865C28.9060500@gmail.com \
    --to=angelo70@gmail.com \
    --cc=u-boot@lists.denx.de \
    /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