qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Artyom Tarasenko <atar4qemu@googlemail.com>
To: Rob Landley <rob@landley.net>
Cc: Blue Swirl <blauwirbel@gmail.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: Fun with sparc (was Re: qemu-ppc can't run static uClibc binaries.)
Date: Sat, 20 Feb 2010 22:59:38 +0100	[thread overview]
Message-ID: <fb8d4f71002201359s51286e07x773cd2abcfad4ec2@mail.gmail.com> (raw)
In-Reply-To: <201002201238.17811.rob@landley.net>

2010/2/20 Rob Landley <rob@landley.net>:
> On Saturday 20 February 2010 11:34:44 Blue Swirl wrote:
>> On 2/20/10, Rob Landley <rob@landley.net> wrote:
>> >  I don't understand what's going wrong here.  Did the kernel break on
>> > sparc sometime between 2.6.18 and 2.6.32 and nobody noticed?  Is sparc
>> > using software emulated floating point at the kernel level and that's
>> > configured as a module?  (Except I don't think busybox ls uses floating
>> > point...)
>>
>> Sparc32 is not maintained anymore so maybe it broke at some point.
>> There was some discussion a few years ago.
>
> Not maintained on the Linux kernel side, or not maintained under qemu?  It
> seems to be working under debian, but the 2.6.18 kernel is from 2006.
>
>> >  Do any sparc people understand what's going on here?  My next step is to
>> > grab a 2.6.18 kernel and try to get _that_ to work with the tweaked
>> > debian config (and an ext2 root filesystem since squashfs wasn't merged
>> > back then and had a format change when it was merged).  But I'm mostly
>> > flailing around blind here...
>>
>> I'm also trying different kernels using my .config. But already 2.6.12
>> hangs in ESP probe.
>
> I've got 2.6.32 booting to a command prompt (albeit with serial console and
> intentionall restricted set of hardware).  But then it misbehaves.
>
> I'll try getting 2.6.18 to build with a known .config, and then bisect forward
> if that seems to work...

You can also try aurora linux. They had a bit newer kernel. Don't know
how stable is it on a real hw though.

-- 
Regards,
Artyom Tarasenko

solaris/sparc under qemu blog: http://tyom.blogspot.com/

  parent reply	other threads:[~2010-02-20 22:00 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11 11:20 [Qemu-devel] qemu-ppc can't run static uClibc binaries Rob Landley
2010-02-11 12:32 ` Alexander Graf
2010-02-14  8:36   ` Rob Landley
2010-02-14 14:41     ` Alexander Graf
2010-02-15 11:10       ` Rob Landley
2010-02-15 11:19         ` Alexander Graf
2010-02-15 12:58           ` Rob Landley
2010-02-15 13:01             ` Alexander Graf
2010-02-16 18:31               ` Rob Landley
2010-02-16 18:36                 ` Alexander Graf
2010-02-16 19:14                   ` Rob Landley
2010-02-15 13:08             ` [Qemu-devel] " Michael S. Tsirkin
2010-02-16  0:52               ` Rob Landley
2010-02-16  9:31                 ` Alexander Graf
2010-02-16 18:14                   ` Rob Landley
2010-02-17  9:24                     ` Artyom Tarasenko
2010-02-17 15:45                       ` Paolo Bonzini
2010-02-17 18:55                         ` Rob Landley
2010-02-17 20:46                           ` Blue Swirl
2010-02-18 11:38                             ` Artyom Tarasenko
2010-02-18 13:17                               ` Rob Landley
2010-02-18 14:10                                 ` Artyom Tarasenko
2010-02-18 13:05                             ` Rob Landley
2010-02-18 11:21                           ` Artyom Tarasenko
2010-02-18 13:14                             ` Rob Landley
2010-02-18 14:19                               ` Artyom Tarasenko
2010-02-20 17:17                             ` [Qemu-devel] Fun with sparc (was Re: qemu-ppc can't run static uClibc binaries.) Rob Landley
2010-02-20 17:34                               ` [Qemu-devel] " Blue Swirl
2010-02-20 18:38                                 ` Rob Landley
2010-02-20 21:59                                   ` Blue Swirl
2010-02-20 23:12                                     ` Rob Landley
2010-02-21 16:25                                       ` [Qemu-devel] Commit 085219f79cad broke Sparc-32 back in 2.6.28 Rob Landley
2010-02-21 23:57                                         ` [Qemu-devel] " David Miller
2010-02-22  0:28                                           ` Bartlomiej Zolnierkiewicz
2010-02-22  2:03                                             ` Rob Landley
2010-02-22  2:06                                         ` David Miller
2010-02-20 21:59                                   ` Artyom Tarasenko [this message]
2010-02-20 21:39                                 ` [Qemu-devel] Re: Fun with sparc (was Re: qemu-ppc can't run static uClibc binaries.) Artyom Tarasenko
2010-02-20 22:03                                   ` Blue Swirl
2010-02-17 16:36                       ` [Qemu-devel] Re: qemu-ppc can't run static uClibc binaries Rob Landley
2010-02-16  8:21           ` [Qemu-devel] " Stuart Brady
2010-02-28 21:05             ` Aurelien Jarno

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=fb8d4f71002201359s51286e07x773cd2abcfad4ec2@mail.gmail.com \
    --to=atar4qemu@googlemail.com \
    --cc=blauwirbel@gmail.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rob@landley.net \
    /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).