From: "Rafał Miłecki" <zajec5@gmail.com>
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH][WAS:bcmai, axi] bcma: add Broadcom specific AMBA bus driver
Date: Sat, 7 May 2011 18:49:30 +0200 [thread overview]
Message-ID: <BANLkTi=GJs=04H=HpCDy_o1JnhY4+aPgxA@mail.gmail.com> (raw)
In-Reply-To: <4DC57383.3050903@broadcom.com>
2011/5/7 Arend van Spriel <arend@broadcom.com>:
> 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?
--
Rafa?
next prev parent reply other threads:[~2011-05-07 16:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-08 17:41 [PATCH][WAS:bcmai,axi] bcma: add Broadcom specific AMBA bus driver Rafał Miłecki
[not found] ` <BANLkTi=epFN2EZBj9n8pac6h7F4RWmyk+Q@mail.gmail.com>
2011-05-05 23:01 ` [PATCH][WAS:bcmai, axi] " Rafał Miłecki
[not found] ` <201105061605.31625.arnd@arndb.de>
2011-05-06 14:50 ` Rafał Miłecki
2011-05-07 13:34 ` Rafał Miłecki
2011-05-07 13:55 ` [PATCH][WAS:bcmai,axi] " Michael Büsch
[not found] ` <4DC57383.3050903@broadcom.com>
2011-05-07 16:49 ` Rafał Miłecki [this message]
[not found] ` <4DC57B81.6030705@broadcom.com>
2011-05-07 17:20 ` [PATCH][WAS:bcmai, axi] " Rafał Miłecki
[not found] ` <1304790665.13983.10.camel@dev.znau.edu.ua>
2011-05-07 18:05 ` Rafał Miłecki
[not found] ` <1304792795.13983.28.camel@dev.znau.edu.ua>
2011-05-07 18:48 ` Rafał Miłecki
[not found] ` <1304794931.13983.44.camel@dev.znau.edu.ua>
2011-05-07 19:21 ` Rafał Miłecki
[not found] ` <1304796956.13983.65.camel@dev.znau.edu.ua>
2011-05-08 1:44 ` [PATCH][WAS:bcmai,axi] " Michael Büsch
[not found] ` <20110508101609.GF27807@n2100.arm.linux.org.uk>
2011-05-08 10:37 ` [PATCH][WAS:bcmai, axi] " Rafał Miłecki
[not found] ` <201105081706.12449.arnd@arndb.de>
2011-05-08 15:25 ` Rafał Miłecki
[not found] ` <201105081647.22091.arnd@arndb.de>
2011-05-08 14:59 ` Rafał Miłecki
[not found] ` <201105081759.03032.arnd@arndb.de>
2011-05-09 14:33 ` Rafał Miłecki
[not found] ` <20110509153728.GA29762@kroah.com>
2011-05-09 15:48 ` Rafał Miłecki
2011-05-07 16:13 ` Hauke Mehrtens
2011-05-07 16:23 ` Rafał Miłecki
2011-05-07 16:32 ` Hauke Mehrtens
2011-05-07 16:51 ` Rafał Miłecki
2011-05-07 17:24 ` Hauke Mehrtens
2011-05-07 17:35 ` Rafał Miłecki
[not found] ` <20110507224223.GA2537@broadcom.com>
2011-05-07 23:17 ` Hauke Mehrtens
2011-05-08 12:48 ` Hauke Mehrtens
2011-05-08 12:55 ` Rafał Miłecki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTi=GJs=04H=HpCDy_o1JnhY4+aPgxA@mail.gmail.com' \
--to=zajec5@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).