From: Scott Wood <scottwood@freescale.com>
To: Benjamin Zores <benjamin.zores@alcatel-lucent.fr>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: FSL Driver load issues with OF
Date: Thu, 30 Apr 2009 11:20:19 -0500 [thread overview]
Message-ID: <20090430162019.GA3655@ld0162-tx32.am.freescale.net> (raw)
In-Reply-To: <49F821B0.6030706@alcatel-lucent.fr>
On Wed, Apr 29, 2009 at 11:45:20AM +0200, Benjamin Zores wrote:
> Since the progressive migration of some PPC drivers to use of_platform bus
> (typically migrating OF parsing from fsl_soc.c to the device probe/init
> functions),
> I'm experiencing driver load issues.
>
> Actually, I'm not longer able to load of these drivers as the probe()
> function is never called.
Make sure your board is calling of_platform_bus_probe(), and that the
devices you're trying to probe are under buses described by the id list.
-Scott
next prev parent reply other threads:[~2009-04-30 16:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-29 9:45 FSL Driver load issues with OF Benjamin Zores
2009-04-30 16:20 ` Scott Wood [this message]
2009-05-04 14:27 ` Benjamin Zores
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=20090430162019.GA3655@ld0162-tx32.am.freescale.net \
--to=scottwood@freescale.com \
--cc=benjamin.zores@alcatel-lucent.fr \
--cc=linuxppc-dev@ozlabs.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox