All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Luis Alves <ljalvs@gmail.com>
Cc: uClinux development list <uclinux-dev@uclinux.org>,
	linux-m68k@vger.kernel.org, gerg@uclinux.org
Subject: Re: [PATCH 1/1] 68000 code integration
Date: Tue, 8 May 2012 12:56:28 +1000	[thread overview]
Message-ID: <4FA88B5C.3040406@snapgear.com> (raw)
In-Reply-To: <CAGj5WxA=uO0Pkbn5UM4Tu3oGFO9JAXA7mEiwNQ3cuiOHM2b+hg@mail.gmail.com>

Hi Luis,

On 04/05/12 19:48, Luis Alves wrote:
> On Fri, May 4, 2012 at 7:53 AM, Greg Ungerer<gerg@snapgear.com>  wrote:
[snip]
>> An observation from the patch, the 68000/entry-*.S files all look
>> quite similar. Is there any way they can be merged into a single
>> file?
>
> I'm just noticed that accidentally I've added the 'entry-68000.S'!
> This file should be removed.
>
> About merging, yes I plan to do it later. The thing is that in my
> first attempt of running this kernel in the 68000 the entry code from
> the  68328 had a strange behavior (you should remember debugging this
> with me - lots of softlocks).
> Then I've used the entry.S from coldfire sources as base and it worked smooth.

I suspect the existing 68x328 code is broken, and we probably want
to use your fixed and working version of this entry.S for all.

I don't have any real 68328 based hardware, but many years ago
people used the xcopilot simulator for 68328 testing. I don't know
what the state of it these days, but it may still be useful.

Regards
Greg


------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close                             FAX:         +61 7 3217 5323
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com

      parent reply	other threads:[~2012-05-08  3:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1335818553-14402-1-git-send-email-ljalvs@gmail.com>
     [not found] ` <4FA37D01.2000107@snapgear.com>
2012-05-04  9:48   ` [PATCH 1/1] 68000 code integration Luis Alves
2012-05-04 10:58     ` Geert Uytterhoeven
2012-05-04 11:53       ` Luis Alves
2012-05-06 20:46         ` Geert Uytterhoeven
2012-05-08  2:56     ` Greg Ungerer [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=4FA88B5C.3040406@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=gerg@uclinux.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=ljalvs@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.