Re: [U-Boot] FDT driver initialization function declaration

2012-07-13 Thread Simon Glass
Hi Michal, On Tue, Jul 10, 2012 at 3:49 PM, Michal Simek wrote: > On 07/10/2012 03:18 PM, Simon Glass wrote: >> >> Hi Michal, >> >> >> On Tue, Jul 10, 2012 at 12:23 PM, Michal Simek > > wrote: >> >> Hi Simon, Wolfgang and others, >> >> just want to open new topic

Re: [U-Boot] FDT driver initialization function declaration

2012-07-13 Thread Marek Vasut
Dear Michal Simek, > On 07/10/2012 05:11 PM, Marek Vasut wrote: > > Dear Michal Simek, > > > >> Dear Wolfgang, > >> > >> On 07/10/2012 03:03 PM, Wolfgang Denk wrote: > >>> Dear Michal Simek, > >>> > >>> In message<4ffc1ef8.9060...@monstr.eu> you wrote: > The hardest part I have identify

Re: [U-Boot] FDT driver initialization function declaration

2012-07-11 Thread Michal Simek
On 07/10/2012 03:12 PM, Marek Vasut wrote: Dear Wolfgang Denk, Dear Michal Simek, In message<4ffc1ef8.9060...@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 b

Re: [U-Boot] FDT driver initialization function declaration

2012-07-10 Thread Michal Simek
On 07/10/2012 05:08 PM, Marek Vasut wrote: Dear Michal Simek, [...] Michal, can you try investigating how will the DT probing intertwine with the DM? Firstly I need to understand what you are trying to achieve and how. Then if I have time I can look at how DT probing can be added to it. But

Re: [U-Boot] FDT driver initialization function declaration

2012-07-10 Thread Michal Simek
On 07/10/2012 05:11 PM, Marek Vasut wrote: Dear Michal Simek, Dear Wolfgang, On 07/10/2012 03:03 PM, Wolfgang Denk wrote: Dear Michal Simek, In message<4ffc1ef8.9060...@monstr.eu> you wrote: The hardest part I have identify on microblaze was about u-boot variables. Because based on inform

Re: [U-Boot] FDT driver initialization function declaration

2012-07-10 Thread Marek Vasut
Dear Michal Simek, > Dear Wolfgang, > > On 07/10/2012 03:03 PM, Wolfgang Denk wrote: > > Dear Michal Simek, > > > > In message<4ffc1ef8.9060...@monstr.eu> you wrote: > >> The hardest part I have identify on microblaze was about u-boot > >> variables. Because based on information from device-tre

Re: [U-Boot] FDT driver initialization function declaration

2012-07-10 Thread Marek Vasut
Dear Michal Simek, [...] > > Michal, can you try investigating how will the DT probing intertwine with > > the DM? > > Firstly I need to understand what you are trying to achieve and how. > Then if I have time I can look at how DT probing can be added to it. > > But I think that there is good e

Re: [U-Boot] FDT driver initialization function declaration

2012-07-10 Thread Michal Simek
On 07/10/2012 03:18 PM, Simon Glass wrote: Hi Michal, On Tue, Jul 10, 2012 at 12:23 PM, Michal Simek mailto:mon...@monstr.eu>> wrote: Hi Simon, Wolfgang and others, just want to open new topic about FDT driver initialization function declaration. There are some drivers which c

Re: [U-Boot] FDT driver initialization function declaration

2012-07-10 Thread Michal Simek
Dear Wolfgang, On 07/10/2012 03:03 PM, Wolfgang Denk wrote: Dear Michal Simek, In message<4ffc1ef8.9060...@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 s

Re: [U-Boot] FDT driver initialization function declaration

2012-07-10 Thread Wolfgang Denk
Dear Marek, In message <201207101505.26919.marek.va...@gmail.com> you wrote: > > Wolfgang, is it possible to somehow tag the DM patches so we can later > collect > these tagged patches to prove we did the amount of work to the university > committee? Or maybe simple "dm:" in the subject will s

