[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <134619.1482986267@turing-police.cc.vt.edu>
Date: Wed, 28 Dec 2016 23:37:47 -0500
From: Valdis.Kletnieks@...edu
To: Wolfram Sang <wsa@...-dreams.de>
Cc: Pali Rohár <pali.rohar@...il.com>,
Andy Shevchenko <andy.shevchenko@...il.com>,
Mika Westerberg <mika.westerberg@...ux.intel.com>,
Jean Delvare <jdelvare@...e.com>,
Steven Honeyman <stevenhoneyman@...il.com>,
Jochen Eisinger <jochen@...guin-breeder.org>,
Gabriele Mazzotta <gabriele.mzt@...il.com>,
Andy Lutomirski <luto@...nel.org>,
Mario Limonciello <mario_limonciello@...l.com>,
Alex Hung <alex.hung@...onical.com>,
Michał Kępień <kernel@...pniu.pl>,
Takashi Iwai <tiwai@...e.de>, linux-i2c@...r.kernel.org,
linux-kernel@...r.kernel.org, platform-driver-x86@...r.kernel.org
Subject: Re: [PATCH] i2c: i801: Register optional lis3lv02d i2c device on Dell machines
On Wed, 28 Dec 2016 15:03:02 +0100, Wolfram Sang said:
> > I have absolutely no idea how to you want to achieve calling that
> > i2c_new_device() registration
> > without kernel patches.
>
> Documentation/i2c/instantiating-devices lists all supported methods.
> Method 4 is userspace instantiation.
I'd be totally OK with userspace doing it, except for the question "How good
will distros be about shipping it"? I don't have any sense of how good Fedora
and Ubuntu and so on will be about making sure the userspace part is already
done for the user.
Anybody got evidence one way or another?
Content of type "application/pgp-signature" skipped
Powered by blists - more mailing lists