From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.4 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_2 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 53C69C43603 for ; Thu, 19 Dec 2019 23:41:43 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 1FACF21655 for ; Thu, 19 Dec 2019 23:41:43 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (1024-bit key) header.d=zv.io header.i=me@zv.io header.b="iuvrt6wT" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727252AbfLSXlm (ORCPT ); Thu, 19 Dec 2019 18:41:42 -0500 Received: from sender4-of-o51.zoho.com ([136.143.188.51]:21170 "EHLO sender4-of-o51.zoho.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726992AbfLSXlk (ORCPT ); Thu, 19 Dec 2019 18:41:40 -0500 X-Greylist: delayed 904 seconds by postgrey-1.27 at vger.kernel.org; Thu, 19 Dec 2019 18:41:40 EST ARC-Seal: i=1; a=rsa-sha256; t=1576797983; cv=none; d=zohomail.com; s=zohoarc; b=Inz6YHSYhC779548yK6cPFAYkj1L6vFEDExMEGkTZFEfNqb+yuiWIFLTSzj0lMF4ksjpiqRGr8D6utPqQyjLGPRg4EqSSOiSnGU0RHVzezzQ1sZbMiIWv0g6zChqPaUmGiKTDWjRJPce6gK08WgReO2UxM0z0NTs/r4SeY+RaDw= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1576797983; h=Content-Type:Content-Transfer-Encoding:Cc:Date:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:To; bh=YRwMCe3+7E5yL5rCzLP2abaTZ1SGUf1q183PkTOBBBU=; b=HeAPxRLUuUDKJnJaSXxWlZaKAsWPT3LweVlf9nBcuReGrhEpUhWwsJXo9xwZmh7E47q/J572kGQCsMVS8wXOGcp9SbW3fnEVkFObY+B4Q1ImlEfsOC/iTOIzkk4v3+BBk8svsvleWa+iDEQ9GYAuVIQdPtd1IloKngISI4DWwws= ARC-Authentication-Results: i=1; mx.zohomail.com; dkim=pass header.i=zv.io; spf=pass smtp.mailfrom=me@zv.io; dmarc=pass header.from= header.from= DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; t=1576797983; s=zoho; d=zv.io; i=me@zv.io; h=Message-ID:Subject:From:To:Cc:Date:In-Reply-To:References:Content-Type:Mime-Version:Content-Transfer-Encoding; bh=YRwMCe3+7E5yL5rCzLP2abaTZ1SGUf1q183PkTOBBBU=; b=iuvrt6wT4Yin5Ozj9gAnzkOUjr2JJrFPULCIr3ZIQdGTRqFP8cq/U+F+i/NhdGGH zjxEsXKWm64CmkgpUa+KjTUNcMXDKeAI7aOdyoHpmLdHW87ZSPjQB6hxMhPrX0ik9Zm mkw8KE905hUFEck5K37QbEAq5VBufSJAynk6iEkY= Received: from lighthouse (cpe-70-114-218-141.austin.res.rr.com [70.114.218.141]) by mx.zohomail.com with SMTPS id 1576797982566959.8883413676132; Thu, 19 Dec 2019 15:26:22 -0800 (PST) Message-ID: <1576797980.31912.110.camel@zv.io> Subject: Re: [PATCH v5 6/8] media: v4l2-core: fix v4l2_buffer handling for time64 ABI From: Zach van Rijn To: Arnd Bergmann , Hans Verkuil Cc: Linux Media Mailing List , Mauro Carvalho Chehab , y2038 Mailman List , "linux-kernel@vger.kernel.org" Date: Thu, 19 Dec 2019 17:26:20 -0600 In-Reply-To: References: <20191126161824.337724-1-arnd@arndb.de> <20191126161824.337724-7-arnd@arndb.de> <09c664fd-87fb-4fac-f104-9afbe7d33aa2@xs4all.nl> <81bb5da1-6b84-8473-4ada-c174f43bbae2@xs4all.nl> <0843718f-1391-3379-38be-41fa9558ea6d@xs4all.nl> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6-1+deb9u2 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-ZohoMailClient: External Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 2019-12-14 at 22:44 +0100, Arnd Bergmann wrote: > On Sat, Dec 14, 2019 at 12:27 PM Hans Verkuil .nl> wrote: > > > > On 12/13/19 4:32 PM, Hans Verkuil wrote: > > > > > ... > > > > > > > > I've heard good things about the prebuilt toolchains > > > > from http://musl.cc/. > > > > These seems to come with a libstdc++, but I have not > > > > tried that myself. > > > > > > I'll see if I can give those a spin, but if I can't get it > > > to work quickly, > > > then I don't plan on spending much time on it. > > > > I managed to build v4l2-ctl/compliance with those > > toolchains, but they seem to be > > still using a 32-bit time_t. > > > > Do I need to get a specific version or do something special? > > My mistake: only musl-1.2.0 and up have 64-bit time_t, but > this isn't released yet. According to https://wiki.musl- > libc.org/roadmap.html, the release was planned for last month, > no idea how long it will take. > > It appears that a snapshot build at > http://more.musl.cc/7.5.0/x86_64-linux-musl/i686-linux-musl- > native.tgz is new enough to have 64-bit time_t (according to > include/bits/alltypes.h), but this is a month old as well, so > it may have known bugs. > > Adding Zach to Cc here, maybe he already has plans for another > build with the latest version. Yes, that's correct. The current (as of 2019-12-19) GCC 9.2.1 offering is based on musl 1.1.24, though the 7.5.0 release is using a more recent git tag only due to timing/availability. Within reason, I'm happy to bump versions with justification. Rebuilding takes about a full day but no time on my end. Rich sent out a message [1] just today suggesting there is still some time64 work to be done, so once he pushes those patches I'll build and release new toolchains for 9.2, 8.3, and 7.5. ZV [1]: https://www.openwall.com/lists/musl/2019/12/19/6