From owner-freebsd-bugs@freebsd.org Mon Jul 16 04:00:10 2018 Return-Path: Delivered-To: freebsd-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 58B75103C28F for ; Mon, 16 Jul 2018 04:00:10 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id E73B27D846 for ; Mon, 16 Jul 2018 04:00:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id A8322103C288; Mon, 16 Jul 2018 04:00:09 +0000 (UTC) Delivered-To: bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 96EB3103C283 for ; Mon, 16 Jul 2018 04:00:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 313077D83C for ; Mon, 16 Jul 2018 04:00:09 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 6A289D734 for ; Mon, 16 Jul 2018 04:00:08 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w6G408oI077847 for ; Mon, 16 Jul 2018 04:00:08 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w6G408PR077840 for bugs@FreeBSD.org; Mon, 16 Jul 2018 04:00:08 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 189914] i2c(8) utility does not work on Raspberry Pi Date: Mon, 16 Jul 2018 04:00:04 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: arm X-Bugzilla-Version: unspecified X-Bugzilla-Keywords: needs-patch, needs-qa X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: koobs@FreeBSD.org X-Bugzilla-Status: Open X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: mfc-stable10? mfc-stable11? X-Bugzilla-Changed-Fields: assigned_to short_desc keywords flagtypes.name rep_platform cc priority Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Jul 2018 04:00:10 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D189914 Kubilay Kocak changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|loos@FreeBSD.org |bugs@FreeBSD.org Summary|i2c(8) |i2c(8) utility does not | |work on Raspberry Pi Keywords| |needs-patch, needs-qa Flags| |mfc-stable10?, | |mfc-stable11? Hardware|Any |arm CC| |loos@FreeBSD.org Priority|Normal |--- --- Comment #8 from Kubilay Kocak --- Reset assignee (Luiz, last modified 4+ years), keep Luiz CC'd so someone el= se can take this if necessary. Given the age of this issue, it would be great to get (re)confirmation that base i2c(8) in CURRENT, as of today, still doesn't work on arm (RPi) The current patch apparently (comment 3) needs work, but more precisely, is= not in a state ready to commit (needs-patch). An updated patch against CURRENT = is required to progress this issue. --=20 You are receiving this mail because: You are the assignee for the bug.=