From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] OMAP3: Introduce CONFIG option for power code
Date: Tue, 19 May 2009 16:36:29 +0200 [thread overview]
Message-ID: <4A12C3ED.3070901@googlemail.com> (raw)
In-Reply-To: <20090518215307.GP17539@game.jcrosoft.org>
Dear Jean-Christophe,
Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 07:56 Sat 16 May , Dirk Behme wrote:
>> Some OMAP3 boards need control for external power companion
>> chips. Introduce a CONFIG option for this, to avoid Makefile
>> changes for each board.
>>
>> Signed-off-by: Dirk Behme <dirk.behme@googlemail.com>
>> ---
> IIRC the Revc Change it's companion chip is this code still compatible?
Yes, the code is still compatible. And yes, the companion chip
changed. And yes, this is quite confusing ;) Do you still remember
what I wrote in one of the other mails "only TI marketing department
might understand their chip naming"?
What I understood is that revision A & B BeagleBoards used "OEM"
companion chip you will only get in large quantities and manual is
NDA. Revision C now uses the "catalogue" device, you will e.g. able to
get from DigiKey and manual is publically available. So different chip
names, but compatible.
Recent U-Boot mainline is used on rev B and C boards without any
difference :)
Best regards
Dirk
prev parent reply other threads:[~2009-05-19 14:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-16 5:56 [U-Boot] [PATCH v2] OMAP3: Introduce CONFIG option for power code Dirk Behme
2009-05-18 21:53 ` Jean-Christophe PLAGNIOL-VILLARD
2009-05-19 14:36 ` Dirk Behme [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=4A12C3ED.3070901@googlemail.com \
--to=dirk.behme@googlemail.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.