From: "Mark A. Greer" <mgreer@mvista.com>
To: Hegde Ashok-aah024 <ashok.hegde@motorola.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: MV64360 MPSC - console problem
Date: Mon, 07 Mar 2005 11:27:39 -0700 [thread overview]
Message-ID: <422C9D1B.1090400@mvista.com> (raw)
In-Reply-To: <772BCEF88A1DD91191F80011856715F301C2B56C@zin24exm01.ap.mot.com>
Hi Ashok.
Hegde Ashok-aah024 wrote:
>Hi All,
>
> I am trying to bring up linux-2.6.10 on ppc based system with
>MV64360(marvell controller).
>I am unable to use mpsc as the console, serial text debug messages are
>coming fine i.e. ppc_md.progress able to print properly on the serial port.
>I observed that when console_init() is being called from init/main.c none
>of our "mpsc" init functions are called.
>Also I see that there is no call to "console_initcall" in mpsc driver.
>According to my understanding this call is required in serial drivers used
>as consoles.
> I took this mpsc driver from "bk://source.mvista.com/linux-2.5-marvell" as
>mentioned in ppc mailinglist.
> Hardware has been tested with linux-2.4.20 flavour and it is absolutely
>fine.
>
>Appreciate any help.
>
>
It almost sounds like you don't have the mpsc config option selected.
Make sure that "Marvell MPSC serial port support" and "Support for
consol on Marvell MPSC serial port" under "Device Drivers"/"Character
devices"/"Serial drivers" are selected. If they don't appear then you
don't have CONFIG_PPC and/or CONFIG_MV64X60 defined. Those two should
be defined in arch/ppc/Kconfig under the appropriate board selection.
You also have to have the platform_data that is passed into the MPSC
driver set up correctly for it to work correctly.
Mark
next prev parent reply other threads:[~2005-03-07 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 10:33 MV64360 MPSC - console problem Hegde Ashok-aah024
2005-03-07 18:27 ` Mark A. Greer [this message]
2005-03-07 20:46 ` Mark A. Greer
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=422C9D1B.1090400@mvista.com \
--to=mgreer@mvista.com \
--cc=ashok.hegde@motorola.com \
--cc=linuxppc-embedded@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.