From: Jarkko Nikula <jhnikula@gmail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Koen Kooi <koen@dominion.thruhere.net>,
Laurent Epinat <laurent.epinat@cioinfoindus.fr>,
linux-omap@vger.kernel.org
Subject: Re: beagleboard expansion boards, was Trying to understand how to use new OMAP mux code
Date: Wed, 2 Jun 2010 17:14:27 +0300 [thread overview]
Message-ID: <20100602171427.5024be97.jhnikula@gmail.com> (raw)
In-Reply-To: <20100602135709.GK5980@atomide.com>
On Wed, 2 Jun 2010 16:57:10 +0300
Tony Lindgren <tony@atomide.com> wrote:
> > Problem is that amount of expansion boards is practically unlimited so
> > patching bootloader and board file could come quite maintenance effort.
> >
> > Of course there are some lets say generic boards but bunch of in-house,
> > DIY, etc. boards and there is no point to patch common bootloader and
> > kernel board files because of them.
>
> Just saveenv the kernel cmdline options in u-boot?
>
I meant that if kernel module could do muxing then there is no need the
user to change muxings for different add-on boards.
Works fine if you have one board but how about when amount of expansion
boards grow?
--
Jarkko
next prev parent reply other threads:[~2010-06-02 14:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-11 22:24 Trying to understand how to use new OMAP mux code Peter Barada
2010-03-11 22:48 ` Tony Lindgren
2010-03-12 4:48 ` Peter Barada
2010-03-12 5:42 ` Premi, Sanjeev
2010-06-02 10:09 ` Laurent Epinat
2010-06-02 11:21 ` Tony Lindgren
2010-06-02 11:46 ` Jarkko Nikula
2010-06-02 12:56 ` beagleboard expansion boards, was " Koen Kooi
2010-06-02 13:14 ` Jarkko Nikula
2010-06-02 13:57 ` Tony Lindgren
2010-06-02 14:06 ` Koen Kooi
2010-06-02 14:44 ` Tony Lindgren
2010-06-02 14:14 ` Jarkko Nikula [this message]
2010-06-02 14:45 ` Tony Lindgren
2010-06-02 14:54 ` Felipe Balbi
2010-06-02 15:01 ` Tony Lindgren
2010-06-02 16:12 ` Gadiyar, Anand
2010-06-03 13:42 ` Laurent Epinat
2010-06-03 14:06 ` Tony Lindgren
2010-06-03 14: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=20100602171427.5024be97.jhnikula@gmail.com \
--to=jhnikula@gmail.com \
--cc=koen@dominion.thruhere.net \
--cc=laurent.epinat@cioinfoindus.fr \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).