Return-Path: Subject: Re: [Bluez-users] bt3c_cs time out - no firmware loaded? From: Marcel Holtmann To: Benjamin Herrenschmidt Cc: Krisztian Mark Szentes , BlueZ Mailing List , Edd Dumbill In-Reply-To: <1053092826.2561.90.camel@gaston> References: <53B03DA73719D5119E6A0008C71E1D78030EA9A3@svr-mail1.corp.home.nl> <200305131047.39294.office@produktivIT.com> <1053083095.26552.49.camel@pegasus> <200305161438.08919.office@produktivIT.com> <1053091452.2561.86.camel@gaston> <1053091839.26550.125.camel@pegasus> <1053091938.2978.88.camel@gaston> <1053092394.26552.132.camel@pegasus> <1053092826.2561.90.camel@gaston> Content-Type: text/plain Message-Id: <1053093446.26552.137.camel@pegasus> Mime-Version: 1.0 Sender: bluez-users-admin@lists.sourceforge.net Errors-To: bluez-users-admin@lists.sourceforge.net List-Help: List-Post: List-Subscribe: , List-Id: List-Unsubscribe: , List-Archive: Date: 16 May 2003 15:57:17 +0200 Hi Ben, > > an ioctl is not possible at that time, because we need the firmware > > loaded before we can initialise the Bluetooth HCI device. And I don't > > want to use the /proc for this kind of stuff. We hopefully will have a > > unified interface for this in 2.5 with request_firmware() call and the > > sysfs. See current discussion on LKML. > > Then a /proc entry or a temporary /dev entry will be the only sane > solution for 2.4 I'm afraid... if you don't see any other solution to work around, this device will be not supported on the PowerPC platform. Regards Marcel ------------------------------------------------------- Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara The only event dedicated to issues related to Linux enterprise solutions www.enterpriselinuxforum.com _______________________________________________ Bluez-users mailing list Bluez-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-users