From: Romit Dasgupta <romit@ti.com>
To: "Gadiyar, Anand" <gadiyar@ti.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Strange boot messages on mainline + omap3_defconfig
Date: Fri, 18 Dec 2009 18:07:01 +0530 [thread overview]
Message-ID: <4B2B776D.8000709@ti.com> (raw)
In-Reply-To: <5A47E75E594F054BAF48C5E4FC4B92AB031DB9AB9D@dbde02.ent.ti.com>
Gadiyar, Anand wrote:
> I get some "mux: Unknown ball ..." messages booting
> v2.6.33-rc1 from Linux' tree (built with the omap3_defconfig).
>
> This was on a 3630 SDP.
>
> Won't be looking at this for a while, so just reporting it.
>
> - Anand
>
> 0x588
> [ 0.000000] mux: Unknown ball offset 0x58a
> [ 0.000000] mux: Unknown ball offset 0x58c
> [ 0.000000] mux: Unknown ball offset 0x58e
> [ 0.000000] mux: Unknown ball offset 0x590
> [ 0.000000] mux: Unknown ball offset 0x578
> [ 0.000000] mux: Unknown ball offset 0x57a
> [ 0.000000] mux: Unknown ball offset 0x57c
> [ 0.000000] mux: Unknown ball offset 0x57e
> [ 0.000000] mux: Unknown ball offset 0x580
> [ 0.000000] mux: Unknown ball offset 0x582
> [ 0.000000] mux: Unknown ball offset 0x584
> [ 0.000000] mux: Unknown ball offset 0x586
> [ 0.000000] mux: Unknown ball offset 0x570
> [ 0.000000] mux: Unknown ball offset 0x572
> [ 0.000000] mux: Unknown ball offset 0x40
> [ 0.000000] mux: Unknown ball offset 0x0
> [ 0.000000] mux: Unknown ball offset 0x2
>
> ....
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
Try this in you .config
CONFIG_OMAP_PACKAGE_CBB=y
CONFIG_OMAP_PACKAGE_CUS=y
CONFIG_OMAP_PACKAGE_CBP=y
next prev parent reply other threads:[~2009-12-18 12:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 12:16 Strange boot messages on mainline + omap3_defconfig Gadiyar, Anand
2009-12-18 12:35 ` Romit Dasgupta
2009-12-18 12:37 ` Romit Dasgupta [this message]
2009-12-21 18:37 ` Tony Lindgren
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=4B2B776D.8000709@ti.com \
--to=romit@ti.com \
--cc=gadiyar@ti.com \
--cc=linux-omap@vger.kernel.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.