Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Tom Talpey <tmtalpey@rcn.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: arm kernel configurations
Date: Thu, 30 Oct 2008 14:09:12 -0400	[thread overview]
Message-ID: <MADEUP.15FE1A15F97DC729.13558@groups.io> (raw)
In-Reply-To: <1225386831.17961.15.camel@mill.internal.reciva.com>

At 01:13 PM 10/30/2008, Phil Blundell wrote:
>On Thu, 2008-10-30 at 12:45 -0400, Tom Talpey wrote:
>> As above - the specs do include "--with-float=soft". I guess I'll have to
>> dig some more. Do I also need -mfloat-abi=softfp in the machine.conf like
>> some of the other arm's?
>
>I don't think so.  If I remember right, -mfloat-abi=softfp is for the
>case where you want to use hard floating point instructions (for speed)
>but still want to retain compatibility with a soft-float ABI.
>
>I wonder if something has gone wrong with your glibc configuration.  Try
>disassembling one of your binaries and see if you can find any reference
>to "wfs" or "rfs" instructions.  Also have a look in libc.so.6 itself to
>see what the syscall instructions look like: for OABI you will see
>something like "swi 0x900004", whereas for EABI it will look more like
>"mov ip, r7; mov r7, #4; swi 0; mov r7, ip".

Looks like EABI to me then, objdump -d libc.so.6 sample syscall:

0002a0c0 <kill>:
   2a0c0:       e1a0c007        mov     ip, r7
   2a0c4:       e3a07025        mov     r7, #37 ; 0x25
   2a0c8:       ef000000        svc     0x00000000
   2a0cc:       e1a0700c        mov     r7, ip
   2a0d0:       e3700a01        cmn     r0, #4096       ; 0x1000
   2a0d4:       312fff1e        bxcc    lr
   2a0d8:       eaffaa98        b       14b40 <__libc_start_main+0x248>
   2a0dc:       e1a00000        nop                     (mov r0,r0)

And no wfs/rfs at all in any binaries. Hmm, let me try the no-OABI
kernel again. Maybe I can get more status from it. Basically it would
say "Freeing init memory" then nothing more, while with-OABI it would
cruise.

Tom.




  reply	other threads:[~2008-10-30 18:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-29 15:26 arm kernel configurations Phil Blundell
2008-10-30 14:40 ` Tom Talpey
     [not found] ` <E1KvYmj-0007s2-Og@linuxtogo.org>
2008-10-30 15:08   ` Phil Blundell
2008-10-30 16:45     ` Tom Talpey
     [not found]     ` <E1Kvahy-0001AR-Sj@linuxtogo.org>
2008-10-30 17:13       ` Phil Blundell
2008-10-30 18:09         ` Tom Talpey [this message]
     [not found]         ` <E1Kvc17-0001Gl-VY@linuxtogo.org>
2008-10-30 18:37           ` Tom Talpey
2008-10-30 18:42           ` Phil Blundell
     [not found]           ` <E1KvcSD-0007H7-V3@linuxtogo.org>
2008-10-30 19:01             ` Phil Blundell
2008-10-30 20:10               ` Tom Talpey

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=MADEUP.15FE1A15F97DC729.13558@groups.io \
    --to=tmtalpey@rcn.com \
    --cc=openembedded-devel@lists.openembedded.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