linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Schocher <hs@denx.de>
To: Vitaly Bordug <vbordug@ru.mvista.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Compile Error using SMC1 on a MPC8272 for 2.6.19-rc4
Date: Mon, 04 Dec 2006 13:09:10 +0100	[thread overview]
Message-ID: <1165234150.6011.77.camel@Zeus.EmbLux> (raw)
In-Reply-To: <20061111001527.1274c7f4@localhost.localdomain>

Hello Vitaly,

Am Samstag, den 11.11.2006, 00:15 +0300 schrieb Vitaly Bordug:
> On Fri, 10 Nov 2006 12:53:14 +0100
> Heiko Schocher wrote:
> > I tried to compile the Linux Kernel 2.6.19-rc5 with a MPC8272 CPU and
> > a console on SMC1, and get the following Compile Error:
> > 
> >   CC      drivers/serial/cpm_uart/cpm_uart_cpm2.o
> > drivers/serial/cpm_uart/cpm_uart_cpm2.c: In function
> > 'cpm_uart_init_portdesc':
> > drivers/serial/cpm_uart/cpm_uart_cpm2.c:364: warning: assignment makes
> > integer from pointer without a cast
> > drivers/serial/cpm_uart/cpm_uart_cpm2.c:368: error: invalid type
> > argument of 'unary *'
> > make[3]: *** [drivers/serial/cpm_uart/cpm_uart_cpm2.o] Error 1
> > make[2]: *** [drivers/serial/cpm_uart] Error 2
> > make[1]: *** [drivers/serial] Error 2
> > make: *** [drivers] Error 2
> > 
> > The following Code solves the problem:
> > 
> > diff --git a/drivers/serial/cpm_uart/cpm_uart_cpm2.c
> > b/drivers/serial/cpm_uart/cpm_uart_cpm2.c
> > index 0599030..bb0a6c1 100644
> > --- a/drivers/serial/cpm_uart/cpm_uart_cpm2.c
> > +++ b/drivers/serial/cpm_uart/cpm_uart_cpm2.c
> > @@ -349,7 +349,7 @@ void cpm_uart_freebuf(struct uart_cpm_po
> >  int cpm_uart_init_portdesc(void)
> >  {
> >  #if defined(CONFIG_SERIAL_CPM_SMC1) ||
> > defined(CONFIG_SERIAL_CPM_SMC2)
> > -	u32 addr;
> > +	u32 *addr;
> >  #endif
> >  	pr_debug("CPM uart[-]:init portdesc\n");
> >  
> Yes, but that is not the only issue. I am working on that.

Yes, i think so too, because I tried the 2.6.19 Kernel on a board with
MPC8272, SMC1-2 and SMCC1-4 used as serial port, SMC2 as Console, and
it dont work ... with a 2.6.14er Kernel it worked ...

I had to change the following Code:
----------------------------------------------------------------------------
diff --git a/drivers/serial/cpm_uart/cpm_uart_cpm2.c
b/drivers/serial/cpm_uart/cpm_uart_cpm2.c
index bb0a6c1..4ee1bfc 100644
@@ -349,7 +351,7 @@ void cpm_uart_freebuf(struct uart_cpm_po
 int cpm_uart_init_portdesc(void)
 {
 #if defined(CONFIG_SERIAL_CPM_SMC1) || defined(CONFIG_SERIAL_CPM_SMC2)
-	u32 *addr;
+	u16 *addr;
 #endif
 	pr_debug("CPM uart[-]:init portdesc\n");
 
----------------------------------------------------------------------------

With this change, Linux comes up, with SMC1-2 and SCC1-4 as serial port,
and a console on SMC2 :-)

If I use the Plattform Bus:
I have also to apply the patch from:
http://ozlabs.org/pipermail/linuxppc-embedded/2006-November/025101.html

to bring it up working.

thanks
Heiko

  reply	other threads:[~2006-12-04 12:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-10 11:53 Compile Error using SMC1 on a MPC8272 for 2.6.19-rc4 Heiko Schocher
2006-11-10 21:15 ` Vitaly Bordug
2006-12-04 12:09   ` Heiko Schocher [this message]
2006-12-04 15:00     ` Vitaly Bordug

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=1165234150.6011.77.camel@Zeus.EmbLux \
    --to=hs@denx.de \
    --cc=linuxppc-embedded@ozlabs.org \
    --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).