Return-Path: <cyrus@holtmann.org>
Message-ID: <4B58C622.2090004@irobot.com>
Date: Thu, 21 Jan 2010 13:24:50 -0800
From: Adam Wozniak <awozniak@irobot.com>
MIME-Version: 1.0
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
CC: linux-wireless <linux-wireless@vger.kernel.org>,
	linux-bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: FYI - new compat-wireless based on 2.6.33-rc4
References: <43e72e891001201213x6a2c203dl7121f2dde6d61fb9@mail.gmail.com> 	<4B5897C8.2080006@irobot.com> <43e72e891001211012y4f4c8721t7eb9e0eea0221820@mail.gmail.com> 	<4B58B432.5050200@irobot.com> <43e72e891001211217t17ffed80i2d5bc6f923b56210@mail.gmail.com>
In-Reply-To: <43e72e891001211217t17ffed80i2d5bc6f923b56210@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Sender: linux-bluetooth-owner@vger.kernel.org
List-ID: <linux-bluetooth.vger.kernel.org>

Luis R. Rodriguez wrote:
> BTW Haukes posted a fix for the compile build against ARM. Try that.
> That patch applies to compat.git but you should be able to mangle it
> to apply to compat-wireless easily too.
>   
That worked, thank you.
> OK so it failed here, you may want to try to debug udev stuff now
> then, what distribution do you have? Where are your udev rules put?
> Where is the original udev rule for firmware for your box?
>
> You can debug udev stuff by using 'udevadm monitor'
>   
I'm using openembedded.  Rules are in /etc/udev/rules.d
It contains a file 50-udev-default.rules with a line:

SUBSYSTEM=="firmware", ACTION=="add", RUN+="firmware.sh"

If I copy & paste and change the SUBSYSTEM to "compat_firmware" things 
seem to load ok.

--Adam