From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [U-Boot-DM] List of offending drivers
Date: Fri, 27 Jul 2012 03:26:35 +0200 [thread overview]
Message-ID: <201207270326.35234.marex@denx.de> (raw)
In-Reply-To: <CALButC+yh1YvPn-G=LdqOx_9BQDUWurKwD-MuhB4u28J8-pUhg@mail.gmail.com>
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
next prev parent reply other threads:[~2012-07-27 1:26 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-26 23:18 [U-Boot] List of offending drivers Marek Vasut
2012-07-27 1:08 ` [U-Boot] [U-Boot-DM] " Graeme Russ
2012-07-27 1:11 ` Marek Vasut
2012-07-27 1:20 ` Graeme Russ
2012-07-27 1:26 ` Marek Vasut [this message]
2012-07-27 1:29 ` Graeme Russ
2012-07-27 1:37 ` Marek Vasut
2012-07-27 4:41 ` Wolfgang Denk
2012-07-27 8:42 ` Marek Vasut
2012-07-27 9:33 ` Wolfgang Denk
2012-07-31 7:50 ` Mike Frysinger
2012-07-27 6:28 ` [U-Boot] " Lukasz Majewski
2012-07-27 8:43 ` Marek Vasut
2012-07-27 14:11 ` Igor Grinberg
2012-07-27 14:30 ` Marek Vasut
2012-07-27 14:45 ` Igor Grinberg
2012-07-27 14:49 ` Marek Vasut
2012-08-01 10:11 ` [U-Boot] [U-Boot-DM] " Andreas Bießmann
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=201207270326.35234.marex@denx.de \
--to=marex@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.