From: Jean Delvare <jdelvare@suse.de>
To: Tommy Lee <tommyclee101908sun@gmail.com>
Cc: linux-i2c@vger.kernel.org
Subject: Re: gather_i2c_busses()
Date: Tue, 26 Jul 2022 10:23:58 +0200 [thread overview]
Message-ID: <20220726102358.3236e000@endymion.delvare> (raw)
In-Reply-To: <CAGJPcGaO1j57dZvRGR789m5HZ5s5tUaSomxKVGuhFhimQhGC5Q@mail.gmail.com>
Hi Tommy,
On Mon, 25 Jul 2022 18:00:55 -0700, Tommy Lee wrote:
> Hi Linux-i2c,
You got the list address wrong, I'm fixing it (it's a dash, not an
underscore).
> My platform is ASUS Vivobook e203 running Ubuntu 22.04 LTS. The i2c-tools
> src package I installed is 3.1.2. The make command works. But the
> "i2cdetect -l" execution gave me the following alert. I discovered that
> the /proc/bus/i2c used by the 3.1.2 gather_i2c_busses() has been moved
> to /sys/bus/i2c in Ubuntu22.04 LTS.
/proc/bus/i2c has not been replaced by /sys/bus/i2c in Ubuntu 22.04.
It's a changed that happened almost 2 decades ago. Even kernel 2.6.0
had it already.
> I replaced /proc/bus/i2c with
> /sys/bus/i2c in gather_i2c_busses() and replaced adapters[count].name with
> adapters->nr. Running tools/i2cdetect shows 0 on adapters->nr.
That change makes no sense at all, so it's not surprising it doesn't
work.
The problem is that you are using i2c-tools-3.1 which is a legacy
branch that can only work with very old kernels. It is in maintenance
mode, hasn't received any development since 8 years and really nobody
should be using it any longer.
Why don't you just use i2c-tools version 4.3 which is already packaged
in your distribution?
--
Jean Delvare
SUSE L3 Support
parent reply other threads:[~2022-07-26 8:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAGJPcGaO1j57dZvRGR789m5HZ5s5tUaSomxKVGuhFhimQhGC5Q@mail.gmail.com>]
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=20220726102358.3236e000@endymion.delvare \
--to=jdelvare@suse.de \
--cc=linux-i2c@vger.kernel.org \
--cc=tommyclee101908sun@gmail.com \
/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