From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Joachim Meyer" <Jogi95@web.de>, linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Linux for ml310
Date: Wed, 9 Jan 2008 09:48:55 -0700 [thread overview]
Message-ID: <fa686aa40801090848m33170951paed90d8a79d41e32@mail.gmail.com> (raw)
In-Reply-To: <524178230@web.de>
always CC the mailing list when replying.
On 1/9/08, Joachim Meyer <Jogi95@web.de> wrote:
> arch/ppc/boot/common/ns16550.c:21: error: `XPAR_UARTNS550_0_CLOCK_FREQ_HZ' undeclared here (not in a function)
> arch/ppc/boot/common/ns16550.c:21: error: initializer element is not constant
> arch/ppc/boot/common/ns16550.c:21: error: (near initialization for `rs_table[0].baud_base')
> arch/ppc/boot/common/ns16550.c:21: error: `XPAR_INTC_0_UARTNS550_0_VEC_ID' undeclared here (not in a function)
> arch/ppc/boot/common/ns16550.c:21: error: initializer element is not constant
> arch/ppc/boot/common/ns16550.c:21: error: (near initialization for `rs_table[0].irq')
> arch/ppc/boot/common/ns16550.c:21: error: `XPAR_UARTNS550_0_BASEADDR' undeclared here (not in a function)
> arch/ppc/boot/common/ns16550.c:21: error: initializer element is not constant
> arch/ppc/boot/common/ns16550.c:21: error: (near initialization for `rs_table[0].iomem_base')
> arch/ppc/boot/common/ns16550.c:21: error: initializer element is not constant
> arch/ppc/boot/common/ns16550.c:21: error: (near initialization for `rs_table[0]'
You're xparameters_ml300.h file does not define
`XPAR_UARTNS550_0_CLOCK_FREQ_HZ', `XPAR_INTC_0_UARTNS550_0_VEC_ID' and
`XPAR_UARTNS550_0_BASEADDR'.
You'll need to look in your xparams file, find out what the real
#defines are for the uart and add fixups to xparameter.h so ns16550
can find them.
You're almost there! :-)
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next parent reply other threads:[~2008-01-09 16:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <524178230@web.de>
2008-01-09 16:48 ` Grant Likely [this message]
2008-01-11 11:40 Linux for ml310 Enno Lübbers
-- strict thread matches above, loose matches on Subject: below --
2008-01-10 15:44 Joachim Meyer
2008-01-10 15:48 ` Grant Likely
2008-01-10 10:13 Joachim Meyer
2008-01-10 14:54 ` Grant Likely
2008-01-09 19:00 Joachim Meyer
2008-01-09 19:16 ` Grant Likely
2008-01-09 17:29 Joachim Meyer
2008-01-09 18:07 ` Grant Likely
2008-01-09 15:19 Joachim Meyer
2008-01-09 15:24 ` Grant Likely
2008-01-07 20:41 Joachim Meyer
2008-01-07 21:02 ` Grant Likely
2008-01-09 21:29 ` Joachim Meyer
2008-01-09 22:10 ` Grant Likely
2008-01-14 18:42 ` greenlean
2008-01-14 18:47 ` Stephen Neuendorffer
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=fa686aa40801090848m33170951paed90d8a79d41e32@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=Jogi95@web.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).