From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH] Move init_sequence table into code.
Date: Fri, 18 Apr 2008 06:14:13 +0200 [thread overview]
Message-ID: <20080418041413.02A8F248A0@gemini.denx.de> (raw)
In-Reply-To: Your message of "Tue, 15 Apr 2008 08:40:21 +0200." <1208241621.5911.32.camel@gentoo-jocke.transmode.se>
In message <1208241621.5911.32.camel@gentoo-jocke.transmode.se> you wrote:
>
> It is not going to be a walk in the park :) The big remaining part
> is string literals while still in flash, not sure how to solve these
> yet.
>
> >
> > > > The original idea of having such a list of funtion pointers which
> > > > just get executed one after another was to be able to wrap this into
> > > > some "#ifndef CONFIG_INIT_SEQUENCE" and use this to allow for board-
> > > > specific init sequences by just adding a #define with the needed list
> > > > of functions to the board config files.
> > >
> > > You can do that with weak functions too. Just make all the functions
> > > weak, then a board can overide with its own function.
> >
> > That would not, for example, to allow to change the sequence - say
> > one board needs to initialize PCI very early, but another one very
> > late.
>
> True, but as no one even uses this code ATM, it can't be a big deal.
OK. Well, this is not a bug fix, but a (more or less invasive) change
to basic infrastructure. I will not add this so shortly before a
release. Please rebase and resubmit when the next merge window is
open.
Thanks.
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
"You ain't experienced..." "Well, nor are you." "That's true. But the
point is ... the point is ... the point is we've been not experienced
for a lot longer than you. We've got a lot of experience of not
having any experience." - Terry Pratchett, _Witches Abroad_
prev parent reply other threads:[~2008-04-18 4:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-28 15:45 [U-Boot-Users] [PATCH] Move init_sequence table into code Joakim Tjernlund
2008-03-28 15:45 ` [U-Boot-Users] [PATCH] Change env_get_char from a global function ptr to a function Joakim Tjernlund
2008-03-30 18:08 ` Jean-Christophe PLAGNIOL-VILLARD
2008-03-30 20:59 ` Wolfgang Denk
2008-03-30 21:05 ` Joakim Tjernlund
2008-03-30 22:33 ` Wolfgang Denk
2008-03-31 7:15 ` Joakim Tjernlund
2008-04-05 17:31 ` Joakim Tjernlund
2008-04-14 1:09 ` Wolfgang Denk
2008-04-14 21:01 ` Joakim Tjernlund
2008-04-18 4:14 ` Wolfgang Denk
2008-04-14 1:09 ` [U-Boot-Users] [PATCH] Move init_sequence table into code Wolfgang Denk
2008-04-14 21:06 ` Joakim Tjernlund
2008-04-15 4:35 ` Wolfgang Denk
2008-04-15 6:40 ` Joakim Tjernlund
2008-04-18 4:14 ` Wolfgang Denk [this message]
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=20080418041413.02A8F248A0@gemini.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