LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Mark A. Greer" <mgreer@mvista.com>
To: Paul Mackerras <paulus@samba.org>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 02/19] bootwrapper: Set -msoft-float and assembler target options.
Date: Mon, 12 Mar 2007 22:32:59 -0700	[thread overview]
Message-ID: <20070313053258.GB27618@mag.az.mvista.com> (raw)
In-Reply-To: <17910.4629.587851.80369@cargo.ozlabs.ibm.com>

On Tue, Mar 13, 2007 at 01:53:09PM +1100, Paul Mackerras wrote:

Many of these are really mine to answer...

> Scott Wood writes:
> > Without the assembler target option, the assembler will use the old
> > dedicated mftb/mftbu instructions, rather than mfspr.  This causes the
> > boot to hang on e500, which doesn't have the dedicated instructions.
> 
> I see mftb being used for udelay in util.S, and udelay being used in
> serial_edit_cmdline in serial.c.  It's somewhat bogus that we just
> hard-code an assumed timebase frequency in util.S, and also bogus that

The timebase stuff was a straight copy from arch/ppc/boot/common/util.S.
I agree that its a bogus and should be fixed.

> we get command line editing for serial consoles but not for OF
> consoles (why should they be different?).

IIRC, a few of us talked about that on IRC way back.  The consensus
was that you would just change it with OF.  I added editing for non-OF
(should really be any fw that doesn't pass in an updated dtb (i.e.,
anything but OF and the new u-boot)) because, the cmdline would be
coming from the dtb embedded in the zImage (or from builtin_cmdline).
To change it, you have to find the dts, change it, and run 'wrapper'
(or run a pgm to set builtin_cmdline).  Seems like a lot to do for
a quick, temporary cmdline edit.

Its easy enough to add for OF, if you think its worth it.  I lack the OF
knowledge to do so though.

> It looks to me like we should at least make the platform code provide
> udelay (or mdelay), possibly with the aid of a helper function.

Agreed.

> We
> should also consider whether the command-line editing is generally
> useful, or not, and whether the function to do it should be made more
> generic.

IMHO, it is very useful if you have fw that doesn't update the dtb for
you (i.e., OF and u-boot).  Don't know if it makes sense for OF and/or
u-boot.

Mark

  reply	other threads:[~2007-03-13  5:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-12 20:41 [PATCH 02/19] bootwrapper: Set -msoft-float and assembler target options Scott Wood
2007-03-13  2:53 ` Paul Mackerras
2007-03-13  5:32   ` Mark A. Greer [this message]
2007-03-13  5:38     ` Mark A. Greer
2007-03-13 12:14     ` Josh Boyer
2007-03-13 15:43   ` Scott Wood
  -- strict thread matches above, loose matches on Subject: below --
2007-02-07 23:00 [PATCH 00/19] cuboot bootwrapper patchset Scott Wood
2007-02-07 23:01 ` [PATCH 02/19] bootwrapper: Set -msoft-float and assembler target options Scott Wood

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=20070313053258.GB27618@mag.az.mvista.com \
    --to=mgreer@mvista.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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