public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Romit Dasgupta <romit@ti.com>
Cc: "Gadiyar, Anand" <gadiyar@ti.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: Strange boot messages on mainline + omap3_defconfig
Date: Mon, 21 Dec 2009 10:37:16 -0800	[thread overview]
Message-ID: <20091221183715.GJ11397@atomide.com> (raw)
In-Reply-To: <4B2B776D.8000709@ti.com>

* Romit Dasgupta <romit@ti.com> [091218 04:35]:
> 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

Sounds like the select statement for your the package your
board is using is missing from arch/arm/mach-omap2/Kconfig.

Also looks like we're missing some checks that should be
in place trying to use a non-existing package..

Regards,

Tony

      reply	other threads:[~2009-12-21 18: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
2009-12-21 18:37   ` Tony Lindgren [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=20091221183715.GJ11397@atomide.com \
    --to=tony@atomide.com \
    --cc=gadiyar@ti.com \
    --cc=linux-omap@vger.kernel.org \
    --cc=romit@ti.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