linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: rdiz@alumni.deec.uc.pt
To: linuxppc-embedded@lists.linuxppc.org
Subject: Compiling kernel 2.6.7-rc1 for 8xx
Date: Thu, 27 May 2004 16:19:53 +0100 (WEST)	[thread overview]
Message-ID: <3321.62.48.238.11.1085671193.squirrel@alumni.deec.uc.pt> (raw)


Hi there,

I'm trying to compile kernel 2.6.7-rc1 for a Motorola 860T misc board. As
of now, I've also tried compiling 2.6.6, 2.6.5, the latest BenH 2.6
Development kernel and the latest Yellow Dog's latest kernel. All came
down to compile errors, and I'm now focusing on solving the problem for
2.6.7-rc1.

So, I'm getting errors when the compilation reaches file
arch/ppc/8xx_io/uart.c . Here is some of the output:

--------------------
arch/ppc/8xx_io/uart.c:86: warning: type defaults to `int' in declaration
of `DECLARE_TASK_QUEUE'
arch/ppc/8xx_io/uart.c:86: warning: parameter names (without types) in
function declaration
arch/ppc/8xx_io/uart.c: In function `serial_console_device':
arch/ppc/8xx_io/uart.c:149: storage class specified for parameter `rs_table'
arch/ppc/8xx_io/uart.c:149: parameter `rs_table' is initialized
arch/ppc/8xx_io/uart.c:151: warning: braces around scalar initializer
arch/ppc/8xx_io/uart.c:151: warning: (near initialization for `rs_table')
arch/ppc/8xx_io/uart.c:151: warning: excess elements in scalar initializer

...

arch/ppc/8xx_io/uart.c:185: field `tqueue' has incomplete type
arch/ppc/8xx_io/uart.c:186: field `tqueue_hangup' has incomplete type
arch/ppc/8xx_io/uart.c:202: warning: structure defined inside parms
arch/ppc/8xx_io/uart.c:202: storage class specified for parameter
`ser_info_t'
arch/ppc/8xx_io/uart.c:204: storage class specified for parameter `sercons'
arch/ppc/8xx_io/uart.c:204: parameter `sercons' is initialized
arch/ppc/8xx_io/uart.c:213: parse error before `*'
arch/ppc/8xx_io/uart.c:213: storage class specified for parameter
`change_speed'
arch/ppc/8xx_io/uart.c:213: warning: function declaration isn't a prototype
arch/ppc/8xx_io/uart.c:214: storage class specified for parameter
`rs_8xx_wait_until_sent'
arch/ppc/8xx_io/uart.c:216: parse error before `*'
arch/ppc/8xx_io/uart.c:218: storage class specified for parameter
`serial_paranoia_check'
--------------------

I subtracted some lines (...) that show warnings in the struct rs_table,
as there was one already declared (I didn't found it). When I compare the
uart.c file for 8xx with the one for 8260, I find that this structure is
the same, and no errors were found when compiling for it.

I'm trying to follow the errors, but I didn't found a link between the
structure rs_table and serial_console_device (where these warnings start).

Has anyone sucessfully compiled the kernel for 8xx PowerPC yet?

Any help would be apreciated,
Regards,
Ricardo Diz


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

             reply	other threads:[~2004-05-27 15:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-27 15:19 rdiz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-05-27 17:14 Compiling kernel 2.6.7-rc1 for 8xx rdiz
2004-05-27 20:55 ` Tom Rini
2004-05-28 11:34   ` rdiz

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=3321.62.48.238.11.1085671193.squirrel@alumni.deec.uc.pt \
    --to=rdiz@alumni.deec.uc.pt \
    --cc=linuxppc-embedded@lists.linuxppc.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).