Date: Fri, 17 Mar 2017 07:04:53 -0000 From: "giorgio.zoppi" <mailbox@iqelite.com> To: freebsd-arm <freebsd-arm@freebsd.org> Subject: freebsd-arm, tienes un mensaje de giorgio.zoppi Message-ID: <20170317070453.1462.91784@mail2.iqelite.com>
next in thread | raw e-mail | index | archive | help
Hola freebsd-arm, Tienes un mensaje de giorgio.zoppi en IQ Elite para ti. = Haz click aqui a.iqelite.com/j/Yf9HA8/md1/?hg=3DhZkcSD8ECA para leer el men= saje = El equipo de IQ Elite --------------------------------------------------------------------------- Este mensaje estaba destinado a freebsd-arm@freebsd.org. Si no deseas segui= r recibiendo mensajes de IQ Elite, haz click en este enlace: a.iqelite.com/= common/unsubscribe/?code=3D888dd5bb&email=3Dfreebsd-arm@freebsd.org.&hg=3Dh= ZkcSD8ECA IQ Elite es un servicio con oficina principal en: C/ Gran de Gr= =C3=A0cia 15, 2=C2=BA 1=C2=AA, 08012 Barcelona, Espa=C3=B1a. ---------------------------------------------------------------------------= =20 From owner-freebsd-arm@freebsd.org Fri Mar 17 15:58:13 2017 Return-Path: <owner-freebsd-arm@freebsd.org> Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id B029CD10F66 for <freebsd-arm@mailman.ysv.freebsd.org>; Fri, 17 Mar 2017 15:58:13 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-it0-x231.google.com (mail-it0-x231.google.com [IPv6:2607:f8b0:4001:c0b::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7F4D11377 for <freebsd-arm@freebsd.org>; Fri, 17 Mar 2017 15:58:13 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-it0-x231.google.com with SMTP id g138so31251767itb.0 for <freebsd-arm@freebsd.org>; Fri, 17 Mar 2017 08:58:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=ahLuQ8yw3vd4EYb2KWEEjfezydShPiGdC06kfeq9nXM=; b=TMx+fym1APPWj3UyfWkFJJxbGfyLkdvoAr0N4wt2MVH33BRBtb4uzEGxJ33llHwiQ/ imOFxWqFs4WKqrliNAPdarZY6i9JOjTitw4cy5/OVWwjw4JaOrrJa+Ok14JxXy2EJ6bf F3aNUUU98+/ngQHjfxD3ZBz6bYmX3MGEsxX/KLBv9XMqnhCCEjNPQPSLs3Veyj8ZFI9n 2SqMUJuYshL3vBFVIatdvKlTOH/Z39kan/tjnLZjkJU+DDRj+ZCOihcNFI1aX/m+u2oi NXXZ9JPCJKuN5k4U+Qzp5TkU4ZA5dL42tiC6TgFp8vMKF3PjsnTVmJ9lCqttipz8scXx G6TQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=ahLuQ8yw3vd4EYb2KWEEjfezydShPiGdC06kfeq9nXM=; b=YiWpJuM9igl8VgdM4lB8xLYG2l7OwNneIySu4xG7NVRYwQHdoFZJYxEFzdU1Oo9K2k /CV9nBqifhPn1dsV129xVxDmKK36ntWL5lbMFCrBJZHTROKSpEiiBqlhY5ax4MBynZ/I JHafwBMeXeFdcol8LfBokinny2bCTX/G5JvSUy5MokQxr3JQWmxlQUulUzdpmbfee8ZW lBZt31UyJGrbtAmUqBvU7H2pCnzF4PdlCS67kCAnQ7WzTK6jI0JxOH3TIKgdwLDtwyKi YmCjOmZFiblCANtvPH50ebYknw5ncyLhPGBBBMINy9vgeVMmt/QqyYtDKkBOZSSQ8TsV T+Kg== X-Gm-Message-State: AFeK/H0f8gA2b7mQmRoIUz6A3d3EZrsRE/EL8VJtZqvezzcQ9lPfvGdiJPZhY0Aq8YARH53NukAXY+CLIzbYHQ== X-Received: by 10.36.34.212 with SMTP id o203mr3230471ito.103.1489766274839; Fri, 17 Mar 2017 08:57:54 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 10.79.134.129 with HTTP; Fri, 17 Mar 2017 08:57:54 -0700 (PDT) X-Originating-IP: [69.53.246.16] In-Reply-To: <201703170244.v2H2ibXc013800@jwlab.FEITH.COM> References: <201703170244.v2H2ibXc013800@jwlab.FEITH.COM> From: Warner Losh <imp@bsdimp.com> Date: Fri, 17 Mar 2017 09:57:54 -0600 X-Google-Sender-Auth: DxsQXTdkTG_d-mAEeUp4GlOZkKM Message-ID: <CANCZdfoE-tp=N-kuezS3zbaJYsKk5avOgWyUDtd4j5CW=SNkNQ@mail.gmail.com> Subject: Re: Making INTRNG a requirement on armv6 To: John Wehle <john@feith.com> Cc: Ganbold Tsagaankhuu <ganbold@gmail.com>, "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org> Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." <freebsd-arm.freebsd.org> List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-arm>, <mailto:freebsd-arm-request@freebsd.org?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arm/>; List-Post: <mailto:freebsd-arm@freebsd.org> List-Help: <mailto:freebsd-arm-request@freebsd.org?subject=help> List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-arm>, <mailto:freebsd-arm-request@freebsd.org?subject=subscribe> X-List-Received-Date: Fri, 17 Mar 2017 15:58:13 -0000 On Thu, Mar 16, 2017 at 8:44 PM, John Wehle <john@feith.com> wrote: >> As for Amlogic ones, iirc, John did some tests on his devices with INTRNG >> in December last year. > > The primary issue is regarding the older interrupt controller used on > the aml8726-m3 and also present on the aml8726-m6. I did the original > porting work using the aml8726-m6 with the older interrupt controller > which seemed to work fine ... there didn't seem to be any interrupts > being lost. It was only towards the end of the porting work that I > switched the aml8726-m6 (which happens to have both the older controller > and a GIC) to using the GIC. > > Back in December 2016 the aml8726-m6 (and -m8b) passed a smoke test using > INTRNG with the GIC. Disabling INTRNG caused the aml8726-m3 and the > aml8726-m6 (configured for the older interrupt controller) to "lose" > clock interrupts. > > I did at that time see about updating the older Amlogic interrupt code > to use INTRNG which was a pretty straight forward effort, though even > with the updated code the older interrupt controller still suffered > from "lost" clock interrupts. Unfortunately my attentions (as is > probably evident) have been elsewhere so the "lost" clock interrupts > issue is unresolved. > > I can see about providing the INTRNG version of the older Amlogic > interrupt driver it that helps, however I'm probably not finding > time to debug the "lost" clock interrupts issue anytime soon. Almost working code that has an issue or two, especially if those are documented, is much better than having to dump the port because we want to require INTRNG... So yes, if it isn't a huge hassle, can you dig that up? Warner
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170317070453.1462.91784>