qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>, detaolb-devel@lists.sourceforge.net
Subject: Re: [Qemu-devel] ANN: DetaolB v0.4 is released
Date: Tue, 10 Jul 2007 13:34:57 -0400	[thread overview]
Message-ID: <200707101334.57862.rob@landley.net> (raw)
In-Reply-To: <f43fc5580706301015s59db7e8ahd9638b8054a00b44@mail.gmail.com>

On Saturday 30 June 2007 13:15:44 Blue Swirl wrote:
> On 6/30/07, Thiemo Seufer <ths@networkno.de> wrote:
> > Johannes Schindelin wrote:
> > > Hi,
> > >
> > > On Sat, 30 Jun 2007, Blue Swirl wrote:
> > > > On 6/30/07, Christian MICHON <christian.michon@gmail.com> wrote:
> > > > > DetaolB aimed to be a "much-less-than-a-floppy" x86 linux live
> > > > > distro. Now, it's evolving more into "a-la-slax" type of distro.
> > > >
> > > > As the number of Sparc32 distributions keeps approaching zero, could
> > > > you consider porting DetaolB to non-x86 CPUs?
> > >
> > > Yes, please!
> >
> > The reason why distributions drop sparc32 is the unmaintained kernel.
> > Nobody stepped up for Linux kernel maintenance in the last years.
> > Debian managed to keep up a sort-of working kernel for the last
> > release, the people who put their time into it are disinclined to
> > repeat this exercise.
>
> But there is a difference in maintaining a kernel suitable for high
> quality distribution with over 18733 packages working in different
> real hardware, versus a test/evaluation distribution with <30 packages
> running on Qemu. I'd see that as an "enhanced qemu-tests.tar.gz".

Just FYI, Firmware Linux builds for sparc and has for months now.

http://landley.net/code/firmware

Go "./build.sh sparc", and wait a bit.  It even generates a run-sparc.sh in 
the build directory that'll invoke qemu against the kernel and ext2 image it 
generated.

That creates a sparc cross compiler, uses it to build a root filesystem 
containing a native toolchain for sparc, and packages it into an ext2 image.  
Over on arm I've built binutils and gcc natively inside the emulator.

The sparc platform has a problem that if I boot with init as a "hello world" 
program everything behaves as expected (there are two in the image for 
testing purposes, /tools/bin/hello-dynamic and /tools/bin/hello-static).  But 
if you boot with init=/tools/bin/bash it hangs.  And so do the busybox 
shells.

I think it's a uClibc bug on sparc, but haven't made time to track it down.  
Either that or the kernel needs something _weird_ for console initialization.  
(The cross-compiler and kernel seem to be working fine...)

You can try it out yourself by downloading all the *sparc* files from 
http://landley.net/code/firmware/downloads/images and then running:

qemu-system-sparc -nographic -no-reboot -hda image-sparc.ext2 -kernel \
  zImage-sparc -append 'rw init=/tools/bin/hello-dynamic panic=1 \
  PATH=/tools/bin root=/dev/sda console=ttyS0'

That prints "Hello world!", panics, and exits.

./run-sparc.sh does the exact same command line with "init=/tools/bin/sh" 
(bash 2.05b), which hangs.  Note that init=/tools/bin/ash (busybox ash) does 
the same thing.  Haven't debugged beyond that yet...

Rob

P.S.  I gave a tutorial about this system at OLS, and my lecture notes are at 
http://landley.net/ols/ols2007/tutorial.txt
-- 
"One of my most productive days was throwing away 1000 lines of code."
  - Ken Thompson.

  reply	other threads:[~2007-07-10 17:35 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-29 23:58 [Qemu-devel] ANN: DetaolB v0.4 is released Christian MICHON
2007-06-30  7:47 ` Blue Swirl
2007-06-30 10:36   ` Johannes Schindelin
2007-06-30 10:51     ` Thiemo Seufer
2007-06-30 12:07       ` Christian MICHON
2007-06-30 17:15       ` Blue Swirl
2007-07-10 17:34         ` Rob Landley [this message]
2007-07-10 18:30           ` Blue Swirl
2007-07-10 19:42             ` Rob Landley
2007-07-11 11:17               ` Blue Swirl
2007-07-11 13:34                 ` [Detaolb-devel] " Christian MICHON
2007-07-11 14:20                   ` Christian MICHON
2007-07-11 17:33                   ` Rob Landley
2007-07-11 20:20                     ` Christian MICHON
2007-07-11 17:38                 ` Rob Landley
2007-07-11 20:26                   ` [Detaolb-devel] " Christian MICHON
2007-06-30 12:10     ` Christian MICHON
2007-07-04 18:30   ` Christian MICHON
2007-07-04 18:54     ` Blue Swirl
2007-07-04 19:45       ` Christian MICHON
2007-07-04 20:18         ` Blue Swirl
2007-07-04 20:30           ` Christian MICHON
2007-07-04 20:52             ` Blue Swirl
2007-07-04 21:04               ` Christian MICHON
2007-07-05 12:41                 ` Christian MICHON
2007-07-04 20:25         ` Andreas Färber
2007-07-04 20:32           ` Christian MICHON
2007-07-06 15:07             ` Rob Landley
2007-07-04 19:50     ` Cedric Hombourger
2007-07-04 19:54       ` Cedric Hombourger
2007-07-10 20:32         ` Bernhard Fischer
2007-07-10 20:36           ` Christian MICHON
2007-07-04 20:11       ` Christian MICHON
2007-07-05 19:23         ` Rob Landley
2007-07-05 20:28           ` Christian MICHON

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=200707101334.57862.rob@landley.net \
    --to=rob@landley.net \
    --cc=blauwirbel@gmail.com \
    --cc=detaolb-devel@lists.sourceforge.net \
    --cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).