public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Lawnick <nospam_lawnick-Mmb7MZpHnFY@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Request for Clarification: old - legacy - new driver model
Date: Thu, 26 Feb 2009 16:16:46 +0100	[thread overview]
Message-ID: <go6bp4$i9k$1@ger.gmane.org> (raw)
In-Reply-To: <20090226142854.2b6f72e4-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>

Jean Delvare said the following:
> Hi Michael,
> 
> On Thu, 26 Feb 2009 12:09:52 +0100, Michael Lawnick wrote:
>> Therefore I asked for links in the OP so I can understand the idea of
>> the so called 'new I2C model'. The kernel documentation seems not to be
>> sufficient to achieve my goals.
>> Currently I'm waiting for 2 MUXes and an LM75, so I can connect them to
>> our current MUX-less board and start to play.
> 
> The documentation might not be perfect, right. It should become clearer
> once we get completely rid of the legacy model. Contributions to
> enhance the documentation are welcome, too.
> 
Just in short:
Don't feel criticized here. The documentation feels excellent for making
new devices. But what I'm searching for are 'inner' documents, which
AFAICS LINUX lacks almost completely.

Kind Regards,
Michael

  parent reply	other threads:[~2009-02-26 15:16 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-18 12:37 Request for Clarification: old - legacy - new driver model Michael Lawnick
2009-02-18 17:36 ` Wolfram Sang
     [not found]   ` <20090218173645.GD3049-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-02-19 14:17     ` Michael Lawnick
2009-02-20 12:53       ` Jean Delvare
     [not found]         ` <20090220135300.353cd53a-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-02-24 15:09           ` Michael Lawnick
2009-02-25  8:00             ` Jean Delvare
     [not found]               ` <20090225090002.2c31dbf1-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-02-26 11:09                 ` Michael Lawnick
2009-02-26 13:28                   ` Jean Delvare
     [not found]                     ` <20090226142854.2b6f72e4-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-02-26 15:16                       ` Michael Lawnick [this message]
2009-02-27  9:36                       ` Michael Lawnick
2009-03-05 14:57                         ` Jean Delvare
     [not found]                           ` <20090305155713.46ac1968-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-03-09 14:13                             ` Michael Lawnick
2009-03-09 14:38                               ` Jean Delvare
     [not found]                                 ` <20090309153851.6d92729e-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-03-10  6:45                                   ` Michael Lawnick
     [not found]                                     ` <20090310103609.0d756775@hyperion.delvare>
     [not found]                                       ` <20090310114215.181300@gmx.net>
     [not found]                                         ` <20090310114215.181300-hi6Y0CQ0nG0@public.gmane.org>
2009-03-10 11:47                                           ` Michael Lawnick

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='go6bp4$i9k$1@ger.gmane.org' \
    --to=nospam_lawnick-mmb7mzphnfy@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    /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