All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 22 Dec 2011 17:22:48 +1000	[thread overview]
Message-ID: <4EF2DAC8.3060409@snapgear.com> (raw)
In-Reply-To: <201112181824.56271.me@danielpalmer.co.uk>

Hi Daniel,

On 19/12/11 12:24, Daniel Palmer wrote:
> Sorry for not replying sooner. Too much work :(
>
>> 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

Yep, a couple of issues when building for the Palm/Pilot.
I just sent a couple of patches to m68k-linux that fix the main
problems. You will also want to disable CONFIG_FW_LOADER if you
have that enabled.

After that I can compile it all the way (I am building on 3.2-rc6).
No idea if it works though.

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

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: Thu, 22 Dec 2011 17:22:48 +1000	[thread overview]
Message-ID: <4EF2DAC8.3060409@snapgear.com> (raw)
In-Reply-To: <201112181824.56271.me@danielpalmer.co.uk>

Hi Daniel,

On 19/12/11 12:24, Daniel Palmer wrote:
> Sorry for not replying sooner. Too much work :(
>
>> 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

Yep, a couple of issues when building for the Palm/Pilot.
I just sent a couple of patches to m68k-linux that fix the main
problems. You will also want to disable CONFIG_FW_LOADER if you
have that enabled.

After that I can compile it all the way (I am building on 3.2-rc6).
No idea if it works though.

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:[~2011-12-22  7:26 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
2011-12-21 11:49         ` Greg Ungerer
2011-12-22  7:22       ` Greg Ungerer [this message]
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=4EF2DAC8.3060409@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.