From: "Matvejchikov Ilya" <matvejchikov@gmail.com>
To: "Scott Wood" <scottwood@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: No output from SMC1 console with the 2.6.26 kernel (PQ2FADS based board)
Date: Tue, 29 Jul 2008 10:10:27 +0400 [thread overview]
Message-ID: <8496f91a0807282310r5e70fe01v85b2ff2da7a80416@mail.gmail.com> (raw)
In-Reply-To: <488E2510.7070209@freescale.com>
No, it's not working for me :(
My pins is configured by u-boot so I disable init_ioports() function
call. Moreover the udbg0 console forks fine... I have no output at all
after "udbg_putc = NULL" line in the cpm_uart driver. As I see it the
cpm_uart driver doesn't run properly after udbg console has turned
off.....
2008/7/28 Scott Wood <scottwood@freescale.com>:
> Matvejchikov Ilya wrote:
>>
>> cpm@119c0 {
>> #address-cells = <1>;
>> #size-cells = <1>;
>> #interrupt-cells = <2>;
>> compatible = "fsl,mpc8280-cpm", "fsl,cpm2";
>
> Add "simple-bus" to this compatible list.
>
> Other than that, and that you should be using dts-v1, the tree looks fine.
> If adding "simple-bus" doesn't fix it, check your pin setup; pq2fads
> doesn't have an SMC serial port, so its platform file doesn't set up those
> pins.
>
> -Scott
>
>
next prev parent reply other threads:[~2008-07-29 6:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-28 19:43 No output from SMC1 console with the 2.6.26 kernel (PQ2FADS based board) Matvejchikov Ilya
2008-07-28 19:59 ` Scott Wood
2008-07-29 6:10 ` Matvejchikov Ilya [this message]
2008-07-29 15:33 ` No output from SMC1 console with the 2.6.26 kernel (8xx " Ben Gardiner
2008-07-29 18:36 ` Matvejchikov Ilya
2008-07-29 19:39 ` Scott Wood
2008-07-30 9:37 ` Matvejchikov Ilya
2008-07-30 15:45 ` Scott Wood
2008-08-19 11:13 ` Matvejchikov Ilya
2008-08-19 16:13 ` Scott Wood
2008-08-21 13:04 ` Matvejchikov Ilya
2008-07-29 19:36 ` Scott Wood
2008-07-30 13:36 ` Ben Gardiner
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=8496f91a0807282310r5e70fe01v85b2ff2da7a80416@mail.gmail.com \
--to=matvejchikov@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--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;
as well as URLs for NNTP newsgroup(s).