From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13288 invoked by alias); 2 Jan 2013 07:07:24 -0000 Received: (qmail 13265 invoked by uid 22791); 2 Jan 2013 07:07:23 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_SPAMHAUS_DROP,KHOP_THREADED,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 02 Jan 2013 07:07:18 +0000 Received: from localhost (hagrid.ecoscentric.com [127.0.0.1]) by mail.ecoscentric.com (Postfix) with ESMTP id 6F57E4680011 for ; Wed, 2 Jan 2013 07:07:17 +0000 (GMT) Received: from mail.ecoscentric.com ([127.0.0.1]) by localhost (hagrid.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EQ0qv-tioo3E; Wed, 2 Jan 2013 07:07:15 +0000 (GMT) From: bugzilla-daemon@bugs.ecos.sourceware.org To: ecos-patches@ecos.sourceware.org Subject: [Bug 1001397] I2C driver for Kinetic microcontrollers X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: eCos X-Bugzilla-Component: Patches and contributions X-Bugzilla-Keywords: X-Bugzilla-Severity: enhancement X-Bugzilla-Who: mjones@linear.com X-Bugzilla-Status: NEEDINFO X-Bugzilla-Priority: low X-Bugzilla-Assigned-To: unassigned@bugs.ecos.sourceware.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: In-Reply-To: References: X-Bugzilla-URL: http://bugs.ecos.sourceware.org/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Date: Wed, 02 Jan 2013 07:07:00 -0000 Message-Id: <20130102070715.B23754680001@mail.ecoscentric.com> Mailing-List: contact ecos-patches-help@ecos.sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: ecos-patches-owner@ecos.sourceware.org X-SW-Source: 2013-01/txt/msg00006.txt.bz2 Please do not reply to this email. Use the web interface provided at: http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001397 --- Comment #35 from Mike Jones 2013-01-02 07:07:14 GMT --- I read the reference on I2C. I am pretty clear how the standard I2C API works in terms of making transactions using locking, etc. I am making a simple app with no tasks, just to run in main. I assume there is some magic for making a cyg_i2c_bus and then you can make some cyg_i2c_device. Then call freescale_i2c_init(...) I see a macro for creating the bus, but it has to pass some function pointers. I assume there is some code for that, or I have to know all the magic things to put in the macro. Once there is a device, it is not clear if the standard API can use it. And if it can, I am not certain if it would behave any different that the Freescale specific API commands. So I think I mainly need to know how to get things glued together and relationship between the generic vs Freescale API. I don't need to know how to use the API to send and receive data. -- Configure bugmail: http://bugs.ecos.sourceware.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.