ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Rob Landley <rob@landley.net>
Cc: Shuah Khan <shuah.kh@samsung.com>,
	"ksummit-discuss@lists.linuxfoundation.org"
	<ksummit-discuss@lists.linuxfoundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: [Ksummit-discuss] kselftest - What's in 3.17 and plans for 3.18 and beyond
Date: Mon, 18 Aug 2014 09:16:52 +0200	[thread overview]
Message-ID: <CAMuHMdWJFjziYGrtHUOac+guL-Kf=znTG9F5xW1T-0Tz6WP9Rg@mail.gmail.com> (raw)
In-Reply-To: <53F16E14.6030507@landley.net>

Hi Rob,

On Mon, Aug 18, 2014 at 5:08 AM, Rob Landley <rob@landley.net> wrote:
> (My dayjob has nothing to do with anything interesting, I'm paid to work
> on a a company's fork of a vendor's bsp fork of a really old kernel. For
> the new board, we just upgraded _to_ a version that's only 4 years old.
> When they finally ship there will be a nominal compliance tarball put on
> a website somewhere that nobody will ever look at or care about. I keep
> meaning to put up a patreon to see if people would be willing to sponsor
> me to spend all my time on actually _interesting_ stuff like this, but
> the chances are low enough I haven't bothered.)
>
>> I have been unable to find a working combination of kernel configuration,
>> qemu version, qemu command line, and root file system for m68k. Presumably
>> that must exist, because qemu supports m68k, I just have not been able
>> to figure out how to make it work.
>
> QEMU does not support m68k, qemu supports coldfire which is a nommu
> subset of m68k. But people have used the aranym emulator to fake an
> atari machine that _has_ run the root filesystems I've been building.
> (With a different kernel config, and a largeish patch for aranym devices
> that since went upstream. But it showed the basics were right.)

These days atari_defconfig in upstream should run fine on ARAnyM.

> The problem with using aranym is my setup expects a certain pile of
> devices. If /dev/console goes to stdin/stdout than it's easy to script
> the sucker with tcl/expect and log the output with "tee". If you have a

Ah, ARAnyM's nfcon only does stdout, not stdin.

> virtual network card you can move the heavy lifting of compilation
> outside the emulator with distcc hooked up to the cross compiler

But nfeth works fine.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

  reply	other threads:[~2014-08-18  7:16 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-07 14:36 Shuah Khan
2014-08-07 18:24 ` Bird, Tim
2014-08-07 19:59   ` Shuah Khan
2014-08-08  2:18 ` Masami Hiramatsu
2014-08-11 14:11   ` Shuah Khan
2014-08-11 16:13     ` Masami Hiramatsu
2014-08-12 13:00       ` Grant Likely
2014-08-12 16:15         ` Guenter Roeck
2014-08-12 16:21           ` Masami Hiramatsu
2014-08-12 16:51             ` Geert Uytterhoeven
2014-08-12 17:15             ` Theodore Ts'o
2014-08-12 16:23           ` Grant Likely
2014-08-12 16:49             ` Mark Brown
2014-08-13  6:26               ` Grant Likely
2014-08-13 10:40                 ` Mark Brown
2014-08-13 11:12                   ` Geert Uytterhoeven
2014-08-13 12:42                     ` Mark Brown
2014-08-13 13:08                       ` Geert Uytterhoeven
2014-08-13 15:00                   ` Kevin Hilman
2014-08-13 16:40                     ` Olof Johansson
2014-08-13 17:11                       ` Mark Brown
2014-08-12 17:46             ` Tim Bird
2014-08-12 18:06               ` Steven Rostedt
2014-08-12 20:52                 ` Tim Bird
2014-08-14 16:35                 ` Grant Likely
2014-08-12 17:30           ` Andy Lutomirski
2014-08-12 16:34         ` Shuah Khan
2014-08-13  8:35         ` Linus Walleij
2014-08-13 16:11           ` Guenter Roeck
2014-08-13 16:16             ` Andy Lutomirski
2014-08-13 16:44               ` Bird, Tim
2014-08-13 17:07                 ` Grant Likely
2014-08-13 17:10                   ` Andy Lutomirski
2014-08-13 17:10                 ` Guenter Roeck
2014-08-18  3:10               ` Rob Landley
2014-08-18  3:08             ` Rob Landley
2014-08-18  7:16               ` Geert Uytterhoeven [this message]
2014-08-13 16:45           ` Masami Hiramatsu
2014-08-18  3:18             ` Rob Landley
2014-08-13 15:06         ` Aneesh Kumar K.V

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='CAMuHMdWJFjziYGrtHUOac+guL-Kf=znTG9F5xW1T-0Tz6WP9Rg@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=rob@landley.net \
    --cc=shuah.kh@samsung.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox