linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Mark Zhan <rongkai.zhan@windriver.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 2/3] 82xx: Parse SMC serial device node in DTS
Date: Tue, 17 Jul 2007 22:29:35 +0800	[thread overview]
Message-ID: <1184682576.18501.62.camel@mark> (raw)
In-Reply-To: <200707171506.43102.arnd@arndb.de>

On Tue, 2007-07-17 at 15:06 +0200, Arnd Bergmann wrote:
> On Tuesday 17 July 2007, Mark Zhan wrote:
> > Yes, basically I agree what you say. That should be the right way. 
> > 
> > but, the current situation is that: in all DTS files that are using smc
> > or scc as uart device, all device node definitions have the same
> > "compatible" property -- "cpm_uart"
> > 
> > So what I do here is just following the upstream source tree.
> > 
> 
> Well, AFAICS, all of them currently use scc. The 8xx platforms don't
> even build correctly in the mainline kernel, so I guess it would
> be good to change them to also list fsl,cpm-smc in the compatible
> property.

That probably could be done by another series of patches, and I really
don't want to introduce those kinds of patches in my BSP patches. I
don't know if the 8xx/82xx series patches from Scott Wood will cover
this issue or not. We can wait for them to see where thing will go.

Thanks
mark zhan

  reply	other threads:[~2007-07-17 14:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-16  9:01 [PATCH 2/3] 82xx: Parse SMC serial device node in DTS Mark Zhan
2007-07-17  1:02 ` Arnd Bergmann
2007-07-17  4:49   ` Mark Zhan
2007-07-17 12:06     ` Arnd Bergmann
2007-07-17 13:53       ` Mark Zhan
2007-07-17 13:06         ` Arnd Bergmann
2007-07-17 14:29           ` Mark Zhan [this message]
2007-07-17 14:18             ` Arnd Bergmann
2007-07-17 16:06               ` Scott Wood
2007-07-17 15:12         ` Segher Boessenkool
2007-07-17 15:08       ` Segher Boessenkool
2007-07-17 14:22         ` Arnd Bergmann

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=1184682576.18501.62.camel@mark \
    --to=rongkai.zhan@windriver.com \
    --cc=arnd@arndb.de \
    --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;
as well as URLs for NNTP newsgroup(s).