public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: U-Boot for Motorola M5272C3 and M5282EVB
Date: Mon, 08 Dec 2003 22:58:12 +0100	[thread overview]
Message-ID: <20031208215817.CE70BC5F5F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Mon, 08 Dec 2003 22:34:30 +0100." <3FD4EE66.6080301@metrowerks.com>

Dear Bernhard,

in message <3FD4EE66.6080301@metrowerks.com> you wrote:
> 
> I have to admit that the coldfire u-boot port was a
> quick-hack intended as prototype that at least was
> usefull for me :-)

This is exactly what I though when I saw the code ;-)

> Unforntunatly i'm not involved in any Coldfire related
> development at the moment and pretty busy with other
> projects, so i won't have the time right now to sort
> out the issue you have discovered.

Understood.

> But i will at least try to provide some usefull
> comments for each of the items listed below, so that
> other Coldfire/u-boot users can start cleaning things
> up, so that the patch will be free of any licencing
> or technical issues. In this context, please feel
> free to redistribute this mail to whomever you think
> it might be usefull for.

I re-sent it to the U-Boot-Users mailing list so others interested in
this stuff can pick up from what we have now.

> Although certain files are even holding PPC assembly
> instructions, or other obviously PPC related routines,
> the bootloader will still compile and work (IMHO
> pretty well) for the coldfire because the appropriate
> code will not be compiled (ifdef'ed out) or is just
> dead code in the resulting binary.

This is what I imageined, but the code init's current form is a mess.
It needs to be cleaned up before I'm willing to check it in.

>  > Please provide a doc/README.Coldfire which explains this procedure.
> 
> I will add appropriate notes to the existing coldfire specfic
> installation instruction when the cleanups have been finished.

Thanks.

> To be serious: as the file name of the patch indicates, it
> was intended to be applied for u-boot-0.4.0. I didn't have
> done anything on it since then ...

Well, actually there is very little difference between applying  your
patch to U-Boot 0.4.0 or 1.1.0 ...

...

> As indicated above: i can't afford to spend time on the cleanup work,
> right now, sorry. However, if somebody is volunteering to do the
> necessary cleanups, then i will try to assist her or him as good
> as possible.

OK, so we're looking for a volunteer to cleanup the  open  issies  of
the Coldfire port now.


Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
If you're not part of the solution, then you're part of the  precipi-
tate.

  reply	other threads:[~2003-12-08 21:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20031208011928.E2B75C5F5F@atlas.denx.de>
2003-12-08 21:34 ` [U-Boot-Users] Re: [uClinux-dev] [Announcement] U-Boot for Motorola M5272C3 and M5282EVB Bernhard Kuhn
2003-12-08 21:58   ` Wolfgang Denk [this message]
2003-12-09  1:09     ` [U-Boot-Users] BUBINGA405EP Platform Bruce Boettjer
2003-12-09  8:34       ` Stefan Roese
2003-12-11 19:40         ` Bruce Boettjer
2003-12-12  8:10           ` Stefan Roese

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=20031208215817.CE70BC5F5F@atlas.denx.de \
    --to=wd@denx.de \
    --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