From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752031AbWG1QK7 (ORCPT ); Fri, 28 Jul 2006 12:10:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752028AbWG1QK7 (ORCPT ); Fri, 28 Jul 2006 12:10:59 -0400 Received: from ug-out-1314.google.com ([66.249.92.174]:42361 "EHLO ug-out-1314.google.com") by vger.kernel.org with ESMTP id S1752031AbWG1QK6 (ORCPT ); Fri, 28 Jul 2006 12:10:58 -0400 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=II92KBuvbPUsXcEVBcNj8CHdPx+LEBym6OQZdoPhAEFeI+333KhI+XTUpFSh7/EOldBXo/yW3bBOeIrxnI/cbNi4AGNUULXfLJvAZe0gXrXUJaV3A/o8UK44+cW9aIJkhIXh9MI6SA+t9YPBkIERn6q0MVLWANBz75oZidzqUSs= Message-ID: Date: Fri, 28 Jul 2006 12:10:43 -0400 From: "Dmitry Torokhov" To: "Shem Multinymous" Subject: Re: Generic battery interface Cc: "Vojtech Pavlik" , "Brown, Len" , "Pavel Machek" , "Matthew Garrett" , "kernel list" , linux-thinkpad@linux-thinkpad.org, linux-acpi@vger.kernel.org In-Reply-To: <41840b750607280819t71f55ea7off89aa917421cc33@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <41840b750607271332q5dea0848y2284b30a48f78ea7@mail.gmail.com> <20060727232427.GA4907@suse.cz> <41840b750607271727q7efc0bb2q706a17654004cbbc@mail.gmail.com> <20060728074202.GA4757@suse.cz> <41840b750607280819t71f55ea7off89aa917421cc33@mail.gmail.com> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 7/28/06, Shem Multinymous wrote: > On 7/28/06, Dmitry Torokhov wrote: > > 4) sysfs - all capabilities, IDs, etc for input devices exported there as well. > > Forgive my ignorance, but how do I conncet a sysfs directory with a /dev device? > So far the only way I found is to compare /sys/whatever/dev with the > major+minor of the dev file, which requires brute-force enumeration on > at least one side. > Can't we have udev make a symlink when it creates device node? Kernel can't provide this link since it knows nothing about naming. You could either have a symlink from /sys/ or maybe /dev/enum/ -- Dmitry