From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: "Rogério Brito" <rbrito@ime.usp.br>,
"Scott Wood" <scottwood@freescale.com>,
linuxppc-dev@ozlabs.org
Subject: [REGRESSION 2.6.27] i2c-mpc not probing on linkstation (was Re: [PATCH] powerpc: enable heap randomization for linkstations)
Date: Tue, 21 Oct 2008 08:42:36 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0810210832260.4941@axis700.grange> (raw)
In-Reply-To: <9e4733910810200519w4689131dv73bf3539c53d2bea@mail.gmail.com>
On Mon, 20 Oct 2008, Jon Smirl wrote:
> On Mon, Oct 20, 2008 at 1:55 AM, Guennadi Liakhovetski
> <g.liakhovetski@gmx.de> wrote:
> > On Sun, 19 Oct 2008, Jon Smirl wrote:
> >
> >> Is i2c-mpc built into your kernel? It's not going to module auto-load
> >> because the names don't match - fsl-i2c and i2c-mpc.
> >
> > It is built into the kernel.
>
> Put a printk in it's init function to make sure it is initializing.
I don't need that, I see it here:
/sys/bus/of_platform/drivers/mpc-i2c
> Next thing I do is put printks over in arch/powerpc/.. to tell me
> which strings from the device tree are being looked for.
>
> You can also look in /proc/device_tree and make sure fsl-i2c is in there.
>
> When you find the problem is will probably be something simple like a
> mismatch between _ and -. I have been down this path before and spent
> a day figuring out why a module wouldn't load and it was a simple
> typo.
Thanks, I know, that I can find the reason and, probably, a fix after a
day of printk debugging. The thing is - I don't have this day, and I am
sure there are people on this list, who can spot and fix the problem
within minutes, that's why I posted it here after I realised, that 2 hours
of me searching for the problem didn't bring any result.
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
next prev parent reply other threads:[~2008-10-21 6:42 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 4:07 [PATCH] powerpc: compile kernel for linkstations optimized for size Rogério Brito
2008-10-13 4:51 ` [PATCH] powerpc: enable heap randomization for linkstations Rogério Brito
2008-10-13 18:05 ` Guennadi Liakhovetski
2008-10-13 18:44 ` Scott Wood
2008-10-13 19:27 ` Guennadi Liakhovetski
2008-10-13 20:56 ` Rogério Brito
2008-10-19 2:53 ` Rogério Brito
2008-10-19 3:16 ` Rogério Brito
2008-10-19 20:59 ` Guennadi Liakhovetski
2008-10-19 21:32 ` Jon Smirl
2008-10-19 21:49 ` Guennadi Liakhovetski
2008-10-19 22:05 ` Jon Smirl
2008-10-19 22:28 ` Guennadi Liakhovetski
2008-10-19 22:40 ` Jon Smirl
2008-10-20 5:55 ` Guennadi Liakhovetski
2008-10-20 12:19 ` Jon Smirl
2008-10-21 6:42 ` Guennadi Liakhovetski [this message]
2008-10-21 7:19 ` [REGRESSION 2.6.27] i2c-mpc not probing on linkstation Rogério Brito
2008-10-21 15:16 ` [PATCH] powerpc: enable heap randomization for linkstations Scott Wood
2008-10-21 15:26 ` Guennadi Liakhovetski
2008-10-21 15:32 ` Scott Wood
2008-10-17 9:38 ` Rogério Brito
2008-10-28 13:58 ` Kumar Gala
2008-10-13 18:03 ` [PATCH] powerpc: compile kernel for linkstations optimized for size Guennadi Liakhovetski
2008-10-13 21:28 ` Rogério Brito
2008-10-17 9:37 ` Rogério Brito
2008-10-28 13:58 ` Kumar Gala
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=Pine.LNX.4.64.0810210832260.4941@axis700.grange \
--to=g.liakhovetski@gmx.de \
--cc=jonsmirl@gmail.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=rbrito@ime.usp.br \
--cc=scottwood@freescale.com \
/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