Port-arm archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Raspberry Pi I2C implementation still broken?

Sorry for the delay... r/l is in the way.

In any case, I'm glad progress has been made :D. When I get the chance (whenever that is :/), I'll see if I can't fix some of the other bugs... I'm getting comfortable with the bus_space functions that NetBSD provides, and I think, combined with some Broadcom documentation, I should be able to fix the other issues.

-----Original Message----- From: Jonathan A. Kollasch
Sent: Thursday, January 22, 2015 1:13 PM
To: William D. Jones
Cc: port-arm%NetBSD.org@localhost
Subject: Re: Raspberry Pi I2C implementation still broken?

On Mon, Jan 05, 2015 at 11:31:54AM -0500, William D. Jones wrote:
Hello all,

According to the following bug report:

and mailing list posts:

Either the IOCTL or I2C driver the Raspberry Pi I2C implementation
is broken. I believe I may have found another bug in the
implementation by trying to read/write an I2C EEPROM using IOCTL,
but I'm guessing it is related to the already existing IOCTL issues
that cause writes to always succeed. It's also possible my sample
code is wrong :P. So, before I file a problem report: Has there been
any progress in fixing the above I2C write errors?

There has now;
(The ioctl was broken in certain situations.)

While port-arm/48855 and port-arm/48932 still remain, they should be easy
to fix.

Jonathan Kollasch

William D. Jones
Rowan University | ECE | 2012
Member IEEE
Member Tau Beta Pi
Message sent using 'Windows Live Mail' client.

Home | Main Index | Thread Index | Old Index