From: Brent Cook <bcook@bpointsys.com>
To: linuxppc-embedded@ozlabs.org
Cc: "Kiran Kumar.A" <kiranf5@lycos.com>
Subject: Re: regarding mvme6100 on kernel 2.6.13
Date: Tue, 30 May 2006 10:12:07 -0500 [thread overview]
Message-ID: <200605301012.07607.bcook@bpointsys.com> (raw)
In-Reply-To: <20060530140929.88FBD3384B@ws7-3.us4.outblaze.com>
On Tuesday 30 May 2006 09:09, Kiran Kumar.A wrote:
> Hi all,
>
> I'm porting mvme6100 for 2.6.13.
> But its hanging after "Now Booting the kernel.."
>
> Can anybody guide me in this regard.
>
> thanks and regards
Eh, it's probably not hanging at all - you're just not seeing anything because
the device naming scheme changed and the serial console not getting
initialized correctly. Be sure that in your platform_notify function has
a '.' in the platform device name - this was added around 2.6.11 or so.
An example from another board I have:
static int xes_mv64x60_platform_notify(struct device *dev)
{
static struct {
char *bus_id;
void ((*rtn) (struct platform_device * pdev));
} dev_map[] = {
#ifdef CONFIG_SERIAL_MPSC
{
MPSC_CTLR_NAME ".0", xes_mv64x60_fixup_mpsc_pdata}, {
MPSC_CTLR_NAME ".1", xes_mv64x60_fixup_mpsc_pdata},
#endif
}
Also, be sure to enable early boot messages - they help a lot. Also, don't
overlook setting console=ttyMM0,9600 in the kernel args.
- Brent
prev parent reply other threads:[~2006-05-30 15:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-30 14:09 regarding mvme6100 on kernel 2.6.13 Kiran Kumar.A
2006-05-30 15:12 ` Brent Cook [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=200605301012.07607.bcook@bpointsys.com \
--to=bcook@bpointsys.com \
--cc=kiranf5@lycos.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 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).