Date: Wed, 3 Mar 2010 11:10:14 +0200 From: Alexandr Rybalko <ray@dlink.ua> To: Weongyo Jeong <weongyo@freebsd.org> Cc: Alex RAY <ray@ddteam.net>, current@freebsd.org, Weongyo Jeong <weongyo.jeong@gmail.com> Subject: Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver Message-ID: <20100303111014.6564ea1e.ray@dlink.ua> In-Reply-To: <20100303082833.GB22865@weongyo> References: <20091223035331.GA1293@weongyo> <4b31cb29.9413f30a.5f4a.ffff8382@mx.google.com> <20100226005115.GP14937@weongyo> <20100227011535.ed3f2486.ray@ddteam.net> <20100228095259.GB3536@weongyo> <20100301103240.3a4aac8a.ray@dlink.ua> <20100303082833.GB22865@weongyo>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 3 Mar 2010 00:28:33 -0800 Weongyo Jeong <weongyo.jeong@gmail.com> wrote: >> On Mon, Mar 01, 2010 at 10:32:40AM +0200, Alexandr Rybalko wrote: >> > On Sun, 28 Feb 2010 01:52:59 -0800 >> > Weongyo Jeong <weongyo.jeong@gmail.com> wrote: >> > >> > Can You test your driver without siba_switchcore, I see the device >> > have mapping for all cores on SSB? >> >> I see what you mean. siba_core.c which depends on PCI code would be >> compiled when it builds on SENTRY5. So it looks currently it needs a >> patch to compile siba bus code without PCI code. I'll try to make a >> patch. I now trying to make bus independent interface, not done yet. When finish, I send to You for review and maybe test. >> >> > > ssb0: <Broadcom BCM4315 802.11b/g Wireless> mem 0xf4000000-0xf4003fff >> > Think thre is 4 cores. >> > When SSB on nexus, we don`t need core switching, maybe on PCI too. >> >> I think this is a difference between siba(4) and siba_bwn currently and >> it's one of TODOs we should solve to merge two codes. >> >> AFAIK approach to access each cores isn't same; it looks siba(4) creates >> devices for each cores so it'd not need to switch cores. But siba_bwn >> doesn't do it like siba(4) so it needs to switch cores because all are >> handled on one device. Look into this line: ssb0: <Broadcom BCM4315 802.11b/g Wireless> mem 0xf4000000-0xf4003fff There we see, device have 0x4000 memory window. Each core required 0x1000. Your code to call required core move PCI window to appropriate 0x1000 block (if core - second, move to 0xf4001000). Maybe we can map full window, and then access to required core without core switching. >> >> regards, >> Weongyo Jeong >> -- Рыбалко Александр Консультант D-Link Украина
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100303111014.6564ea1e.ray>