Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753689Ab1EGREW (ORCPT ); Sat, 7 May 2011 13:04:22 -0400 Received: from mms3.broadcom.com ([216.31.210.19]:2528 "EHLO MMS3.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751800Ab1EGREU convert rfc822-to-8bit (ORCPT ); Sat, 7 May 2011 13:04:20 -0400 X-Server-Uuid: B55A25B1-5D7D-41F8-BC53-C57E7AD3C201 Message-ID: <4DC57B81.6030705@broadcom.com> Date: Sat, 7 May 2011 19:04:01 +0200 From: "Arend van Spriel" User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10 MIME-Version: 1.0 To: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= cc: =?UTF-8?B?TWljaGFlbCBCw7xzY2g=?= , "Arnd Bergmann" , "linux-wireless@vger.kernel.org" , "John W. Linville" , "b43-dev@lists.infradead.org" , "Greg KH" , =?UTF-8?B?TWljaGFlbCBCw7xzY2g=?= , "Larry Finger" , "George Kashperko" , "linux-arm-kernel@lists.infradead.org" , "Russell King" , "Andy Botting" , linuxdriverproject , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH][WAS:bcmai,axi] bcma: add Broadcom specific AMBA bus driver References: <1304632783-8781-1-git-send-email-zajec5@gmail.com> <201105061605.31625.arnd@arndb.de> <1304776555.16344.2.camel@maggie> <4DC57383.3050903@broadcom.com> In-Reply-To: X-WSS-ID: 61DBA3D84NS2885821-01-01 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1519 Lines: 29 On 05/07/2011 06:49 PM, Rafał Miłecki wrote: > 2011/5/7 Arend van Spriel: >> On 05/07/2011 03:55 PM, Michael Büsch wrote: >>>> Arnd: did you have a look at defines at all? >>>> >>>> Most of the defines have values in range 0x800 → 0x837. Converting >>>> this to array means loosing 0x800 u16 entries. We can not use 0x800 >>>> offset, because there are also some defined between 0x000 and 0x800: >>>> #define BCMA_CORE_OOB_ROUTER 0x367 /* Out of band */ >>>> #define BCMA_CORE_INVALID 0x700 >> Please be aware that the core identifier itself is not unique (in the >> current list they are). In the scan the BCMA_CORE_OOB_ROUTER will always >> show BCMA_MANUF_ARM (did not look up the proper manufacturer define but you >> get the idea, i hope). > Unfortunately, I don't. Could you explain this? How core identified > can be not unique? Can 0x800 mean ChipCommon but also SuperPCIeX? Yes, if ChipCommon is Broadcom core and SuperPCIeX is ARM core (or some other). The core identifiers are chosen by a chip manufacturer (eg. Broadcom ;-) ). They are not unique by itself so that is why the bcma_device_id consists of manufacturer, id, rev, and class. Providing a device table with ANY_MANUF would be a bad idea. Gr. AvS -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/