From mboxrd@z Thu Jan  1 00:00:00 1970
From: Marek Vasut <marex@denx.de>
Date: Fri, 27 Jul 2012 03:26:35 +0200
Subject: [U-Boot] [U-Boot-DM] List of offending drivers
In-Reply-To: <CALButC+yh1YvPn-G=LdqOx_9BQDUWurKwD-MuhB4u28J8-pUhg@mail.gmail.com>
References: <201207270118.19524.marex@denx.de>
	<201207270311.04978.marex@denx.de>
	<CALButC+yh1YvPn-G=LdqOx_9BQDUWurKwD-MuhB4u28J8-pUhg@mail.gmail.com>
Message-ID: <201207270326.35234.marex@denx.de>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Dear Graeme Russ,

> Hi Marek,
> 
> On Fri, Jul 27, 2012 at 11:11 AM, Marek Vasut <marex@denx.de> wrote:
> > Dear Graeme Russ,
> > 
> >> So neither of these files are 'drivers' per-se. They are really just
> >> initialisation and platform specific support functions. How do these fit
> >> into the new driver model?
> > 
> > You can supply a pointer to that function to some "pci" driver I guess
> > ... Pavel?
> 
> In which case you have a board/arch specific function to intialise the
> pointer :)

No, you have static platform data which contain the pointer.

> Hmm, or are we now looking at a variation of my INIT_FUNC
> architecture where this gets done at compile time?

I think you missed the point here

> Regards,
> 
> Graeme

Best regards,
Marek Vasut