From: Mike Frysinger Date: Wed, 27 May 2009 14:48:41 -0400 Subject: [U-Boot] [RFC] initcall mechanism introduction In-Reply-To: <200905271012.21971.sr@denx.de> References: <20090523150558.GB26561@game.jcrosoft.org> <20090527095235.78e24b0d@hskinnemoen-d830> <200905271012.21971.sr@denx.de> Message-ID: <200905271448.43059.vapier@gentoo.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On Wednesday 27 May 2009 04:12:21 Stefan Roese wrote: > ACK. Even though I don't have a clue right now how this could be > accomplished in practise without breaking some of the (old) board ports. i thought current practice was that if no one cared to update board ports and verify they still worked, then they were in effect dead and should be dropped. i'd also support initcall integration, but in order to have correct initialization order for core aspects, we're still going to need a hardcoded list somewhere -- this is how the kernel works too after all. hopefully this would allow us to unify the board init process into common code though. -mike -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 836 bytes Desc: This is a digitally signed message part. Url : http://lists.denx.de/pipermail/u-boot/attachments/20090527/fff37cf3/attachment.pgp