linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Vitaly Bordug <vbordug@ru.mvista.com>
Cc: Russell McGuire <rmcguire@uwbt.com>, linuxppc-embedded@ozlabs.org
Subject: Re: MPC83xx:  ns16550.c - 'SERIAL_PORT_DFNS' undeclared?
Date: Tue, 23 Jan 2007 08:00:35 +1100	[thread overview]
Message-ID: <1169499635.1582.10.camel@localhost.localdomain> (raw)
In-Reply-To: <20070119233454.6c096bb3@localhost.localdomain>

On Fri, 2007-01-19 at 23:34 +0300, Vitaly Bordug wrote:
> On Fri, 19 Jan 2007 12:14:04 -0800
> Russell McGuire wrote:
> 
> > Ben,
> > 
> > That could be the problem
> > 
> > I am building using ARCH=ppc
> > 
> > What is the difference between the two?
> Newer targets appear within arch/powerpc... Concerning your question, 
> you seem to add new board hence you'll have to do those SERIAL_PORT_DFNS
> in board-specific header file - grep for them inside arch/ppc for reference (if
> that code is still there of course).

Note that SERIAL_PORT_DFNS are pretty much deprecated too :-) Nobody
cared fixing arch/ppc but for arch/powerpc, you should use one of the
new mecanisms, if possible using the device-tree / platform devices.

Ben.

  reply	other threads:[~2007-01-22 21:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-19 19:28 MPC83xx: ns16550.c - 'SERIAL_PORT_DFNS' undeclared? Russell McGuire
2007-01-19 19:58 ` Ben Warren
2007-01-19 20:14   ` Russell McGuire
2007-01-19 20:32     ` Ben Warren
2007-01-19 20:34     ` Vitaly Bordug
2007-01-22 21:00       ` Benjamin Herrenschmidt [this message]
2007-01-19 21:07     ` Timur Tabi

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=1169499635.1582.10.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=rmcguire@uwbt.com \
    --cc=vbordug@ru.mvista.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).