From: Michael.Kang <blackfin.kang@gmail.com>
To: "mike zheng" <mail4mz@gmail.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 2.6 system stuck with one line change in platform_init()
Date: Sat, 11 Aug 2007 10:09:42 +0800 [thread overview]
Message-ID: <a7f827420708101909r20f0abe6m5af0c180702d109b@mail.gmail.com> (raw)
In-Reply-To: <5c9cd53b0708101901n62e732a4m8fba21b592f5dc95@mail.gmail.com>
On 8/11/07, mike zheng <mail4mz@gmail.com> wrote:
> Hi All,
>
> In order to debug the 8548 CDS BSP of kernel 2.6, I want setup serial port
> with UART on mpc85xx as early as possible. . I add the register access code
> at the beginning of platform_init(). However the system just hanging there
> with this line. If I comment out this
> line"WRITE8_ADDR(M85xx_EIIADDR,0)", then linux kernel runs
> well.
>
> Thanks in advance,
>
> Mike Z
>
> Here is the code of my mpc85xx_cds_common.c:
>
> #define WRITE8_ADDR(address, value) \
> ((*((volatile u8 *)(address))) = (u8)(value))
>
> #define M85xx_EII_ADDR 0xe0004500
>
> void __init
> platform_init(unsigned long r3, unsigned long r4, unsigned long r5,
> unsigned long r6, unsigned long r7)
> {
> /* parse_bootinfo must always be called first */
> parse_bootinfo(find_bootinfo());
>
> /* Now we try to access register of UART */
> WRITE8_ADDR(M85xx_EII_ADDR, 0);
where is M85xx_EII_ADDR declearation? If the address need to
be io_remap first?
> ....
> }
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>
--
www.skyeye.org
prev parent reply other threads:[~2007-08-11 2:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-11 2:01 2.6 system stuck with one line change in platform_init() mike zheng
2007-08-11 2:09 ` Michael.Kang [this message]
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=a7f827420708101909r20f0abe6m5af0c180702d109b@mail.gmail.com \
--to=blackfin.kang@gmail.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mail4mz@gmail.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).