[oe] libertas seems broken since udev 180

[Andreas Müller]

On Sun, Mar 4, 2012 at 10:52 PM, Andreas Müller
<schnitzeltony at googlemail.com> wrote:
> Hi,
>
> this problem I face since a while but didn't find the time to take
> care. Since udev 180 overo's wlan does not work (marvel) and  I get:
>
> at early user space:
> udevd[77]: starting version 181
> Starting POSIX Message Queue File System...
> Started Configuration File System                                      [  OK  ]
> Started Security File System                                           [  OK  ]
> Started FUSE Control File System                                       [  OK  ]
> Started udev Kernel Device Manager                                     [  OK  ]
> Started Lock Directory                                                 [  OK  ]
> Started Runtime Directory                                              [  OK  ]
> Started Media Directory                                                [  OK  ]
> Started Remount API VFS                                                [  OK  ]
> Started Apply Kernel Variables                                         [  OK  ]
> Started Debug File System                                              [  OK  ]
> Started File System Check on Root Device                               [  OK  ]
> Started POSIX Message Queue File System                                [  OK  ]
> Starting Remount Root FS...
> Started udev Coldplug all Devices                                      [  OK  ]
> _regulator_get: spi1.0 supply vcc not found, using dummy regulator
> ads7846 spi1.0: touchscreen, irq 274
> ads7846 spi1.0: no device detected, test read result was 0x00000000
> cfg80211: Calling CRDA to update world regulatory domain
> Started Remount Root FS                                                [  OK  ]
> libertas_sdio: Libertas SDIO driver
> libertas_sdio: Copyright Pierre Ossman
>
> Right after login prompt:
> libertas_sdio mmc1:0001:1: (unregistered net_device):
> ff:ff:ff:ff:ff:ff, fw 0.0.0p0, cap 0x00000000
> libertas_sdio mmc1:0001:1: (unregistered net_device): unidentified
> region code; using the default (USA)
> libertas_sdio mmc1:0001:1: wlan0: Marvell WLAN 802.11 adapter
>
> and cyclic ~every 3s
>
> libertas_sdio mmc1:0001:1: wlan0: command 0x0000 timed out
> libertas_sdio mmc1:0001:1: wlan0: Timeout submitting command 0x0000
>
>
>
> With udev 175 wlan is working properly and I get after boot prompt
> (please ignore 'Network Manager Wait Online'-lines. This is for test
> and it looks same with unmodified networkmanager):
>
> Angstrom v2012.03-core - Kernel 3.0.17+
>
> overo login: cfg80211: Calling CRDA to update world regulatory domain
> Started Network Manager                                                [  OK  ]
> Starting Network Manager Wait Online...
> Failed to start Network Manager Wait Online                            [FAILED]
> See 'systemctl status NetworkManager-wait-online.service' for details.
> Starting Network Time Service...
> smsc911x smsc911x.0: eth0: SMSC911x/921x identified at 0xd0808000, IRQ: 336
> Started Network Time Service                                           [  OK  ]
> libertas_sdio: Libertas SDIO driver
> libertas_sdio: Copyright Pierre Ossman
> Starting Getty on tty1...
> Started Getty on tty1                                                  [  OK  ]
> libertas_sdio mmc1:0001:1: (unregistered net_device):
> 00:19:88:20:72:5c, fw 9.70.3p14, cap 0x00000303
> libertas_sdio mmc1:0001:1: wlan0: Marvell WLAN 802.11 adapter
>
> Any suggestions where to get further information on how to solve? Is
> it possible that the changed sequence causes adapter not yet started
> up when reading MAC / firmware info?
>
> Thanks in advance
>
Sorry for this - but any hints where I can start investigation?

Andreas