public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Re: PATCH: bi_iic_fast[] initialization
Date: Wed, 07 Apr 2004 17:13:41 +0200	[thread overview]
Message-ID: <20040407151346.519B1C133F@atlas.denx.de> (raw)
In-Reply-To: Your message of "Wed, 07 Apr 2004 09:58:48 CDT." <30399.216.110.51.8.1081349928.squirrel@www.orkun.us>

In message <30399.216.110.51.8.1081349928.squirrel@www.orkun.us> you wrote:
> 
> > I think you should  rework  this  patch.  At  the  moment,  you  call
> > getenv() in board_init_f() - but board_init_f() is still running from
> > flash,  which  means  that we don't have a full C runtime environment
> > (uninitialized BSS, no writable data, limited stack space) so the use
> > of getenv() is not allowd in that function. You  may  use  getenv_r()
> > instead.
> 
> I can convert it to use getenv_r() or I think it would be better to move
> that section dealing with initialization of bi_iic_fast[] flags to
> board_init_r(). bi_iic_fast[] is not used by u-boot itself. It is passed
> to Linux.

Then move it to board_init_r(), please.

> Personally, the most appropriate place to initialize such things would be
> right before u-boot boots the OS. The immediate changes to the environment
> would also be captured without forcing an environment save and reset as
> well.

Be careful, though. Not everybody uses the same path to boot a kernel.

> 1) Fix in board_init_f() using getenv_r()
> 2) Fix by moving to board_init_r()

Go for 2.

> 3) Create a new function (say board_init_preboot) and move that section
> into it. Hook board_init_preboot() to the existing boot functions (boot,
> bootm etc. somehow)

No, please not yet another xxx_init_pre_before_early_reallybefore_preinit
function.


Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
He had quite a powerful intellect, but it  was  as  powerful  like  a
locomotive,  and  ran on rails and was therefore almost impossible to
steer.                          - Terry Pratchett, _Lords and Ladies_

  reply	other threads:[~2004-04-07 15:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <14824.216.110.51.8.1079378410.squirrel@www.orkun.us>
2004-04-07  9:54 ` [U-Boot-Users] Re: PATCH: bi_iic_fast[] initialization Wolfgang Denk
2004-04-07 14:58   ` Tolunay Orkun
2004-04-07 15:13     ` Wolfgang Denk [this message]
2004-04-07 16:46       ` [U-Boot-Users] PATCH: bi_iic_fast[] initialization relocated to board_init_r() Tolunay Orkun
2004-04-18 21:29         ` 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=20040407151346.519B1C133F@atlas.denx.de \
    --to=wd@denx.de \
    --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