Re: [U-Boot] FDT driver initialization function declaration

2012-07-10 Thread Michal Simek
On 07/10/2012 03:12 PM, Marek Vasut wrote: Dear Wolfgang Denk, Dear Michal Simek, In message<4ffc1ef8.9060...@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 b

Re: [U-Boot] FDT driver initialization function declaration

2012-07-10 Thread Michal Simek
On 07/10/2012 03:00 PM, Marek Vasut wrote: Dear Michal Simek, Dear Wolfgang, On 07/10/2012 01:54 PM, Wolfgang Denk wrote: Dear Michal, In message<4ffc02bd.7060...@monstr.eu> you wrote: just want to open new topic about FDT driver initialization function declaration. There are some driver

Re: [U-Boot] FDT driver initialization function declaration

2012-07-10 Thread Simon Glass
Hi Michal, On Tue, Jul 10, 2012 at 12:23 PM, Michal Simek wrote: > Hi Simon, Wolfgang and others, > > just want to open new topic about FDT driver initialization function > declaration. > > There are some drivers which can be simple move to fdt initialization. > I have in my mind ethernet driver

Re: [U-Boot] FDT driver initialization function declaration

2012-07-10 Thread Simon Glass
Hi, On Tue, Jul 10, 2012 at 3:05 PM, Marek Vasut wrote: > Dear Michal Simek, > > > Hi Simon, Wolfgang and others, > > > > just want to open new topic about FDT driver initialization function > > declaration. > > Ok, my few nits (with consideration of the DM stuff) ... > 1) Parsing the DTB is slo

Re: [U-Boot] FDT driver initialization function declaration

2012-07-10 Thread Marek Vasut
Dear Wolfgang Denk, > Dear Michal Simek, > > In message <4ffc1ef8.9060...@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

Re: [U-Boot] FDT driver initialization function declaration

2012-07-10 Thread Marek Vasut
Dear Michal Simek, > Hi Simon, Wolfgang and others, > > just want to open new topic about FDT driver initialization function > declaration. Ok, my few nits (with consideration of the DM stuff) ... 1) Parsing the DTB is slowish 2) The DT can bind nicely with the DM, but if you could investigate f

Re: [U-Boot] FDT driver initialization function declaration

2012-07-10 Thread Wolfgang Denk
Dear Michal Simek, In message <4ffc1ef8.9060...@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

Re: [U-Boot] FDT driver initialization function declaration

2012-07-10 Thread Marek Vasut
Dear Michal Simek, > Dear Wolfgang, > > On 07/10/2012 01:54 PM, Wolfgang Denk wrote: > > Dear Michal, > > > > In message<4ffc02bd.7060...@monstr.eu> you wrote: > >> just want to open new topic about FDT driver initialization function > >> declaration. > >> > >> There are some drivers which can

Re: [U-Boot] FDT driver initialization function declaration

2012-07-10 Thread Michal Simek
Dear Wolfgang, On 07/10/2012 01:54 PM, Wolfgang Denk wrote: Dear Michal, In message<4ffc02bd.7060...@monstr.eu> you wrote: just want to open new topic about FDT driver initialization function declaration. There are some drivers which can be simple move to fdt initialization. I have in my mi

Re: [U-Boot] FDT driver initialization function declaration

2012-07-10 Thread Wolfgang Denk
Dear Michal, In message <4ffc02bd.7060...@monstr.eu> you wrote: > > just want to open new topic about FDT driver initialization function > declaration. > > There are some drivers which can be simple move to fdt initialization. > I have in my mind ethernet drivers and then systemace (I have porte

[U-Boot] FDT driver initialization function declaration

2012-07-10 Thread Michal Simek
Hi Simon, Wolfgang and others, just want to open new topic about FDT driver initialization function declaration. There are some drivers which can be simple move to fdt initialization. I have in my mind ethernet drivers and then systemace (I have ported it). Ethernet drivers use include/netdev.h