All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: Andres Marquez <amarquez@edgeaccess.net>
Cc: Nirmala Kakkuppi <nkakkuppi@edgeaccess.net>,
	linuxppc-dev@ozlabs.org, Haysam Rachid <hrachid@edgeaccess.net>
Subject: Re: Enable Serial Management Controller (SMC) in MPC8265
Date: Mon, 27 Apr 2009 10:19:44 -0500	[thread overview]
Message-ID: <49F5CD10.9010801@freescale.com> (raw)
In-Reply-To: <1240839625.3643.19.camel@localhost.localdomain>

Andres F Marquez wrote:
>      After struggling for several days with this issue we have finally
> taken a different approach to solve our problem. We wanted to interface
> our CPU (MPC8265) with a FPGA through a serial connection. Now, we are
> using a parallel interface through the data bus (defining a new memory
> region in uboot -an additional chip select).

That sounds much better.

>      We tried enabling SCC's and SMC's through the kernel configuration
> in ltib,

LTIB doesn't alter device trees AFAIK...  Unless you have more than two 
CPM serial nodes, you won't get more than ttyCPM0 and ttyCPM1.

> but we were always getting the same tty devices device under
> "/dev". No matter how many SCC's or SMC's we enable we were always
> getting only /dev/ttyCPM0 and /dev/ttyCPM1. 

Do you have a static /dev, or are you running mdev or udev?  If the 
latter, then any changes in the kernel or device tree are not going to 
automatically show up in /dev.

-Scott

      reply	other threads:[~2009-04-27 15:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-23 23:50 Enable Serial Management Controller (SMC) in MPC8265 Andres F Marquez
2009-04-24 16:02 ` Scott Wood
2009-04-27 13:40   ` Andres F Marquez
2009-04-27 15:19     ` Scott Wood [this message]

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=49F5CD10.9010801@freescale.com \
    --to=scottwood@freescale.com \
    --cc=amarquez@edgeaccess.net \
    --cc=hrachid@edgeaccess.net \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=nkakkuppi@edgeaccess.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.