Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754843Ab1DJQOt (ORCPT ); Sun, 10 Apr 2011 12:14:49 -0400 Received: from mail.academy.zt.ua ([82.207.120.245]:44947 "EHLO mail.academy.zt.ua" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753983Ab1DJQOr (ORCPT ); Sun, 10 Apr 2011 12:14:47 -0400 X-MDAV-Processed: mail.academy.zt.ua, Sun, 10 Apr 2011 19:14:45 +0300 X-Spam-Processed: mail.academy.zt.ua, Sun, 10 Apr 2011 19:14:44 +0300 (not processed: message from trusted or authenticated source) X-Authenticated-Sender: george@academy.zt.ua X-Return-Path: george@znau.edu.ua X-Envelope-From: george@znau.edu.ua Subject: Re: [RFC][PATCH] bcmai: introduce AI driver From: George Kashperko To: Arend van Spriel Cc: "linux-wireless@vger.kernel.org" , "John W. Linville" , Michael B?sch , Larry Finger , George Kashperko , "b43-dev@lists.infradead.org" , "linux-arm-kernel@lists.infradead.org" , Russell King , Arnd Bergmann , linuxdriverproject , "linux-kernel@vger.kernel.org" In-Reply-To: References: <1302033463-1846-1-git-send-email-zajec5@gmail.com> <20110410080159.GB2798@ucw.cz> <20110410082420.GA1460@localhost.ucw.cz> Content-Type: text/plain; charset=UTF-8 Date: Sun, 10 Apr 2011 19:11:57 +0300 Message-Id: <1302451917.14558.13.camel@dev.znau.edu.ua> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-19.el5) Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1654 Lines: 44 > On Sun, 10 Apr 2011 10:30:53 +0200, Rafał Miłecki wrote: > > > 2011/4/10 Pavel Machek : > >>> >> >+config BCMAI_HOST_PCI_POSSIBLE > >>> >> >+ bool > >>> >> >+ depends on BCMAI && PCI = y > >>> >> >+ default y > >>> >> >+ > >>> >> >+config BCMAI_HOST_PCI > >>> >> >+ bool "Support for AI on PCI-host bus" > >>> >> >+ depends on BCMAI_HOST_PCI_POSSIBLE > >>> >> >+ > > Hi Rafał, > > Could use term AMBA AXI instead which gives enough hits on Google to hint > interested people to more in depth information. > > FYI: AXI = Advanced eXtensible Interface > High-speed interconnect for chip cores ( provides higher bursts/transfers > than predecessor AHB = Advanced High-performance Bus (AHB)). > > Gr. AvS Not sure if AXI will be relevant bus name to manage newer Broadcom IP cores. Yes, AMBA AXI is underlying interconnect used for communications, but those communications are made in regard of communication ports (those thingys referenced at Broadcom code as wrappers and which are actually master ports intermediately bound to the backplane itself). Pretty much sure your original bcmb is much more relevant for managing Broadcom hardware extensions over AXI than just axi, especially considering that techniques we use to identify, enumerate and control AXI slave ports are completely Broadcom-specific. Have nice day, George -- 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/