From: pebolle@tiscali.nl (Paul Bolle)
To: kernelnewbies@lists.kernelnewbies.org
Subject: i2c-dev
Date: Thu, 23 Oct 2014 20:15:53 +0200 [thread overview]
Message-ID: <1414088153.17121.40.camel@x220> (raw)
In-Reply-To: <20141022172729.GA3098@vega.jjdev.com>
On Wed, 2014-10-22 at 13:27 -0400, John de la Garza wrote:
> On Wed, Oct 22, 2014 at 06:35:02PM +0200, Paul Bolle wrote:
> > Having looked into this a bit, but failing to come up with something
> > helpful, I decided to ask some additional info.
> >
> > On Tue, 2014-10-21 at 21:54 -0400, John de la Garza wrote:
> > > I have my kernel
> >
> > Which version (roughly)?
>
> Linux vega 3.18.0-rc1+ #71 SMP Wed Oct 22 00:49:21 EDT 2014 x86_64 GNU/Linux
> >
> > > built with dev-i2c and i2c_i801
> >
> > .config, please?
> >
> see below
>
> > > but do not have
> > > a /dev entry.
> > >
> > > lspci shows this:
> > > 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 06)
> >
> > What are the PCI vendor and device codes? See "lspci -nn".
> >
> 00:1f.3 SMBus [0c05]: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller [8086:3b30] (rev 06)
> > > dmesg shows this:
> > > [ 1.566003] i801_smbus 0000:00:1f.3: enabling device (0000 -> 0003)
I'm afraid I can't really help you here, sorry. That is, except for the
obvious question whether this is a regression (ie, do releases v3.17 or
earlier show something in /sys/bus/i2c/devices/?) or a configuration
issue (perhaps a distribution provided kernel does show what you want).
Hope this helps,
Paul Bolle
next prev parent reply other threads:[~2014-10-23 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 1:54 i2c-dev John de la Garza
2014-10-22 16:35 ` i2c-dev Paul Bolle
[not found] ` <20141022172729.GA3098@vega.jjdev.com>
2014-10-23 18:15 ` Paul Bolle [this message]
2014-10-26 16:04 ` i2c-dev John de la Garza
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=1414088153.17121.40.camel@x220 \
--to=pebolle@tiscali.nl \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).