From: Marco Stornelli <marco.stornelli@coritel.it>
To: skepper@ukf.net
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Not probing devices on PowerPC MPC8247 and kernel 2.6.26
Date: Wed, 10 Sep 2008 12:18:58 +0200 [thread overview]
Message-ID: <48C79F12.5040503@coritel.it> (raw)
In-Reply-To: <Pine.LNX.4.62.0809101058580.24139@chara.vm.bytemark.co.uk>
Hi Chris,
probably there's some mismatch between the device (for example some
information in dts) and the driver. The match function scan for a driver
for those devices but the values compared don't match the values of the
drivers.
Regards.
Chris Skepper ha scritto:
> Hi All,
>
> I have an MPC8247 based board. I can get the SMC1 console working, but
> the other SCCx serial ports and the FCC1 ethernet doesn't work.
>
> It appears that a part of the problem is that the probe methods are
> not called. The "match" table stuff all looks fine and the serial
> ports and ethernet are defined in the .dts file. The module init
> function is called, but the probe methods are not reached. It seems
> driver_register gets called, so why doesn't something call probe?
>
> Is there likely to be some problem with the bus setup?
>
> Cheers,
>
> Chris.
>
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
--
Marco Stornelli
Embedded Software Engineer
CoRiTeL - Consorzio di Ricerca sulle Telecomunicazioni
http://www.coritel.it
marco.stornelli@coritel.it
+39 06 72582838
next prev parent reply other threads:[~2008-09-10 10:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 10:07 Not probing devices on PowerPC MPC8247 and kernel 2.6.26 Chris Skepper
2008-09-10 10:18 ` Marco Stornelli [this message]
2008-09-10 10:32 ` Chris Skepper
2008-09-10 15:56 ` Scott Wood
2008-09-12 14:46 ` Chris Skepper
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=48C79F12.5040503@coritel.it \
--to=marco.stornelli@coritel.it \
--cc=linuxppc-embedded@ozlabs.org \
--cc=skepper@ukf.net \
/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.