SRU: Fix blaze board crash with tiwlan package installed
SRU justification:
Impact: When booting official Maverick pre-installed images on OMAP4
blaze board, with standard wlan packages installed (tiwlan-wl1271*), the
blaze board crashes on wlan driver init.
Fix: The problem is fixed by registering the wlan device exclusively on
pandaboard (the wlan device on blaze board is not compatible).
Testcase: install the standard TI packages on the Maverick OMAP4
pre-installed image running on a blaze board. On next boot, the platform
crashes while loading the wlan driver.
This issue is fixed by the below (and also attached) patch.
From f8c552bce2a258a080536c86fff61e5c50e0e843 Mon Sep 17 00:00:00 2001
From: Sebastien Jan <s-jan@ti.com>
Date: Mon, 18 Oct 2010 18:00:55 +0200
Subject: [PATCH] wlan: register wlan device only on pandaboard
Registering the wlan device on blaze triggers the loading
of user-space wlan drivers for 1271 chip. These user-space
drivers are not compatible with the 1283 chip of the blaze and
cause a kernel crash.
The event is the same whatever the wlan controller, which
prevents managing different wlan drivers in user-space.
This patch registers the wlan device only on pandaboard.
Long term, we would like to generate different events depending
on the wlan controller.
From f8c552bce2a258a080536c86fff61e5c50e0e843 Mon Sep 17 00:00:00 2001
From: Sebastien Jan <s-jan@ti.com>
Date: Mon, 18 Oct 2010 18:00:55 +0200
Subject: [PATCH] wlan: register wlan device only on pandaboard
Registering the wlan device on blaze triggers the loading
of user-space wlan drivers for 1271 chip. These user-space
drivers are not compatible with the 1283 chip of the blaze and
cause a kernel crash.
The event is the same whatever the wlan controller, which
prevents managing different wlan drivers in user-space.
This patch registers the wlan device only on pandaboard.
Long term, we would like to generate different events depending
on the wlan controller.