From: Nishanth Menon <menon.nishanth@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] Add support for the KwikByte KBOC OMAP35xx board
Date: Sun, 12 Jul 2009 09:25:21 -0500 [thread overview]
Message-ID: <4A59F251.1050801@gmail.com> (raw)
In-Reply-To: <20090712131357.GE7218@game.jcrosoft.org>
Jean-Christophe PLAGNIOL-VILLARD said the following on 07/12/2009 08:13 AM:
>>> _sread*/\
>>> + MUX_VAL(CP(D2D_MBUSFLAG), (IEN | PTD | DIS | M0)) /*d2d_mbusflag*/\
>>> + MUX_VAL(CP(D2D_SBUSFLAG), (IEN | PTD | DIS | M0)) /*d2d_sbusflag*/\
>>> + MUX_VAL(CP(SDRC_CKE0), (IDIS | PTU | EN | M0)) /*sdrc_cke0*/\
>>> + MUX_VAL(CP(SDRC_CKE1), (IDIS | PTU | EN | M0)) /*sdrc_cke1*/
>>>
>> one more reason why the mux needs a big change in mux handling :( I
>> think we will end up with 1/2 a dozen crazy and code repetition for
>> each board... Arrggghhh...
>>
> NM: yes, it's really not easy to follow here
> do you plan to do it soon?
>
Been a little tied up recent days with "work load" hoping things to ease
down.. will try to send out a mux cleanup rev next weekend..
Regards,
Nishanth Menon
next prev parent reply other threads:[~2009-07-12 14:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 23:03 [U-Boot] [PATCH] Add support for the KwikByte KBOC OMAP35xx board christian at kwikbyte.com
2009-07-10 1:06 ` Nishanth Menon
2009-07-10 16:27 ` christian at kwikbyte.com
2009-07-12 13:13 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-12 13:35 ` Dirk Behme
2009-07-12 14:48 ` Wolfgang Denk
2009-07-12 15:06 ` Dirk Behme
2009-07-12 15:52 ` Wolfgang Denk
2009-07-12 15:20 ` Jean-Christophe PLAGNIOL-VILLARD
2009-07-12 15:34 ` Dirk Behme
2009-07-12 14:25 ` Nishanth Menon [this message]
2009-07-12 14:31 ` Dirk Behme
2009-07-12 14:50 ` [U-Boot] OMAP MUX handling improvement (was: Add support for the KwikByte KBOC OMAP35xx board) Nishanth Menon
2009-07-12 15:28 ` [U-Boot] OMAP MUX handling improvement Dirk Behme
2009-07-12 14:45 ` [U-Boot] [PATCH] Add support for the KwikByte KBOC OMAP35xx board Wolfgang Denk
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=4A59F251.1050801@gmail.com \
--to=menon.nishanth@gmail.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 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.