All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] New init sequence processing without init_sequence array
Date: Wed, 24 Aug 2011 15:24:50 +0200	[thread overview]
Message-ID: <20110824132450.D253311F9E76@gemini.denx.de> (raw)
In-Reply-To: <4E54F501.6050706@gmail.com>

Dear Graeme Russ,

In message <4E54F501.6050706@gmail.com> you wrote:
> 
> > Sorry, but when reading the source code or when revioewing patches I
> > cannot paick up any next funtion pointers, I'm stuck with reading the
> > source code only.
> 
> Well, I guess I had a good shot at creating a 'better' init sequence - one
> where any board, SoC, or arch can seamlessly inject a custom init step
> without treading on any toes.
> 
> I must say, it was rather fun learning how to build the macros and get the
> linker to do the right thing and have it all work so quickly. I'll stick it
> in my bag of tricks for another day :)

Hey, you give up early.  Are you suffering from hot weather, too?  :-)

Seriously,  I do not think we should stop this discussion yet. I agree
that a better approach to the init code would be a good thing, but at
the same time I want to make sure the result will be really better,
and we not by means of Beelzebub expel the demons...


I already tried to lend a helping hand by suggesting to create a list
of init functions as part of the build process - OK, we still have to
build the code to get this, but at last we can then see the complete
and precise order for this specific configuration.


Also, Detlev made some interesting remarks - he noted that basicly
what we are trying to solve is a dependency issue: each init function
has a list of dependencies (other init steps) that need to be run
before.  Instead of manually assigning initcall numbers, we could try
and write down these dependencies, for example in a format that can
be digested by a tool like tsort.  We could then use this to
auto-generate the list of init calls.  This is a completely new
approach, but it has the charme of making the dependencies clear.


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
Einstein argued that there must be simplified explanations of nature,
because God is not capricious or arbitrary. No  such  faith  comforts
the software engineer.                             - Fred Brooks, Jr.

  reply	other threads:[~2011-08-24 13:24 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-17 13:22 [U-Boot] [RFC] New init sequence processing without init_sequence array Graeme Russ
2011-08-22 20:10 ` Wolfgang Denk
2011-08-22 23:20   ` Graeme Russ
2011-08-23 11:49     ` Wolfgang Denk
2011-08-23 23:20       ` Graeme Russ
2011-08-24  5:38         ` Wolfgang Denk
2011-08-24  5:57           ` Graeme Russ
2011-08-24  6:48             ` Wolfgang Denk
2011-08-24  7:06               ` Graeme Russ
2011-08-24 12:49                 ` Wolfgang Denk
2011-08-24 12:56                   ` Graeme Russ
2011-08-24 13:24                     ` Wolfgang Denk [this message]
2011-08-24 13:58                       ` Graeme Russ
2011-08-24 23:00                         ` Graeme Russ
2011-08-24 23:41                           ` Simon Glass
2011-08-25  2:45                             ` Graeme Russ
2011-08-24 13:46               ` Detlev Zundel
2011-08-23  0:17   ` Graeme Russ
2011-08-23  1:00   ` Mike Frysinger
2011-08-23  1:10     ` Graeme Russ
2011-08-23 11:52     ` 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=20110824132450.D253311F9E76@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.