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: Fri, 16 Dec 2011 20:57:01 +1000	[thread overview]
Message-ID: <4EEB23FD.9090904@snapgear.com> (raw)
In-Reply-To: <CAMuHMdU+VCVxnawb8DHmZp1EfBGW6T5D0WyXRXpo8bj1bJZ+pg@mail.gmail.com>

Hi Daniel,

> On Fri, Dec 16, 2011 at 06:37, Daniel Palmer<me@danielpalmer.co.uk>  wrote:
>> I'm building a custom machine based around a 68sec000 (Fully static 68ec000).
>> The "board" is a bunch of parts at the moment but I have written a workable
>> simulator for the machine which I am using as a testbed for testing things
>> like my custom video, DMA controller etc before creating the hardware versions
>> in VHDL.
>>
>> I'm interested in getting mmu-less m68k linux (what used to be known as
>> uclinux I guess, seems to be known as m68k/nommu now) running on the simulator
>> and later on the real hardware.

uclinux is/was mmuless support. m68knommu used to be the arch name for
m68k without mmu support. I just use Linux now, it has all been in
mainline for so long now.


>>  From what I can tell the nommu m68k port is still active. But does it actually
>> work? All the details on similar hardware (like the older Palm pilots, Atari
>> machines) is pretty ancient, around 2.0. Does anyone have a machine running a
>> recent kernel? Were there issues getting it running?

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 digging in the source and doesn't look like it should be too
>> difficult to add the specifics for my machine.. I have a 16550 style UART
>> emulated for I/O so I don't need to write a framebuffer driver at the moment.
>> I'm open to any suggestions people have on how to approach this though.

With the m68k and m68knommu arch code now merged it shouldn't
be too hard to enable/configure all the pieces you have. Might take
a little hacking to make it work, but it should be close.

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: Fri, 16 Dec 2011 20:57:01 +1000	[thread overview]
Message-ID: <4EEB23FD.9090904@snapgear.com> (raw)
In-Reply-To: <CAMuHMdU+VCVxnawb8DHmZp1EfBGW6T5D0WyXRXpo8bj1bJZ+pg@mail.gmail.com>

Hi Daniel,

> On Fri, Dec 16, 2011 at 06:37, Daniel Palmer<me@danielpalmer.co.uk>  wrote:
>> I'm building a custom machine based around a 68sec000 (Fully static 68ec000).
>> The "board" is a bunch of parts at the moment but I have written a workable
>> simulator for the machine which I am using as a testbed for testing things
>> like my custom video, DMA controller etc before creating the hardware versions
>> in VHDL.
>>
>> I'm interested in getting mmu-less m68k linux (what used to be known as
>> uclinux I guess, seems to be known as m68k/nommu now) running on the simulator
>> and later on the real hardware.

uclinux is/was mmuless support. m68knommu used to be the arch name for
m68k without mmu support. I just use Linux now, it has all been in
mainline for so long now.


>>  From what I can tell the nommu m68k port is still active. But does it actually
>> work? All the details on similar hardware (like the older Palm pilots, Atari
>> machines) is pretty ancient, around 2.0. Does anyone have a machine running a
>> recent kernel? Were there issues getting it running?

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 digging in the source and doesn't look like it should be too
>> difficult to add the specifics for my machine.. I have a 16550 style UART
>> emulated for I/O so I don't need to write a framebuffer driver at the moment.
>> I'm open to any suggestions people have on how to approach this though.

With the m68k and m68knommu arch code now merged it shouldn't
be too hard to enable/configure all the pieces you have. Might take
a little hacking to make it work, but it should be close.

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

  reply	other threads:[~2011-12-16 10:57 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 [this message]
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
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=4EEB23FD.9090904@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.