Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754843Ab1BHPRj (ORCPT ); Tue, 8 Feb 2011 10:17:39 -0500 Received: from mail-ey0-f174.google.com ([209.85.215.174]:62902 "EHLO mail-ey0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752645Ab1BHPRh convert rfc822-to-8bit (ORCPT ); Tue, 8 Feb 2011 10:17:37 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=ABgXFwbXTNHx8p4GxL8BXBr82MLjikXvRuk09xt8BiyiXSOpc7WYN/tBJH/R9h68J7 9Ptv8Yw3AViX5tj+3XjVRxXuw9VQby2wGEnPoM+qSWlf7BKlDn+D+0KreNE0Ft0HHc0+ 4wbRRhP9pYCEXmZ1k/McYr01/Ayuvsko8ucyg= MIME-Version: 1.0 In-Reply-To: <20110208145301.GA12930@srcf.ucam.org> References: <20110208145301.GA12930@srcf.ucam.org> Date: Tue, 8 Feb 2011 15:17:35 +0000 Message-ID: Subject: Re: What's part of the ABI (breaking eeepc-wmi) From: Corentin Chary To: Matthew Garrett Cc: platform-driver-x86@vger.kernel.org, linux acpi , LKML , Dmitry Torokhov Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2259 Lines: 56 On Tue, Feb 8, 2011 at 2:53 PM, Matthew Garrett wrote: > On Tue, Feb 08, 2011 at 08:51:27AM +0000, Corentin Chary wrote: > >> A first solution is to rename eeepc-wmi asus-wmi, and create an alias >> to make eeepc-wmi work. Then this driver would handle asus-wmi and >> eeepc-wmi platform drivers (it could also be splitted in 3 >> files/modules, common/notebook/eeepc). >> But then, is it important to keep these strings ? >> - hotplug string ("eeepc-wifi") >> - rfkill names ("eeepc-xxxxx") >> - input strings (.phys and .name) > > I think that, realistically, these changes should be fine but may break > some user code. We don't have a good way of enforcing proper sysfs > usage. Unfortunatly, it would break udev (well.. only the touchpad key, which probably never worked, does it really matters ?) ... http://git.kernel.org/?p=linux/hotplug/udev.git;a=blobdiff;f=extras/keymap/95-keymap.rules;h=9059a8c41e4505f0d8088a90fc0c3a64fe8d5f2d;hp=053838d803d7142dd80fbca361ef65565c6189f2;hb=0d8b6be5f5238360d2d8e220d6da280f842c5358;hpb=e99cc72398d1d5057cc6d1e4c065799f8daaf29e But your probably right for rfkill and hotplug slot name. >> - led names ("eeepc::xxxxxx") > > But I don't think there's any other way of identifying LEDs, so this > probably has to stay. Yep .. but as this led probably never worked before the last patchset, this is probably not the most important string to keep. And users tends to use only the second part of the led name (*::touchpad, *::kbd_backlight, etc...). >> Any thoughts on that ? > > Seems less ugly than the alternatives! Ok, I'll try to do something like that. asus-wmi.ko - generic stuff asus-nb-wmi.ko - used only on notebooks (bweark, asus-nb-wmi is an horrible name :/) eeepc-wmi.ko - used only on eeepcs And you'll be able to register only one asus_wmi_driver at a time, since asus-wmi will have some static stuff in it (hotplug_slot_ops, device_attribute, attribute, attribute_group, dev_pm_ops). -- Corentin Chary http://xf.iksaif.net -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/