From: Greg Ungerer <gerg@snapgear.com>
To: Daniel Palmer <me@danielpalmer.co.uk>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
linux-kernel@vger.kernel.org,
Linux/m68k <linux-m68k@vger.kernel.org>,
uClinux development list <uclinux-dev@uclinux.org>
Subject: Re: Porting m68k/nommu to a new board.
Date: Wed, 21 Dec 2011 21:49:03 +1000 [thread overview]
Message-ID: <4EF1C7AF.8040801@snapgear.com> (raw)
In-Reply-To: <201112181824.56271.me@danielpalmer.co.uk>
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@snapgear.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
WARNING: multiple messages have this Message-ID (diff)
From: Greg Ungerer <gerg@snapgear.com>
To: Daniel Palmer <me@danielpalmer.co.uk>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
<linux-kernel@vger.kernel.org>,
Linux/m68k <linux-m68k@vger.kernel.org>,
uClinux development list <uclinux-dev@uclinux.org>
Subject: Re: Porting m68k/nommu to a new board.
Date: Wed, 21 Dec 2011 21:49:03 +1000 [thread overview]
Message-ID: <4EF1C7AF.8040801@snapgear.com> (raw)
In-Reply-To: <201112181824.56271.me@danielpalmer.co.uk>
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@snapgear.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
next prev parent reply other threads:[~2011-12-21 11:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 5:37 Porting m68k/nommu to a new board Daniel Palmer
2011-12-16 7:03 ` Geert Uytterhoeven
2011-12-16 10:57 ` Greg Ungerer
2011-12-16 10:57 ` Greg Ungerer
2011-12-19 2:24 ` Daniel Palmer
2011-12-21 11:49 ` Greg Ungerer [this message]
2011-12-21 11:49 ` Greg Ungerer
2011-12-22 7:22 ` Greg Ungerer
2011-12-22 7:22 ` Greg Ungerer
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=4EF1C7AF.8040801@snapgear.com \
--to=gerg@snapgear.com \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=me@danielpalmer.co.uk \
--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.