From: Alexander Holler <holler@ahsoftware.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] omap3 mux enabling
Date: Fri, 04 Feb 2011 18:32:27 +0100 [thread overview]
Message-ID: <4D4C382B.8020400@ahsoftware.de> (raw)
In-Reply-To: <20110202155043.6a624769@BlackBox>
Am 02.02.2011 15:50, schrieb jacopo mondi:
> Mine is a question related to an end-user problem, since I'm no more
> able to do multiplexing for my DM3730 Beagleboard xM platform.
> The problem is quite simple, multiplexer configurations are totally
> ignored by u-boot (v2010.12), and I'm not able to do what I was used
> to do with my previous C4 board (with v2010.06 and v2010.03).
U-Boot still setups the multiplexing (and the kernel does that too).
If pin-multiplexing wouldn't work, the LEDs wouldn't go on and you
wouldn't be able to boot something.
So something else must be wrong on your side. Maybe your are using a
broken toolchain. Search the post for this month for the subject WARNING
to find something on that topic.
Regards,
Alexander
prev parent reply other threads:[~2011-02-04 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 14:50 [U-Boot] omap3 mux enabling jacopo mondi
2011-02-04 17:32 ` Alexander Holler [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=4D4C382B.8020400@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=u-boot@lists.denx.de \
/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