Return-path: Received: from mms3.broadcom.com ([216.31.210.19]:4864 "EHLO MMS3.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751599Ab1EEMdw convert rfc822-to-8bit (ORCPT ); Thu, 5 May 2011 08:33:52 -0400 Message-ID: <4DC2991F.6030703@broadcom.com> (sfid-20110505_143435_977818_A4A168CB) Date: Thu, 5 May 2011 14:33:35 +0200 From: "Arend van Spriel" MIME-Version: 1.0 To: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= cc: "Arnd Bergmann" , "George Kashperko" , "Hauke Mehrtens" , "Russell King" , "linux-kernel@vger.kernel.org" , "linux-wireless@vger.kernel.org" , "linux-arm-kernel@lists.infradead.org" , "Jonas Gorski" , "b43-dev@lists.infradead.org" , "Greg KH" , "Andy Botting" , "Larry Finger" Subject: AXI driver status => previously: Re: Could I (ab)use bus (struct bus_type) for virtual Broadcom bus? References: <201104171938.12834.arnd@arndb.de> <201104191635.40351.arnd@arndb.de> In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Sender: linux-wireless-owner@vger.kernel.org List-ID: On 04/20/2011 09:29 AM, Rafał Miłecki wrote: > I do not register that exceptional devices in my code. Hi Rafał, There has been some radio silence on the subject of the (bcm)axi driver. I was getting a feeling that my concerns were almost all out of the way in latest emails I got from Arnd and/or Jonas. Do you have an update of what plans you have with this module. Gr. AvS