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 Received: from shelob.surriel.com (shelob.surriel.com [96.67.55.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 2FE65C433F5 for ; Mon, 24 Jan 2022 04:49:39 +0000 (UTC) Received: from localhost ([::1] helo=shelob.surriel.com) by shelob.surriel.com with esmtp (Exim 4.94.2) (envelope-from ) id 1nBrI2-0002lQ-LV; Sun, 23 Jan 2022 23:49:14 -0500 Received: from mail-pf1-x42d.google.com ([2607:f8b0:4864:20::42d]) by shelob.surriel.com with esmtps (TLS1.2) tls TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1nBrI0-0002lA-Ec for kernelnewbies@kernelnewbies.org; Sun, 23 Jan 2022 23:49:12 -0500 Received: by mail-pf1-x42d.google.com with SMTP id e28so10276466pfj.5 for ; Sun, 23 Jan 2022 20:49:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to; bh=I6uVXNmhVGinRF8C46iDT7lrM7laF2Put1gFhRmXuug=; b=Vch1xOTP+ZfrYcmih8ZnydTJwgR4KjIm0E3e2VcQmHOrPafjQ8y1UUIebYBraWzBWO dNMopfkdINAX1hnZzL2ubMPrstJ8eV6O5G+EM3PhaXG2m9Ez/lipx7k/xFiLeoI0hp7p tYsj7hTMUE0+EHRPZb+B8UsOs2Vm8cfZyhY5Mi4W3JMtOi8OdNC0Qgjn0zOJqev3VbD8 53V3lv4t/w8SGYrmekWgeDSlhAHKLbExz2rQTFd4VT+KfTyo6CKF5YQLa6mTcMfm1Ctg WVCs28KbRa7Cc/vsQVnhqRs4U5gzTC8Siy84jJmvKJjcsYhFWgleIU+cwHl3LsNRA4pG z38g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to; bh=I6uVXNmhVGinRF8C46iDT7lrM7laF2Put1gFhRmXuug=; b=gFAYzms+HB63kR4eZqOw5GDy0evK0MC/FnZU7bhBzCKlDzmd14lbI67hk2va0hCt+O vxyWnkCc5GnVz8Zkj0drza/ZyV/+Wbtlhpow4t8TNTGm/Gh0n+kFK4vE/f0umvKuKkJd ejZjvJxxtnf/iF3XtlIifzDcLVFn/Ohyp2KFv0bjjP6tc8io6qZNUOA9y0r/y/H1LJIS KeG6YKPDFePZ/hWhcFwqTh5C/bMlPjsVdXdRT/FaSxzx4MtSBvojby/lRoU8KG3XiILA SsIHSsb+4j1ZcGdLPPKakFf4YJdrOjUXCndudlxUJyJRrjTwLuiH9DtTASUzSd/n+3lq TcSg== X-Gm-Message-State: AOAM532sHjisYqmlrYlr971KpFCSwTR+qYNESQJvStEKQDACkSS2MOm+ nX1NXPkzjN7jTWJZ/j/iXn9+lpiJhW6OV0p/ X-Google-Smtp-Source: ABdhPJxsosV/r5BHDFKwPOJnyAVNA1gGKqiGSq9d74n5fBihlNxy863lKrFLsxG8yetsdCFs1SsKhg== X-Received: by 2002:a62:643:0:b0:4c2:7f6e:c37d with SMTP id 64-20020a620643000000b004c27f6ec37dmr3245852pfg.82.1642999750687; Sun, 23 Jan 2022 20:49:10 -0800 (PST) Received: from mail.google.com (122-58-164-114-fibre.sparkbb.co.nz. [122.58.164.114]) by smtp.gmail.com with ESMTPSA id n2sm10650251pga.39.2022.01.23.20.49.08 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 23 Jan 2022 20:49:10 -0800 (PST) Date: Mon, 24 Jan 2022 17:49:06 +1300 From: Paulo Miguel Almeida To: Greg KH Subject: Re: ioctl number change / backwards compatibility doubt Message-ID: <20220124044906.GA8954@mail.google.com> Mail-Followup-To: Paulo Miguel Almeida , Greg KH , kernelnewbies@kernelnewbies.org References: <20220117070125.GA17186@mail.google.com> <20220123075530.GB79751@mail.google.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Cc: kernelnewbies@kernelnewbies.org X-BeenThere: kernelnewbies@kernelnewbies.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Learn about the Linux kernel List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kernelnewbies-bounces@kernelnewbies.org On Sun, Jan 23, 2022 at 12:04:48PM +0100, Greg KH wrote: > On Sun, Jan 23, 2022 at 08:55:30PM +1300, Paulo Miguel Almeida wrote: > > > > I googled a fair bit of time and I'm 99% confident that there isn't such > > userspace/lib tool so I guess this will have done the hard way :( > > If there is no tool, why was the ioctl code written at all? Something > had to call it. > when you told me to look for the userspace tool that interfaced with the ioctl, my interpretation was that you were referring to something akin to what /usr/bin/uname utility is to the syscall uname. Please correct me if I'm wrong. re: what calls the ioctl created by the driver. I'm led to believe that users of this driver make ioctl sycall invocations directly from their application's source code like this: #include "pi433_if.h" /* userspace driver header */ #include /* ioctl */ int file_desc = open("/dev/pi433.0", O_RDWR); struct pi433_tx_cfg tx_cfg = { .frequency = 433000000, .bit_rate = 4800, ... }; int ret_val = ioctl(file_desc, PI433_IOC_WR_TX_CFG, tx_cfg); .... thanks, Paulo Almeida _______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies