linux-kernel - Re: Porting m68k/nommu to a new board.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 21 Dec 2011 21:49:03 +1000
From:	Greg Ungerer <gerg@...pgear.com>
To:	Daniel Palmer <me@...ielpalmer.co.uk>
CC:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	<linux-kernel@...r.kernel.org>,
	Linux/m68k <linux-m68k@...r.kernel.org>,
	uClinux development list <uclinux-dev@...inux.org>
Subject: Re: Porting m68k/nommu to a new board.

Hi Daniel,

On 12/19/2011 12:24 PM, Daniel Palmer wrote:
> Sorry for not replying sooner. Too much work :(

No problem :-)


>> I run on ColdFire parts all the time. Right up to 3.2-rc5 :-)
>> It works great. But I don't have or regularly use any original m68k
>> core hardware. I occasionally compile for the 68328 target, so it
>> will compile, can't be sure if it still runs though.
>
> I did a bit of poking around, I couldn't get the 68328 target to build.. I was
> going to have a play with it in xcopilot. It complains about some linker
> section missing .. but I started hacking it up anyway.. at the moment m68328
> depends on m68000 which in turn causes the 68328 platform stuff to build.
> So I worked that a little so that 68000 is its own target that builds with
> some minimal startup code (so I can dump the resulting image into my emulator
> and see how far it gets.. I have a gdbserver in my emulator so I can fully see
> whats happening). I haven't managed to get an image out of it yet.. but I will
> have another go at the weekend.

Sounds good. Keep us posted on how you go.


> I'm going to get an old palm pilot off of ebay and see if I can get the 68328
> target running too.

Yeah, would be really nice to know what state the 68328 code is in.

I will compile it again too, and see if anything is obviously broken at
the moment.

Regards
Greg


------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@...pgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close,                            FAX:         +61 7 3891 3630
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/