From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dirk Behme Date: Tue, 19 May 2009 16:36:29 +0200 Subject: [U-Boot] [PATCH v2] OMAP3: Introduce CONFIG option for power code In-Reply-To: <20090518215307.GP17539@game.jcrosoft.org> References: <1242453391-25176-1-git-send-email-dirk.behme@googlemail.com> <20090518215307.GP17539@game.jcrosoft.org> Message-ID: <4A12C3ED.3070901@googlemail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de 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 >> --- > 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