U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Fredrik <fcn-sub@noon.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] error: invalid option `cpu=4kc
Date: Mon, 13 Dec 2004 12:00:47 -0800	[thread overview]
Message-ID: <uis76aryo.fsf@noon.org> (raw)
In-Reply-To: <CFA9FA7615FFD04DB8FD8E34A3FF7F468DF5E3@sjcxch02.tbu.com> (Jattin Dudakia's message of "Mon, 13 Dec 2004 10:20:44 -0800")

Jattin,

The "cpu" option is outdated in favor of the "-march" option.  The tip
sources have changed cpu/mips/config.mk to reflect that:

  -march=4kc -mtune=4kc -Wa,-mips_allow_branch_to_undefined \
  -EB -mabicalls

(The "-mtune" option seems redundant, but shouldn't hurt anything.)

/Fredrik

  reply	other threads:[~2004-12-13 20:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-13 18:20 [U-Boot-Users] error: invalid option `cpu=4kc Jattin Dudakia
2004-12-13 20:00 ` Fredrik [this message]
2004-12-13 21:24 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2004-12-14  7:32 Jattin Dudakia
2004-12-14 13:14 ` Wolfgang Denk
2004-12-11  1:05 Jattin Dudakia
2004-12-12 17:49 ` Wolfgang Denk

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=uis76aryo.fsf@noon.org \
    --to=fcn-sub@noon.org \
    --cc=u-boot@lists.denx.de \
    /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