From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751763AbbCURcY (ORCPT ); Sat, 21 Mar 2015 13:32:24 -0400 Received: from a.ns.miles-group.at ([95.130.255.143]:65275 "EHLO radon.swed.at" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751475AbbCURcW (ORCPT ); Sat, 21 Mar 2015 13:32:22 -0400 Message-ID: <550DAB20.5090504@nod.at> Date: Sat, 21 Mar 2015 18:32:16 +0100 From: Richard Weinberger User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: Sergej Bauer , Arnd Bergmann CC: Paul Bolle , linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org Subject: Re: [PATCH 1/1] Add mkopci driver References: <201503201510.26639.sergej.bauer@gmail.com> <201503211741.11580.sergej.bauer@gmail.com> <201503211641.42508.arnd@arndb.de> <201503212024.46928.sergej.bauer@gmail.com> In-Reply-To: <201503212024.46928.sergej.bauer@gmail.com> Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 21.03.2015 um 18:24 schrieb Sergej Bauer: > Ok, I realized uselessness of merging this driver... Please don't give up that fast! See: http://airlied.livejournal.com/#item80112 > And you brought me to a standstill: >> passthrough. In either case, both the ioctl interface and the procfs interface have no future > But what will be after ioctl? We will not drop the ioctl() system call. But having a character device with random ioctl()s is not really a good driver design. Today we have much more elegant ways to interact between kernel and userspace than ioctl(). For example sysfs or netlink. Thanks, //richard