lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y/0EIRsycj8EWjrz@ninjato>
Date:   Mon, 27 Feb 2023 20:27:29 +0100
From:   Wolfram Sang <wsa@...nel.org>
To:     Paul Menzel <pmenzel@...gen.mpg.de>
Cc:     Jean Delvare <jdelvare@...e.com>, linux-i2c@...r.kernel.org,
        LKML <linux-kernel@...r.kernel.org>, Dell.Client.Kernel@...l.com,
        Pali Rohár <pali@...nel.org>
Subject: Re: Accelerometer lis3lv02d is present on SMBus but its address is
 unknown, skipping registration

Hi Paul,

> What can a user do about this? It looks like the I2C addresses need to be
> added to `dell_lis3lv02d_devices[]` in `drivers/i2c/busses/i2c-i801.c`.

Complain to Dell about the missing address ;)

Until then:

> [   20.631866] i801_smbus 0000:00:1f.4: SPD Write Disable is set

# cd /sys/bus/pci/drivers/i801_smbus/0000\:00\:1f.4
# ls -d i2c-?

The last digit of the printout is the bus number. Then:

# modprobe i2c-dev
# i2cdetect <bus_number>

And post the output here. If you are brave and see that the address 0x1d
or 0x29 are printed in your output, you could try adding an entry to the
array you already mentioned above with the address you found. It may be
safer to do some sanity checking before, though.

Happy hacking,

   Wolfram


Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