Hi Luis,
On 04/05/12 19:48, Luis Alves wrote:
On Fri, May 4, 2012 at 7:53 AM, Greg Ungerer<gerg@xxxxxxxxxxxx> 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@xxxxxxxxxxxx
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
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html