All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Kari Laine <klaine8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
	linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: I2C -bus programming
Date: Fri, 14 Aug 2009 12:23:34 +0100	[thread overview]
Message-ID: <4A854936.5060409@gmail.com> (raw)
In-Reply-To: <4A8491E3.4070907-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>

Copied to i2c mailing list.

> Dear List,
>
> this is my first post here and I am not sure if this is a suitable topic
> here. Anyway I have a Velleman K8000 IO-card and it uses I2C over
> parallel port to communicate.
>
> when I modprobe i2c-parport it does not complain. I tested without card
> connected and it complained so it seems to find the card.
>
> modprobe pcf8591
>
> modprobe i2c-core
>
> modprobe i2c-dev
>
> I am not sure I am doing it right. Should i2c-core probed first ?
>
> anyway now I have
>
> /dev/i2c-0  /dev/i2c-1
>
> Now I don't know whether these i2c-devices refer to this Velleman  board
> or some other i2c-device which happen to be in the computer...
>
> If these devices probably refer to Velleman - then how I can refer
> different i2c-devices on the board.
>
>
> I am totally new to this i2c thing (reading spec at the moment but it
> does not help much with Linux).
>
> I would be very greatfull if some could point me the way - thanks.
>
> Best Regards
> Kari Laine
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>   

WARNING: multiple messages have this Message-ID (diff)
From: Jonathan Cameron <Jonathan.Cameron@gmail.com>
To: Kari Laine <klaine8@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-i2c@vger.kernel.org
Subject: Re: I2C -bus programming
Date: Fri, 14 Aug 2009 12:23:34 +0100	[thread overview]
Message-ID: <4A854936.5060409@gmail.com> (raw)
In-Reply-To: <4A8491E3.4070907@gmail.com>

Copied to i2c mailing list.

> Dear List,
>
> this is my first post here and I am not sure if this is a suitable topic
> here. Anyway I have a Velleman K8000 IO-card and it uses I2C over
> parallel port to communicate.
>
> when I modprobe i2c-parport it does not complain. I tested without card
> connected and it complained so it seems to find the card.
>
> modprobe pcf8591
>
> modprobe i2c-core
>
> modprobe i2c-dev
>
> I am not sure I am doing it right. Should i2c-core probed first ?
>
> anyway now I have
>
> /dev/i2c-0  /dev/i2c-1
>
> Now I don't know whether these i2c-devices refer to this Velleman  board
> or some other i2c-device which happen to be in the computer...
>
> If these devices probably refer to Velleman - then how I can refer
> different i2c-devices on the board.
>
>
> I am totally new to this i2c thing (reading spec at the moment but it
> does not help much with Linux).
>
> I would be very greatfull if some could point me the way - thanks.
>
> Best Regards
> Kari Laine
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>   


  parent reply	other threads:[~2009-08-14 11:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13 22:21 I2C -bus programming Kari Laine
     [not found] ` <4A8491E3.4070907-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-08-14 11:23   ` Jonathan Cameron [this message]
2009-08-14 11:23     ` Jonathan Cameron
     [not found]     ` <4A854936.5060409-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2009-09-12  9:12       ` Jean Delvare
2009-09-12  9:12         ` Jean Delvare

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=4A854936.5060409@gmail.com \
    --to=jonathan.cameron-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=klaine8-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=linux-kernel-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 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.