From mint-bounce@lists.fishpool.fi Sat May 2 10:11:17 2009 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:from:to :in-reply-to:content-type:content-transfer-encoding:mime-version :subject:date:references:x-mailer; bh=KBpy9br5ABf6d0p6rQJtEeYcbpYdl5nBFBqtjuSQQPM=; b=sSwOstPDp2iZ8n4Jqbykz5bo4xFY+U8y437FVutl6jxXyPruwDnAhn0q6gCqreHbl6 XwAQ03MsLivCZ800+f0nPLtv3WOlKjALSrEW8jSVHMuv4jbelukuREYYJUCT8KQC3Zd5 wgHlV1FRtfAWANZKVrXX72Qpz52ZgFOXRdsig= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:from:to:in-reply-to:content-type :content-transfer-encoding:mime-version:subject:date:references :x-mailer; b=m3vNbhwF3/x0vlRGIQG0q2z4eitBxaBN3w07HrJypDDHURftt7m0hgqHE4nUQ6Qbo9 4AZ1y6KXeqI5Ap7wYmkaL2YErBx62cLCeRVX4e9eclmFrBBpIQOP+aEq/pFmMnixBnOW c80LSXV/9WSvwyrqinA8GmESgRJeAzr0WSp5o= Message-Id: <0CD469F3-E167-449D-93AA-4427F345F12C@gmail.com> From: Peter Persson To: MiNT-List In-Reply-To: <609C3308-4B63-4A2E-BEEC-22D7ED26D215@mubf.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Mime-Version: 1.0 (Apple Message framework v930.3) Subject: Re: [MiNT] EmuTOS for ColdFire Date: Sat, 2 May 2009 16:07:37 +0200 References: <68EF70E911F44CB4AC7C90F286219FC1@joevenlt> <49F8D39B.3080303@chello.nl> <3324014950.7760261950@[192.168.178.12]> <20090501111726.70e28da6@phineus> <3324108430.345782912@[192.168.178.12]> <49FC2D44.5040707@freesbee.fr> <609C3308-4B63-4A2E-BEEC-22D7ED26D215@mubf.de> X-Mailer: Apple Mail (2.930.3) X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: pep.fishmoose@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.sparemint.org id n42EBGaN003699 Hi, Line-A constitutes a pitfall here. This range of opcodes are used for MAC-instructions on the ColdFire. Didier solves this by replacing $a000 with an unused TRAP. This trap should probably be implemented in freemint for "standard" 68k machines as well. ColdFire stuff should run fairly well on 060 CPUs, since AFAIK complex instructions and address modes are slower than load/store instructions on the 060. Note: Line-A is a big no-no, I know that, but a lot of applications still rely on the $A000 opcode for some reason. Maybe this is part of some old startup vod or whatever. In a perfect universe, the best way to remedy this would be in the application itself. However, I think the only realistic solution would be to add the TRAP call to the OS instead, because this makes it very easy to patch the applications in question for ColdFire compatibility. -- PeP 2 maj 2009 kl. 13.38 skrev Markus Fröschle: > > Am 02.05.2009 um 13:23 schrieb Vincent Rivière: > >>> I know that, but is a CodFire between a 68000 and 68010? That is >>> what I don´t understand. > > Something which hasn't been mentioned yet, but is very important in > my opinion when it comes to TOS/MinT compatibility: > > Although running MC680xx programs on a CF v4e CPU requires a CPU > emulation library, this is not absolutely necessary the other way > round. The Coldfire instruction set is more like a subset of the > 680xx instruction set than an enhancement and, with some care (only > using adressing modes and instructions which are available on both > processors), it should be possible to write programs which run > natively on 680xx as well as Coldfire processor architectures > (although they might not run as fast on the older architecture than > they would if written exclusively for them). >