Updating src tree:
P src/distrib/sets/lists/debug/module.mi
P src/distrib/sets/lists/modules/mi
P src/share/man/man4/route.4
P src/share/man/man4/tty.4
P src/sys/altq/altq_cbq.c
P src/sys/arch/acorn32/acorn32/rpc_machdep.c
P src/sys/arch/acorn32/doc/history
P
On Tuesday 17 Aug 2021 10:32:50 Jason Thorpe wrote:
> > On Aug 17, 2021, at 10:28 AM, Dave Tyson wrote:
> >
> > The device appears at address 0x77 (it's a BMP085) with i2cscan, the data
> > sheet indicates the read address=0xEF/write address=0xEE. I just put 0x77
> > in the address field and
This is an automatically generated notice of a NetBSD-current/i386
build failure.
The failure occurred on babylon5.netbsd.org, a NetBSD/amd64 host,
using sources from CVS date 2021.08.17.17.31.59.
An extract from the build.sh output follows:
nbmake[5]: stopped in
> On Aug 17, 2021, at 10:28 AM, Dave Tyson wrote:
>
> The device appears at address 0x77 (it's a BMP085) with i2cscan, the data
> sheet indicates the read address=0xEF/write address=0xEE. I just put 0x77 in
> the address field and assume the read/write bit on the wire is added based on
>
Dave,
As I recall, our I2C driver does not support block transfers. It is
necessary to read (or write) one byte at a time. So you would have
to loop from 0xAA-0xBF.
A long time ago I prepared patches for a small subset of our supported
I2C controllers, but they (the patches) are long gone.
I am trying to get data from a temperature/pressure sensor connected via i2c
to a banana pi running NetBSD current. I understand the I2C protocol but I am
having a bit of difficulty understanding what appears on the wire when the
I2C_IOCTL_EXEC is called with the various op commands. By trial
