Return-Path: Subject: Re: [Bluez-users] bt3c_cs time out - no firmware loaded? From: Benjamin Herrenschmidt To: Marcel Holtmann Cc: Krisztian Mark Szentes , BlueZ Mailing List , Edd Dumbill In-Reply-To: <1053091839.26550.125.camel@pegasus> 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> Content-Type: text/plain Message-Id: <1053091938.2978.88.camel@gaston> Mime-Version: 1.0 Date: 16 May 2003 15:32:19 +0200 Sender: Benjamin Herrenschmidt List-ID: On Fri, 2003-05-16 at 15:30, Marcel Holtmann wrote: > Hi Ben, > > > Hrm... The problem isn't simple. You are just not supposed to tap IOs > > that way from userland, especially since PPC arch doesn't have anything > > like "PIO" instructions. The IO space of your card is actually mapped > > somewhere in physical memory, that "somewhere" not beeing generally > > available to userland. > > > > Can you tell me more about the card ? Is it a 16 bits PCMCIA device or > > is it a cardbus (PCI) one ? Why can't you tap the IOs solely from within > > a kernel driver ? > > this is a 16 Bit PCMCIA card. We need to load the firmware from > userspace, because we can't distribute it within the kernel driver due > the legal issues. At the moment we don't even distribute the firmware > file with our userspace firmware loader program. Can't you do some kind of ioctl or /proc entry to the card's driver to pass it the firmware from userland and have the actual IO code in the kernel ? Ben.