Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 1 Dec 2009 06:04:26 +0100
From:      Gonzalo Nemmi <gnemmi@gmail.com>
To:        Weongyo Jeong <weongyo@freebsd.org>, current@freebsd.org
Subject:   Re: Call For Review: Sonics Silicon Backplane(SSB) driver
Message-ID:  <19e9a5dc0911302104l512c3eabw10f4df998dd78241@mail.gmail.com>
In-Reply-To: <20091201024619.GE5432@weongyo>
References:  <20091130034110.GD5432@weongyo> <19e9a5dc0911292122kfce8abbp744ba940cc1c6818@mail.gmail.com> <20091201024619.GE5432@weongyo>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Dec 1, 2009 at 3:46 AM, Weongyo Jeong <weongyo.jeong@gmail.com> wro=
te:
> On Mon, Nov 30, 2009 at 06:22:42AM +0100, Gonzalo Nemmi wrote:
>> On Mon, Nov 30, 2009 at 4:41 AM, Weongyo Jeong <weongyo.jeong@gmail.com>=
 wrote:
>> > Hello,
>> >
>> > I've written a Sonics Silicon Backplane driver which is widely used fo=
r
>> > Broadcom Wireless driver that bwi(4) can use this driver though it has
>> > its own routines in it.
>> >
>> > I don't have any knowledge to write a bus driver like this so I'm not
>> > sure my approach is correct. ?Please review!
>> >
>> > You can download a driver at:
>> >
>> > ? ? ? ?http://people.freebsd.org/~weongyo/ssb_20091129.tar.gz
>> >
>> > regards,
>> > Weongyo Jeong
>>
>> Hi there Weongyo!
>> I=B4d like to know .. will it compile under 8.0-RELEASE or -STABLE?
>
> Yes it should be.

Good to know !
I=B4ll install FreeBSD 8.0 tomorrow and give your driver a go and as
soon as I have something, I=B4ll report back to you :)

>> Should I try your module instead of bwi(4)?
>
> No. =A0ssb driver is a kind of bus driver that it's not a wireless driver
> so can not use. =A0But I'm working on new driver (aka bwn(4)) for
> replacing bwi(4) that it uses v4 firmware (latest firmware) and supports
> more H/Ws. =A0It's almost done that it works to associate with AP and
> pings for RX/TX but not public yet. =A0When it's available let you know
> for testing. :-)

That=B4s even better than I expected because bwi(4) simply doesn=B4t
support my hardware!

So what shoudl I do?
Load it alonside bwi(4)?
Just load it and see what I get on /var/log/messages and dmesg and report b=
ack?

And since you are writing a new driver, can I help to make it work
with ACPI from the get go?

>>
>> And just in case you find it usefull, in ssb_pci.c, {
>> PCI_VENDOR_BROADCOM, 0x4315, "Unknown" }, is actually =A0a 'Broadcom
>> Wireless b/g (BCM4315/BCM22062000)'. I have one .. here you=B4ll find my
>> pciconf -lcvb usinf bwi(4) with parado=B4s firmware:
>> http://pastebin.com/f1f40900c
>>
>> #bwi0@pci0:12:0:0: =A0 =A0 =A0 class=3D0x028000 card=3D0x000b1028
>> chip=3D0x431514e4 rev=3D0x01 hdr=3D0x00
>> # =A0 =A0vendor =A0 =A0 =3D 'Broadcom Corporation'
>> # =A0 =A0device =A0 =A0 =3D 'Broadcom Wireless b/g (BCM4315/BCM22062000)=
'
>> # =A0 =A0class =A0 =A0 =A0=3D network
>> # =A0 =A0cap 01[40] =3D powerspec 3 =A0supports D0 D1 D2 D3 =A0current D=
0
>> # =A0 =A0cap 09[58] =3D vendor (length 120)
>> # =A0 =A0cap 05[e8] =3D MSI supports 1 message, 64 bit
>> # =A0 =A0cap 10[d0] =3D PCI-Express 1 endpoint max data 128(128) link x1=
(x1)
>>
>> bwi0: PHY: type 5, rev 1, ver 6
>> bwi0: RF: manu 0x17f, type 0x2062, rev 2
>>
>> Hope that help :)
>
> Thanks you for informations.

You are welcome !
I=B4ll be sending more info as I get my hands dirty with it :D

Best Regards
Gonzalo Nemmi



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19e9a5dc0911302104l512c3eabw10f4df998dd78241>