From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264272AbUAOPsD (ORCPT ); Thu, 15 Jan 2004 10:48:03 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264325AbUAOPsD (ORCPT ); Thu, 15 Jan 2004 10:48:03 -0500 Received: from linux-bt.org ([217.160.111.169]:48568 "EHLO mail.holtmann.net") by vger.kernel.org with ESMTP id S264272AbUAOPsB (ORCPT ); Thu, 15 Jan 2004 10:48:01 -0500 Subject: Support of sysfs for Bluetooth subsystem From: Marcel Holtmann To: Linux Kernel Mailing List Content-Type: text/plain Message-Id: <1074181646.2625.59.camel@pegasus> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 Date: Thu, 15 Jan 2004 16:47:27 +0100 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Hi Folks, I wanna add sysfs support to the Bluetooth subsystem, but actually I don't know how and where to start. I don't worry much about the coding itself, because I found some very good documents at LWN. My general concern is how it should look like. Are there any design rules for a subsystem? Regards Marcel