On Sun, Jun 6, 2010 at 2:43 AM, Fabio Rossi <rossi.f@xxxxxxxxx> wrote: > On Sunday 06 June 2010 11:29:54 Luis R. Rodriguez wrote: > >> On Sun, Jun 6, 2010 at 2:28 AM, Luis R. Rodriguez <mcgrof@xxxxxxxxx> wrote: >> > On Fri, Jun 4, 2010 at 1:25 AM, Fabio Rossi <rossi.f@xxxxxxxxx> wrote: >> >> On Wednesday 02 June 2010 23:42:14 Luis R. Rodriguez wrote: >> >>> On Wed, Jun 2, 2010 at 2:29 AM, Fabio Rossi <rossi.f@xxxxxxxxx> wrote: >> >>> > Compiling the kernel without ACPI (CONFIG_ACPI=n) gives the following >> >>> > warning: >> >>> > >> >>> > cfg80211: Calling CRDA to update world regulatory domain >> >>> > cfg80211: World regulatory domain updated: >> >>> > (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp) >> >>> > (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm) >> >>> > ath5k 0000:08:01.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17 >> >>> > ath5k 0000:08:01.0: registered as 'phy0' >> >>> > ath5k phy0: request_irq failed >> >>> > ------------[ cut here ]------------ >> >>> >> >>> Since traces are printed reversed you will have to read my logic from >> >>> bottom to top: >> >>> >> >>> Seems we need to implement the dev_release() op for the class of our >> >>> devices. >> >> >> >> Shall I open a bug in kernel bugzilla to keep trace of this? >> > >> > Nah something else is up... >> > >> > struct class ieee80211_class = { >> > .name = "ieee80211", >> > .owner = THIS_MODULE, >> > .dev_release = wiphy_dev_release, >> > .dev_attrs = ieee80211_dev_attrs, >> > #ifdef CONFIG_HOTPLUG >> > .dev_uevent = wiphy_uevent, >> > #endif >> > .suspend = wiphy_suspend, >> > .resume = wiphy_resume, >> > }; >> >> This is wireless-testing, not compat-wireless right? > > Yes, I'm using the latest wireless-testing.git Then I don't know WTF is going on, some sort of class corruption... anyone else have another idea? Luis -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html