From: jacopo mondi <j.mondi@voltaelectronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] omap3 mux enabling
Date: Wed, 2 Feb 2011 15:50:43 +0100 [thread overview]
Message-ID: <20110202155043.6a624769@BlackBox> (raw)
Dear folks,
I'm very new to this community, please pardon me if I'm going to ask
something that seems obvious to the majority of you.
As I've seen digging through the list archives in later months there
was some discussions about mux state, and possible decoupling between
u-boot and linux kernel in doing pin multiplexing [1].
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).
After reading discussion [1] I just wanna know if it is needed to
manually enable MUX for recent u-boot versions as a consequence to
discussions or decisions which I'm not aware of and I was unable to
find in the list logs or in changelogs (since seraching for that in the
web site returns a 403 error[2])
Again, sorry if I'm missing something obvious for you all.
Just ask for details about how I'm doing multiplexing, I've inserted
none since they are not relevant to my main question.
thanks
jacopo
[1]http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/88443/focus=88451
[2]http://git.denx.de/?p=u-boot.git;a=blob_plain;f=CHANGELOG-before-U-Boot-1.1.5;hb=HEAD
next reply other threads:[~2011-02-02 14:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-02 14:50 jacopo mondi [this message]
2011-02-04 17:32 ` [U-Boot] omap3 mux enabling Alexander Holler
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=20110202155043.6a624769@BlackBox \
--to=j.mondi@voltaelectronics.com \
--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