From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michal Simek Date: Tue, 10 Jul 2012 15:47:50 +0200 Subject: [U-Boot] FDT driver initialization function declaration In-Reply-To: <20120710130331.854362026C4@gemini.denx.de> References: <4FFC02BD.7060106@monstr.eu> <20120710115413.9CFB22026C4@gemini.denx.de> <4FFC1EF8.9060705@monstr.eu> <20120710130331.854362026C4@gemini.denx.de> Message-ID: <4FFC3286.2020407@monstr.eu> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear Wolfgang, On 07/10/2012 03:03 PM, Wolfgang Denk wrote: > Dear Michal Simek, > > In message<4FFC1EF8.9060705@monstr.eu> you wrote: >> >> The hardest part I have identify on microblaze was about u-boot variables. >> Because based on information from device-tree you can choose where variables >> should be stored and also this memory should be accessible before u-boot >> try to read variables. It mean in very early state. > > Device initialization before relocation is already hard enough; > resources are very limited then. You will add the additional need to > have the FDT library available then, too. Not to mention that you > need to load the DT blob, too. > > This will be a lot of added complexity. Do you have any timeframe for this work? Or any expectation when this work should be merged to mainline? Thanks, Michal -- Michal Simek, Ing. (M.Eng) w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel 2.6 Microblaze Linux - http://www.monstr.eu/fdt/ Microblaze U-BOOT custodian