From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1751799AbbCUS3W (ORCPT <rfc822;w@1wt.eu>);
	Sat, 21 Mar 2015 14:29:22 -0400
Received: from mail-la0-f45.google.com ([209.85.215.45]:36100 "EHLO
	mail-la0-f45.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1751524AbbCUS3V (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Sat, 21 Mar 2015 14:29:21 -0400
From: Sergej Bauer <sergej.bauer@gmail.com>
To: Richard Weinberger <richard@nod.at>
Subject: Re: [PATCH 1/1] Add mkopci driver
Date: Sat, 21 Mar 2015 21:29:18 +0300
User-Agent: KMail/1.13.7 (Linux/3.18.9; KDE/4.8.4; x86_64; ; )
Cc: Arnd Bergmann <arnd@arndb.de>, Paul Bolle <pebolle@tiscali.nl>,
        linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
References: <201503201510.26639.sergej.bauer@gmail.com> <201503212024.46928.sergej.bauer@gmail.com> <550DAB20.5090504@nod.at>
In-Reply-To: <550DAB20.5090504@nod.at>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-15"
Content-Transfer-Encoding: 7bit
Message-Id: <201503212129.18159.sergej.bauer@gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Thanks a lot :)

But the driver is really very insignificant.
I was wondering about sysfs before, but consumers will not be very happy to get another revision of userspace tools/library.
So this is their own problems :)

Thanks again and sorry for this uselessness dialogue :)

On Saturday 21 March 2015 20:32:16 Richard Weinberger wrote:
> 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
>