From: Adam Wozniak <awozniak@irobot.com>
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
Date: Thu, 21 Jan 2010 13:24:50 -0800 [thread overview]
Message-ID: <4B58C622.2090004@irobot.com> (raw)
In-Reply-To: <43e72e891001211217t17ffed80i2d5bc6f923b56210@mail.gmail.com>
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
next prev parent reply other threads:[~2010-01-21 21:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 20:13 FYI - new compat-wireless based on 2.6.33-rc4 Luis R. Rodriguez
2010-01-21 0:21 ` Richard Farina
2010-01-21 18:07 ` Adam Wozniak
2010-01-21 18:12 ` Luis R. Rodriguez
2010-01-21 19:32 ` [PATCH] compat: fix build on arm Hauke Mehrtens
2010-01-21 19:53 ` Luis R. Rodriguez
2010-01-21 20:16 ` Adam Wozniak
2010-01-21 20:08 ` FYI - new compat-wireless based on 2.6.33-rc4 Adam Wozniak
2010-01-21 20:17 ` Luis R. Rodriguez
2010-01-21 21:24 ` Adam Wozniak [this message]
2010-01-21 21:39 ` Adam Wozniak
2010-01-21 22:21 ` Luis R. Rodriguez
2010-01-22 23:46 ` Adam Wozniak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4B58C622.2090004@irobot.com \
--to=awozniak@irobot.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mcgrof@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).