Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
Buganini wrote: > Hi, with yesterday's CURRENT my bwn works partially. > > this is my hardware > siba_b...@pci0:4:0:0: class=0x028000 card=0x04b514e4 chip=0x431514e4 > rev=0x01 hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' > class = network > > it works with WPA ap without destroy/re-create wlan0 > , but it's unstable, at the first time it works, it goes forth and > back between "associated" and "no carrier", > the other times it stay associated but network is down. > and this usually followed by system freeze if I `/etc/rc.d/netif restart` > later. > > and it never get associated with a open ap. I'm seeing something similar with my hardware with recent current. It associates but I get massive packet loss to my router over the wireless link: --- 10.0.2.1 ping statistics --- 425 packets transmitted, 195 packets received, 54.1% packet loss round-trip min/avg/max/stddev = 1.460/2.894/86.417/8.110 ms siba_b...@pci0:1:0:0: class=0x028000 card=0x1508103c chip=0x431514e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' class = network cap 01[40] = powerspec 3 supports D0 D1 D2 D3 current D0 cap 09[58] = vendor (length 120) cap 05[e8] = MSI supports 1 message, 64 bit enabled with 1 message cap 10[d0] = PCI-Express 1 endpoint max data 128(128) link x1(x1) Current of May 15 works reliably. I'll try to search for the offending commit. Ian -- Ian Freislich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
>Hi, with yesterday's CURRENT my bwn works partially. > >this is my hardware >siba_bwn0 at pci0:4:0:0:class=0x028000 card=0x04b514e4 chip=0x431514e4 >rev=0x01 hdr=0x00 >vendor = 'Broadcom Corporation' >device = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' >class = network > >it works with WPA ap without destroy/re-create wlan0 >, but it's unstable, at the first time it works, it goes forth and >back between "associated" and "no carrier", >the other times it stay associated but network is down. >and this usually followed by system freeze if I `/etc/rc.d/netif restart` >later. > >and it never get associated with a open ap. This sounds similar to the problems detailed in the recent "wpa supplicant (Was: Re: wpi not working on today's current ..." thread. Have you tried reverting r208623 and r208624? b. ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
Hi, with yesterday's CURRENT my bwn works partially. this is my hardware siba_b...@pci0:4:0:0: class=0x028000 card=0x04b514e4 chip=0x431514e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' class = network it works with WPA ap without destroy/re-create wlan0 , but it's unstable, at the first time it works, it goes forth and back between "associated" and "no carrier", the other times it stay associated but network is down. and this usually followed by system freeze if I `/etc/rc.d/netif restart` later. and it never get associated with a open ap. --Buganini ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Thu, May 20, 2010 at 05:04:51PM +0200, Gustau P??rez wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > En/na Weongyo Jeong ha escrit: > > On Fri, May 07, 2010 at 06:08:05PM +0200, Gustavo Perez Querol wrote: > >>> Hello Gustau, I'm so sorry for belated response that I had no time to > >>> read and work email and wireless stuffs. > >>> > >>> Could you please test this symptom with attached patch? It looks in > >>> CURRENT it missed to initialize a ratectl when it associates with AP. > >>> > >> The patch made the machine to panic. I think it happened when launching > >> the supplicant. In fact, right now it works by putting the RF switch to > >> OFF. As soon as I change it to ON the machine panics. > >> > >> It get a trap 12, with two reasons : page fault and "bufwrite, buffer is > >> not busy?" > >> > >> I'm running 9.0/AMD64 from 1 of May (don't know exact svn revision). > >> > >> Do you want me to test anything else ? > > > > OK. The patch is ready to test. Could you please test it with attached > > patch? > > > > regards, > > Weongyo Jeong > > >I've just updated to FreeBSD 8.1 PRERELEASE and I see the > unsupported rate problem again. I applied the patch for CURRENT and it > works. So I guess the patch was not MFC in the 8.1 branch. It's MFCed today. >However it still works slow (betwenn 200 and 300 kbytes/s). I tried > using a rum dongle with the same AP (which is a 8.0-STABLE system with > an Atheros card) and works great when uploading (2Mb sustained). Umm. I have no clue why this is happened currently. When I found any hints I'll let you know. Thank you. >In my laptop I see now messages like these : > > bwn0: RX decryption attempted (old 0 keyidx 0x1) You could ignore this messages because bwn(4) doesn't support H/W crypto and it looks it's harmless. >If you want me to try anything, let me know. Regards, Weongyo Jeong ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
Weongyo Jeong wrote: OK. The patch is ready to test. Could you please test it with attached patch? your patch got rid of the "bwn0: unsupported rate 0" messages on my Dell Inspiron 1150. But it still gives me repeated: bwn0: RX decryption attempted (old 0 keyidx 0x1) and a few of the following: bwn0: need multicast update callback ts_to_ct(1274664456.824638117) = [2010-05-24 01:27:36] please let me know if there is anything you want me to test. Copyright (c) 1992-2010 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 8.0-STABLE #0: Sun May 16 00:05:17 EDT 2010 t...@zoe.uffner.com:/usr/obj/usr/src/sys/ZOE i386 Preloaded elf kernel "/boot/kernel/kernel" at 0xc0ab6000. Preloaded elf module "/boot/kernel/if_bwn.ko" at 0xc0ab6174. Preloaded elf module "/boot/kernel/siba_bwn.ko" at 0xc0ab6220. Preloaded elf module "/boot/modules/bwn_v4_ucode.ko" at 0xc0ab62d0. Timecounter "i8254" frequency 1193182 Hz quality 0 Calibrating TSC clock ... TSC clock: 2597803596 Hz CPU: Intel(R) Celeron(R) CPU 2.60GHz (2597.80-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0xf29 Family = f Model = 2 Stepping = 9 Features=0xbfebf9ff Features2=0x4400 Instruction TLB: 4 KB, 2 MB or 4 MB pages, fully associative, 128 entries Data TLB: 4 KB or 4 MB pages, fully associative, 64 entries 1st-level data cache: 8 KB, 4-way set associative, sectored cache, 64 byte line size Trace cache: 12K-uops, 8-way set associative 2nd-level cache: 128 KB, 2-way set associative, sectored cache, 64 byte line size real memory = 1073741824 (1024 MB) Physical memory chunk(s): 0x1000 - 0x0009efff, 647168 bytes (158 pages) 0x0010 - 0x003f, 3145728 bytes (768 pages) 0x00c26000 - 0x3ec82fff, 1040568320 bytes (254045 pages) avail memory = 1040355328 (992 MB) bios32: Found BIOS32 Service Directory header at 0xc00ffe80 bios32: Entry = 0xffe90 (c00ffe90) Rev = 0 Len = 1 pcibios: PCI BIOS entry at 0xf+0xcfae pnpbios: Found PnP BIOS data at 0xc00fe2d0 pnpbios: Entry = f:e2f4 Rev = 1.0 pnpbios: Event flag at 4b4 Other BIOS signatures found: x86bios: IVT 0x00-0x0004ff at 0xc000 x86bios: SSEG 0x01-0x01 at 0xc3b74000 x86bios: EBDA 0x09f000-0x09 at 0xc009f000 x86bios: ROM 0x0a-0x0e at 0xc00a ULE: setup cpu 0 wlan: <802.11 Link Layer> snd_unit_init() u=0x00ff8000 [512] d=0x7c00 [32] c=0x03ff [1024] feeder_register: snd_unit=-1 snd_maxautovchans=16 latency=5 feeder_rate_min=1 feeder_rate_max=2016000 feeder_rate_round=25 firmware: 'bwn_v4_ucode' version 0: 0 bytes loaded at 0xc0a8b808 firmware: 'bwn_v4_ucode5' version 0: 22384 bytes loaded at 0xc0a8b808 firmware: 'bwn_v4_ucode11' version 0: 29864 bytes loaded at 0xc0a90f78 firmware: 'bwn_v4_ucode13' version 0: 32232 bytes loaded at 0xc0a98420 firmware: 'bwn_v4_ucode14' version 0: 31384 bytes loaded at 0xc0aa0208 firmware: 'bwn_v4_ucode15' version 0: 30488 bytes loaded at 0xc0aa7ca0 firmware: 'bwn_v4_pcm5' version 0: 1320 bytes loaded at 0xc0aaf3b8 firmware: 'bwn_v4_a0g1initvals5' version 0: 1840 bytes loaded at 0xc0aaf8e0 firmware: 'bwn_v4_a0g0initvals5' version 0: 1840 bytes loaded at 0xc0ab0010 firmware: 'bwn_v4_b0g0initvals5' version 0: 1840 bytes loaded at 0xc0ab0740 firmware: 'bwn_v4_b0g0initvals13' version 0: 2080 bytes loaded at 0xc0ab0e70 firmware: 'bwn_v4_a0g1bsinitvals5' version 0: 158 bytes loaded at 0xc0ab1690 firmware: 'bwn_v4_a0g0bsinitvals5' version 0: 158 bytes loaded at 0xc0ab172e firmware: 'bwn_v4_b0g0bsinitvals5' version 0: 158 bytes loaded at 0xc0ab17cc firmware: 'bwn_v4_lp0initvals13' version 0: 3618 bytes loaded at 0xc0ab186a firmware: 'bwn_v4_lp0initvals14' version 0: 2064 bytes loaded at 0xc0ab268c firmware: 'bwn_v4_lp0initvals15' version 0: 2052 bytes loaded at 0xc0ab2e9c firmware: 'bwn_v4_lp0bsinitvals13' version 0: 158 bytes loaded at 0xc0ab36a0 firmware: 'bwn_v4_lp0bsinitvals14' version 0: 158 bytes loaded at 0xc0ab373e firmware: 'bwn_v4_lp0bsinitvals15' version 0: 158 bytes loaded at 0xc0ab37dc firmware: 'bwn_v4_n0bsinitvals11' version 0: 158 bytes loaded at 0xc0ab387a kbd: new array size 4 kbd1 at kbdmux0 nfslock: pseudo-device mem: Pentium Pro MTRR support enabled null: io: random: ACPI: RSDP 0xfdf00 00014 (v0 DELL ) ACPI: RSDT 0x3fef 00028 (v1 DELLCPi R 27D50605 ASL 0061) ACPI: FACP 0x3fef0400 00074 (v1 DELLCPi R 27D50605 ASL 0061) ACPI: DSDT 0x3fef0c00 02594 (v1 INT430 SYSFexxx 1001 MSFT 010E) ACPI: FACS 0x3feff800 00040 npx0: INT 16 interface acpi0: on motherboard acpi0: [MPSAFE] acpi0: [ITHREAD] acpi0: wakeup code va 0xc3b73000 pa 0x1000 atpic: Programming IRQ9 as level/low pci_open(1):mode 1 addr port (0x0cf8) is 0x8050 pci_open(1a): mode1res=0x8000 (0x8000) pci_cfgcheck: device 0 [class=06] [hdr=80]
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 En/na Weongyo Jeong ha escrit: > On Fri, May 07, 2010 at 06:08:05PM +0200, Gustavo Perez Querol wrote: >>> Hello Gustau, I'm so sorry for belated response that I had no time to >>> read and work email and wireless stuffs. >>> >>> Could you please test this symptom with attached patch? It looks in >>> CURRENT it missed to initialize a ratectl when it associates with AP. >>> >> The patch made the machine to panic. I think it happened when launching >> the supplicant. In fact, right now it works by putting the RF switch to >> OFF. As soon as I change it to ON the machine panics. >> >> It get a trap 12, with two reasons : page fault and "bufwrite, buffer is >> not busy?" >> >> I'm running 9.0/AMD64 from 1 of May (don't know exact svn revision). >> >> Do you want me to test anything else ? > > OK. The patch is ready to test. Could you please test it with attached > patch? > > regards, > Weongyo Jeong > I've just updated to FreeBSD 8.1 PRERELEASE and I see the unsupported rate problem again. I applied the patch for CURRENT and it works. So I guess the patch was not MFC in the 8.1 branch. However it still works slow (betwenn 200 and 300 kbytes/s). I tried using a rum dongle with the same AP (which is a 8.0-STABLE system with an Atheros card) and works great when uploading (2Mb sustained). In my laptop I see now messages like these : bwn0: RX decryption attempted (old 0 keyidx 0x1) If you want me to try anything, let me know. Regards, Gus - -- PGP KEY : http://www-entel.upc.edu/gus/gus.asc -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJL9U+SAAoJEH+VVM1WSYnP2R8QAK2HZsdQ2vlqH37+N6MEmoBz AmWHVUYxqx9QINRGx64diuwgn9USU985nJyxj8VDJOYAiPpzSDnvwPt45djKCt51 MCscu9T74yuvNKlDUwIrsfXvTQsknS3UnynYBILmraXMNJRKwezlnqY5/TSDZEvW 8pNSDJrnt9kBvO4Uy1aLCb1aJ/8+LegsTPLjG2PxVEe+Q+3B1vdw7bKjPvQvJo6o EmNH0Ufx4jrVB8SIDKDRYsHFmOKabRyoMG3EYQr/Jz8ZtoPdVWPxMJbDxe4gwJFL N3FI/LvV51tMwAiT+k+k6rjxXXHV58roVw6r7Uu7LxeJKe0ctwyGImR/atP5t0Ak dVfnihGL3BJhY4sAQBUUem+ESWhdhgz/KYAWDjIbg+czo6cXQCYUTv5UDXoWObaS NrsqNsrBweqXui4QN5GdOa8OY2Bv5WjcZMU2v9C93h4uM5HE0P4Zm0ou3ruLgduS WpDBfoHP223qQvm0QQg/CreZUzbriZtDzeHCGwtBhf8pGlm0jlEMu/LGfWRsllGS uLgvg56yE4H6ybkaGkXy778ICqnztL5VhmMWf/UhMzsOM1I9g2xwuGUrTald+xgq YYY5gSu6Lx2ZwDaG1V2y8T/bHeo3d9Q201tKSJerO8K22JjjV8ySJQh+x9QcivwR CDGo0r6LzEHONgnYQA1q =QJQr -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
Attilio Rao wrote: I have another problem where the bwn is fully recognized and wlan0 is created but the interface doesn't scan at all: # netstat -nil Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll bwn0 2290 00:26:5e:64:be:750 0 0 0 0 0 # ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether 00:26:5e:64:be:75 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid "" channel 1 (2412 MHz 11b) country US authmode OPEN privacy OFF txpower 30 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 1 wme bintval 0 # kldstat Id Refs AddressSize Name 14 0x8010 90b9a8 kernel 21 0x80c22000 28a9abwn_v4_ucode.ko doing "ifconfig wlan0 list scan" ends up immediately without further output. The dmesg is here: http://www.freebsd.org/~attilio/dmesg-bwn0.diff I had a similar problem w/ a 4309. If you haven't solved this already, please check that the radio is actually enabled. some laptops have a button. some have a key sequence. many also have a BIOS setting. mine looked pretty much the same as yours to FreeBSD but just endlessly scanned the channels for a signal until i noticed that the radio was disabled in BIOS. tom ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Mon, May 10, 2010 at 11:41:34PM +0200, Ian FREISLICH wrote: > Weongyo Jeong wrote: > > > Do you want me to test anything else ? > > > > OK. The patch is ready to test. Could you please test it with attached > > patch? > > No panic this time. I also don't get these messages any more: > > May 10 23:25:36 mini kernel: bwn0: unsupported rate 0 > May 10 23:26:13 mini last message repeated 2 times > May 10 23:28:29 mini last message repeated 320 times > May 10 23:28:32 mini last message repeated 61 times > May 10 23:29:42 mini shutdown: reboot by ianf: > > It still doesn't associate with my AP until I destroy the wlan > interface and create it again: Could you please show me your setup and steps you did? It would be helpful if you give me a typescript file using script(1). regards, Weongyo Jeong ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Tue, May 11, 2010 at 10:04:34AM +0200, Ian FREISLICH wrote: > Ian FREISLICH wrote: > > Weongyo Jeong wrote: > > > > Do you want me to test anything else ? > > > > > > OK. The patch is ready to test. Could you please test it with attached > > > patch? > > > > No panic this time. I also don't get these messages any more: > > > > May 10 23:25:36 mini kernel: bwn0: unsupported rate 0 > > May 10 23:26:13 mini last message repeated 2 times > > May 10 23:28:29 mini last message repeated 320 times > > May 10 23:28:32 mini last message repeated 61 times > > May 10 23:29:42 mini shutdown: reboot by ianf: > > > > It still doesn't associate with my AP until I destroy the wlan > > interface and create it again: > > But, after about 12 hours it reduced the rate to 36mbit/s OFDM with > large amounts of time either not transmitting or not recieving - > 86% packet loss over 5 minutes. The rate change to 36 MBit/s is a normal operation depending on the rate control algorithm. But the packet loss could be a problem so I think we need to narrow down this issue why this happens. regards, Weongyo Jeong ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Sat, May 15, 2010 at 05:02:42PM +0200, Gustau P??rez wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > En/na Weongyo Jeong ha escrit: > > On Fri, May 07, 2010 at 06:08:05PM +0200, Gustavo Perez Querol wrote: > >>> Hello Gustau, I'm so sorry for belated response that I had no time to > >>> read and work email and wireless stuffs. > >>> > >>> Could you please test this symptom with attached patch? It looks in > >>> CURRENT it missed to initialize a ratectl when it associates with AP. > >>> > >> The patch made the machine to panic. I think it happened when launching > >> the supplicant. In fact, right now it works by putting the RF switch to > >> OFF. As soon as I change it to ON the machine panics. > >> > >> It get a trap 12, with two reasons : page fault and "bufwrite, buffer is > >> not busy?" > >> > >> I'm running 9.0/AMD64 from 1 of May (don't know exact svn revision). > >> > >> Do you want me to test anything else ? > > > > OK. The patch is ready to test. Could you please test it with attached > > patch? > > > > regards, > > Weongyo Jeong > > > >It worked fine with current. I still haven't tested it a few hours, > let's see if it works. Thanks ! > >However, right now I'm testing zfs with the same laptop (with a > different HDD) and unfortunately I'm seeing the same with STABLE. > Tons of : > > "bwn0: unsupported rate 0" > >I wonder if the patch you sent will work with stable's source code ... Recently the ratectl framwork was MFC to STABLE_8 so it could cause this problem. I'll MFC my patch to STABLE_8 as soon as possible. regards, Weongyo Jeong ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 En/na Weongyo Jeong ha escrit: > On Fri, May 07, 2010 at 06:08:05PM +0200, Gustavo Perez Querol wrote: >>> Hello Gustau, I'm so sorry for belated response that I had no time to >>> read and work email and wireless stuffs. >>> >>> Could you please test this symptom with attached patch? It looks in >>> CURRENT it missed to initialize a ratectl when it associates with AP. >>> >> The patch made the machine to panic. I think it happened when launching >> the supplicant. In fact, right now it works by putting the RF switch to >> OFF. As soon as I change it to ON the machine panics. >> >> It get a trap 12, with two reasons : page fault and "bufwrite, buffer is >> not busy?" >> >> I'm running 9.0/AMD64 from 1 of May (don't know exact svn revision). >> >> Do you want me to test anything else ? > > OK. The patch is ready to test. Could you please test it with attached > patch? > > regards, > Weongyo Jeong > It worked fine with current. I still haven't tested it a few hours, let's see if it works. Thanks ! However, right now I'm testing zfs with the same laptop (with a different HDD) and unfortunately I'm seeing the same with STABLE. Tons of : "bwn0: unsupported rate 0" I wonder if the patch you sent will work with stable's source code ... Regards, Gustau - -- PGP KEY : http://www-entel.upc.edu/gus/gus.asc -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJL7reSAAoJEH+VVM1WSYnPPh0P/1u/Z/RPR/8nworwJw7SDCtb q+2ZI2171LnbMKVYPPsIxeuRMCV6w0M7pzizMJ7hdbW9XRz2PSdcubFa+WutTYZx 3k+AZMjJObM/9gLKveqmTLkz16Pc8WsNOSaxWbDKsxGhF0/CZ6hH7y5iiAdN/UTB eVSRSFVrqXRgtGBrKvMM0LvhGJM+l7txHxjSoHLF3zXAQYmggt7jo+3qUCe3m17J 8Wm2An3l9wPfCmtUbXF/6tJpUmtqqopRZSV7LjmpWuqk8w4JIajt5YTVn9F7w0ZX iB12mTYamWy4ZzFsIg0Tbj/x68XbVDgR5RoNSPsSbqO85C9CP/Nx6R+U9lIye40+ rOX/ApXjM87S7uoDSLjDAc706KZGo56O6tpopazGpoTgtyH5dCoSumRUEucz3zJJ wMIahSK4TyGjO0Nz/dRxqIjPZbxQ2DSbC0KaiCHakWD+aYvNC7i6gC8Hfnx1Z3C2 8XoSiJo/SyfmC0lfzKvz+RzXLifJWRLrY9QbPYvKhrfwHquoAU3hDVS62Slyjrg6 hdGxx3pXK2gr8+vjeKC/k3lVl/h39oQfYEoIhuduur9v2H3ftqNlqWfi3Q4SRL9a 89BEZCvL6F1F/TzrAIZUIr1iLPAbWsQBxyhkqeSqWFpokgLDZ2nsJU8oPsr5ls/Q Wef0yTu4lulwIXYUtBol =wEO7 -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
Ian FREISLICH wrote: > Weongyo Jeong wrote: > > > Do you want me to test anything else ? > > > > OK. The patch is ready to test. Could you please test it with attached > > patch? > > No panic this time. I also don't get these messages any more: > > May 10 23:25:36 mini kernel: bwn0: unsupported rate 0 > May 10 23:26:13 mini last message repeated 2 times > May 10 23:28:29 mini last message repeated 320 times > May 10 23:28:32 mini last message repeated 61 times > May 10 23:29:42 mini shutdown: reboot by ianf: > > It still doesn't associate with my AP until I destroy the wlan > interface and create it again: But, after about 12 hours it reduced the rate to 36mbit/s OFDM with large amounts of time either not transmitting or not recieving - 86% packet loss over 5 minutes. Ian -- Ian Freislich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
Weongyo Jeong wrote: > > Do you want me to test anything else ? > > OK. The patch is ready to test. Could you please test it with attached > patch? No panic this time. I also don't get these messages any more: May 10 23:25:36 mini kernel: bwn0: unsupported rate 0 May 10 23:26:13 mini last message repeated 2 times May 10 23:28:29 mini last message repeated 320 times May 10 23:28:32 mini last message repeated 61 times May 10 23:29:42 mini shutdown: reboot by ianf: It still doesn't associate with my AP until I destroy the wlan interface and create it again: wlan0: Ethernet address: 00:26:5e:57:23:33 bwn0: firmware version (rev 478 patch 104 date 0x8701 time 0x657) bwn0: need multicast update callback bwn0: RX decryption attempted (old 0 keyidx 0x1) bwn0: need multicast update callback bwn0: need multicast update callback and then I get lots of these but no where near the rate of the'unsupported rate' messages: May 10 23:31:39 mini kernel: bwn0: RX decryption attempted (old 0 keyidx 0x1) May 10 23:32:10 mini last message repeated 13 times May 10 23:34:09 mini last message repeated 34 times Ian -- Ian Freislich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Fri, May 07, 2010 at 06:08:05PM +0200, Gustavo Perez Querol wrote:
>
> >
> > Hello Gustau, I'm so sorry for belated response that I had no time to
> > read and work email and wireless stuffs.
> >
> > Could you please test this symptom with attached patch? It looks in
> > CURRENT it missed to initialize a ratectl when it associates with AP.
> >
>
> The patch made the machine to panic. I think it happened when launching
> the supplicant. In fact, right now it works by putting the RF switch to
> OFF. As soon as I change it to ON the machine panics.
>
> It get a trap 12, with two reasons : page fault and "bufwrite, buffer is
> not busy?"
>
> I'm running 9.0/AMD64 from 1 of May (don't know exact svn revision).
>
> Do you want me to test anything else ?
OK. The patch is ready to test. Could you please test it with attached
patch?
regards,
Weongyo Jeong
Index: if_bwn.c
===
--- if_bwn.c (revision 207881)
+++ if_bwn.c (working copy)
@@ -8329,6 +8329,7 @@
static int
bwn_newstate(struct ieee80211vap *vap, enum ieee80211_state nstate, int arg)
{
+ const struct ieee80211_txparam *tp;
struct bwn_vap *bvp = BWN_VAP(vap);
struct ieee80211com *ic= vap->iv_ic;
struct ifnet *ifp = ic->ic_ifp;
@@ -8377,6 +8378,11 @@
bwn_set_pretbtt(mac);
bwn_spu_setdelay(mac, 0);
bwn_set_macaddr(mac);
+
+ /* Initializes ratectl for a node. */
+ tp = &vap->iv_txparms[ieee80211_chan2mode(ic->ic_curchan)];
+ if (tp->ucastrate == IEEE80211_FIXED_RATE_NONE)
+ ieee80211_ratectl_node_init(vap->iv_bss);
}
BWN_UNLOCK(sc);
@@ -8994,7 +9000,7 @@
struct bwn_stats *stats = &mac->mac_stats;
struct ieee80211_node *ni;
struct ieee80211vap *vap;
- int slot;
+ int retrycnt = 0, slot;
BWN_ASSERT_LOCKED(mac->mac_sc);
@@ -9027,7 +9033,7 @@
status->ack ?
IEEE80211_RATECTL_TX_SUCCESS :
IEEE80211_RATECTL_TX_FAILURE,
- NULL, 0);
+ &retrycnt, 0);
break;
}
slot = bwn_dma_nextslot(dr, slot);
@@ -9048,7 +9054,7 @@
status->ack ?
IEEE80211_RATECTL_TX_SUCCESS :
IEEE80211_RATECTL_TX_FAILURE,
- NULL, 0);
+ &retrycnt, 0);
}
bwn_pio_handle_txeof(mac, status);
}
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Thu, May 06, 2010 at 10:27:31PM +0200, Attilio Rao wrote: > 2010/5/6 Weongyo Jeong : > > On Sun, Apr 25, 2010 at 10:42:16PM +0200, Gustau P?rez wrote: > >> -BEGIN PGP SIGNED MESSAGE- > >> Hash: SHA1 > >> > >> > >> >> I've been testing the driver for a few time with AMD64/CURRENT. A > >> >> few time ago I started to see messages like : > >> >> > >> >> bwn0: unsupported rate 0 > >> >> > >> >> I've checked the code and I found it seems to fail when trying to > >> >> check the TX rate at if_bw.c:9561 (in bwn_ieeerate2hwrate > >> >> routine the rate parameter is 0). I checked where bwn_ieeerate2hwrate > >> >> is called, to see how 'rate' is calculated. This is where I got lost :( > >> >> > >> >> My AP is FreeBSD 8.0 box with an atheros card. My hostapd works > >> >> with both WPA2-PSK and WPA2-EAP (although > >> >> I thinks this is not the problem) but with default values for rates > >> >> and friends. I then forced my hostapd to use only a subset of transmit > >> >> rates (with supported_rates and basic_rates) with no luck. > >> >> > >> >> My laptop is a DELL D630 with a BCM4310 UART adapter. > >> >> > >> >> Any need info will be provided and any help will be appreciated. > >> > > >> > First I think we need to know that where rate == 0 comes from. ??Rate > >> > information on TX could be got from the following points: > >> > > >> > ?? ?? tp->mgmtrate > >> > ?? ?? tp->mcastrate > >> > ?? ?? tp->ucastrate > >> > ?? ?? ni->ni_txrate > >> > > >> ?? Added some device_printf to test those values. This is what I got : > >> > >> bwn0: tp->mgmtrate : 2 > >> bwn0: tp->mcastrate : 2 > >> bwn0: tp->ucastrate : 255 > >> bwn0: ni->ni_txrate : 0 > >> > >> ?? ??I didn't have time to follow the code to find out why it has a 0 > >> value. If you need > >> more info let me know. > > > > Hello Gustau, I'm so sorry for belated response that I had no time to > > read and work email and wireless stuffs. > > > > Could you please test this symptom with attached patch? ??It looks in > > CURRENT it missed to initialize a ratectl when it associates with AP. > > Hello, > I have another problem where the bwn is fully recognized and wlan0 is > created but the interface doesn't scan at all: > > # netstat -nil > Name Mtu Network Address Ipkts Ierrs Idrop > Opkts Oerrs Coll > bwn0 2290 00:26:5e:64:be:750 0 0 >0 0 0 > > # ifconfig wlan0 > wlan0: flags=8843 metric 0 mtu 1500 > ether 00:26:5e:64:be:75 > media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) > status: no carrier > ssid "" channel 1 (2412 MHz 11b) > country US authmode OPEN privacy OFF txpower 30 bmiss 7 scanvalid 60 > bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 1 wme > bintval 0 > > # kldstat > Id Refs AddressSize Name > 14 0x8010 90b9a8 kernel > 21 0x80c22000 28a9abwn_v4_ucode.ko > > doing "ifconfig wlan0 list scan" ends up immediately without further output. > The dmesg is here: http://www.freebsd.org/~attilio/dmesg-bwn0.diff > > Sorry for not digging further. It looks the interface isn't scanning. Could you please try to UP the device manually as the below after boot? # ifconfig wlan0 create wlandev bwn0 # ifconfig wlan0 ssid # ifconfig wlan0 up # ifconfig wlan0 list scan regards, Weongyo Jeong ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Fri, May 07, 2010 at 06:08:05PM +0200, Gustavo Perez Querol wrote: > > > > > Hello Gustau, I'm so sorry for belated response that I had no time to > > read and work email and wireless stuffs. > > > > Could you please test this symptom with attached patch? It looks in > > CURRENT it missed to initialize a ratectl when it associates with AP. > > > > The patch made the machine to panic. I think it happened when launching > the supplicant. In fact, right now it works by putting the RF switch to > OFF. As soon as I change it to ON the machine panics. > > It get a trap 12, with two reasons : page fault and "bufwrite, buffer is > not busy?" > > I'm running 9.0/AMD64 from 1 of May (don't know exact svn revision). > > Do you want me to test anything else ? Please give me some time to prepare another patch. My machine encountered another problem which looks related with serial console so I can not test my patch due to kernel panic. regards, Weongyo Jeong ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
> > Hello Gustau, I'm so sorry for belated response that I had no time to > read and work email and wireless stuffs. > > Could you please test this symptom with attached patch? It looks in > CURRENT it missed to initialize a ratectl when it associates with AP. > The patch made the machine to panic. I think it happened when launching the supplicant. In fact, right now it works by putting the RF switch to OFF. As soon as I change it to ON the machine panics. It get a trap 12, with two reasons : page fault and "bufwrite, buffer is not busy?" I'm running 9.0/AMD64 from 1 of May (don't know exact svn revision). Do you want me to test anything else ? Regards, Gustau > regards, > Weongyo Jeong > > ___ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org" ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
2010/5/6 Weongyo Jeong : > On Sun, Apr 25, 2010 at 10:42:16PM +0200, Gustau P?rez wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> >> >> I've been testing the driver for a few time with AMD64/CURRENT. A >> >> few time ago I started to see messages like : >> >> >> >> bwn0: unsupported rate 0 >> >> >> >> I've checked the code and I found it seems to fail when trying to >> >> check the TX rate at if_bw.c:9561 (in bwn_ieeerate2hwrate >> >> routine the rate parameter is 0). I checked where bwn_ieeerate2hwrate >> >> is called, to see how 'rate' is calculated. This is where I got lost :( >> >> >> >> My AP is FreeBSD 8.0 box with an atheros card. My hostapd works >> >> with both WPA2-PSK and WPA2-EAP (although >> >> I thinks this is not the problem) but with default values for rates >> >> and friends. I then forced my hostapd to use only a subset of transmit >> >> rates (with supported_rates and basic_rates) with no luck. >> >> >> >> My laptop is a DELL D630 with a BCM4310 UART adapter. >> >> >> >> Any need info will be provided and any help will be appreciated. >> > >> > First I think we need to know that where rate == 0 comes from. Rate >> > information on TX could be got from the following points: >> > >> > tp->mgmtrate >> > tp->mcastrate >> > tp->ucastrate >> > ni->ni_txrate >> > >> Added some device_printf to test those values. This is what I got : >> >> bwn0: tp->mgmtrate : 2 >> bwn0: tp->mcastrate : 2 >> bwn0: tp->ucastrate : 255 >> bwn0: ni->ni_txrate : 0 >> >> I didn't have time to follow the code to find out why it has a 0 >> value. If you need >> more info let me know. > > Hello Gustau, I'm so sorry for belated response that I had no time to > read and work email and wireless stuffs. > > Could you please test this symptom with attached patch? It looks in > CURRENT it missed to initialize a ratectl when it associates with AP. Hello, I have another problem where the bwn is fully recognized and wlan0 is created but the interface doesn't scan at all: # netstat -nil Name Mtu Network Address Ipkts Ierrs Idrop Opkts Oerrs Coll bwn0 2290 00:26:5e:64:be:750 0 0 0 0 0 # ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether 00:26:5e:64:be:75 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid "" channel 1 (2412 MHz 11b) country US authmode OPEN privacy OFF txpower 30 bmiss 7 scanvalid 60 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 1 wme bintval 0 # kldstat Id Refs AddressSize Name 14 0x8010 90b9a8 kernel 21 0x80c22000 28a9abwn_v4_ucode.ko doing "ifconfig wlan0 list scan" ends up immediately without further output. The dmesg is here: http://www.freebsd.org/~attilio/dmesg-bwn0.diff Sorry for not digging further. Thanks, Attilio -- Peace can only be achieved by understanding - A. Einstein ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Sun, Apr 25, 2010 at 10:42:16PM +0200, Gustau P?rez wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> >> I've been testing the driver for a few time with AMD64/CURRENT. A
> >> few time ago I started to see messages like :
> >>
> >> bwn0: unsupported rate 0
> >>
> >> I've checked the code and I found it seems to fail when trying to
> >> check the TX rate at if_bw.c:9561 (in bwn_ieeerate2hwrate
> >> routine the rate parameter is 0). I checked where bwn_ieeerate2hwrate
> >> is called, to see how 'rate' is calculated. This is where I got lost :(
> >>
> >> My AP is FreeBSD 8.0 box with an atheros card. My hostapd works
> >> with both WPA2-PSK and WPA2-EAP (although
> >> I thinks this is not the problem) but with default values for rates
> >> and friends. I then forced my hostapd to use only a subset of transmit
> >> rates (with supported_rates and basic_rates) with no luck.
> >>
> >> My laptop is a DELL D630 with a BCM4310 UART adapter.
> >>
> >> Any need info will be provided and any help will be appreciated.
> >
> > First I think we need to know that where rate == 0 comes from. Rate
> > information on TX could be got from the following points:
> >
> > tp->mgmtrate
> > tp->mcastrate
> > tp->ucastrate
> > ni->ni_txrate
> >
> Added some device_printf to test those values. This is what I got :
>
> bwn0: tp->mgmtrate : 2
> bwn0: tp->mcastrate : 2
> bwn0: tp->ucastrate : 255
> bwn0: ni->ni_txrate : 0
>
>I didn't have time to follow the code to find out why it has a 0
> value. If you need
> more info let me know.
Hello Gustau, I'm so sorry for belated response that I had no time to
read and work email and wireless stuffs.
Could you please test this symptom with attached patch? It looks in
CURRENT it missed to initialize a ratectl when it associates with AP.
regards,
Weongyo Jeong
Index: if_bwn.c
===
--- if_bwn.c (revision 207481)
+++ if_bwn.c (working copy)
@@ -8329,6 +8329,7 @@
static int
bwn_newstate(struct ieee80211vap *vap, enum ieee80211_state nstate, int arg)
{
+ const struct ieee80211_txparam *tp;
struct bwn_vap *bvp = BWN_VAP(vap);
struct ieee80211com *ic= vap->iv_ic;
struct ifnet *ifp = ic->ic_ifp;
@@ -8377,6 +8378,11 @@
bwn_set_pretbtt(mac);
bwn_spu_setdelay(mac, 0);
bwn_set_macaddr(mac);
+
+ /* Initializes ratectl for a node. */
+ tp = &vap->iv_txparms[ieee80211_chan2mode(ic->ic_curchan)];
+ if (tp->ucastrate == IEEE80211_FIXED_RATE_NONE)
+ ieee80211_ratectl_node_init(vap->iv_bss);
}
BWN_UNLOCK(sc);
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
Weongyo Jeong wrote: > > > The corollery is that it doesn't work first time on reboot. ??I need > > > to either '/etc/rc.d/netif restart' and if that panics the machine, > > > destroy wlan0 and then restart netif. > > > > > > Then wlan0/bwn0 associates correctly with this device. > > If you're a CURRENT user could you please show me the result of `netstat > -ni' after updating latest CURRENT and keeping scanning channels? [mini] /usr/home/ianf $ netstat -niI bwn0 NameMtu Network Address Ipkts Ierrs IdropOpkts Oerrs Coll bwn0 2290 00:26:5e:57:23:33 913 0 0 537 0 0 [mini] /usr/home/ianf # ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether 00:26:5e:57:23:33 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid "" channel 1 (2412 MHz 11g) country US authmode WPA privacy ON deftxkey UNDEF txpower 30 bmiss 7 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme roaming MANUAL [mini] /usr/home/ianf $ ifconfig wlan0 list scan SSID/MESH IDBSSID CHAN RATE S:N INT CAPS quasar 00:30:4f:58:bf:941 54M -108:-95 100 EP WPA WME 00:1f:33:01:76:f4 11 54M -137:-95 100 EPS WPA WME ATH It's not scanning. Now: [mini] /usr/home/ianf # ifconfig wlan0 destroy [mini] /usr/home/ianf # /etc/rc.d/netif restart [mini] /usr/home/ianf # ifconfig wlan0 wlan0: flags=8843 metric 0 mtu 1500 ether 00:26:5e:57:23:33 inet 10.0.2.232 netmask 0xff00 broadcast 10.0.2.255 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated ssid quasar channel 1 (2412 MHz 11g) bssid 00:30:4f:58:bf:94 country US authmode WPA privacy ON deftxkey UNDEF TKIP 2:128-bit txpower 30 bmiss 7 scanvalid 450 bgscan bgscanintvl 300 bgscanidle 250 roam:rssi 7 roam:rate 5 protmode CTS wme roaming MANUAL Ian -- Ian Freislich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 >> I've been testing the driver for a few time with AMD64/CURRENT. A >> few time ago I started to see messages like : >> >> bwn0: unsupported rate 0 >> >> I've checked the code and I found it seems to fail when trying to >> check the TX rate at if_bw.c:9561 (in bwn_ieeerate2hwrate >> routine the rate parameter is 0). I checked where bwn_ieeerate2hwrate >> is called, to see how 'rate' is calculated. This is where I got lost :( >> >> My AP is FreeBSD 8.0 box with an atheros card. My hostapd works >> with both WPA2-PSK and WPA2-EAP (although >> I thinks this is not the problem) but with default values for rates >> and friends. I then forced my hostapd to use only a subset of transmit >> rates (with supported_rates and basic_rates) with no luck. >> >> My laptop is a DELL D630 with a BCM4310 UART adapter. >> >> Any need info will be provided and any help will be appreciated. > > First I think we need to know that where rate == 0 comes from. Rate > information on TX could be got from the following points: > > tp->mgmtrate > tp->mcastrate > tp->ucastrate > ni->ni_txrate > Added some device_printf to test those values. This is what I got : bwn0: tp->mgmtrate : 2 bwn0: tp->mcastrate : 2 bwn0: tp->ucastrate : 255 bwn0: ni->ni_txrate : 0 I didn't have time to follow the code to find out why it has a 0 value. If you need more info let me know. Regards, Gus - -- PGP KEY : http://www-entel.upc.edu/gus/gus.asc -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJL1KknAAoJEH+VVM1WSYnPAPUQAJrpVOOJ4KzUAe6GQHwFnM15 bUiuUeL+5b7sujjLY9j/zuCHQxPDak+/F7eG5AeaJ1bQFkuexG1oDJDLx3oTR06x xhSOKUPZuabrqVeX9xT2d9h8PHa8soEG1GtOPgKzLLfbP8emaimwEnNTlp9G+typ IFxI/LOGzSkpXsqupsXzHTjNiHOxjkijj7e2tEvU8qHh133JebrxBX0jpqSBrZKg +TAC6QnKxh+Mygumsc/5nVQiOPFJEQEEXXdSLXZbr2SqczDeDw98MXxiR4M7TnF/ 20j5fQQE65r6YoPx4X5h2IvaBz2f9aeXlP/t3XIepwuVl3cjL+7B9/CRkV5+T4B1 C5u1Je3tZU0c6fcXOAVOVo7A2c6d+tHXP014CKONPrsTUR2HmLHYNuCQZ+d9LBKx luMcPlqTeRjo+L+VxsM+P+2feegJ7/eV6gweYt3bWsbYzMwfPvjpX2HqgqDtx3DO IT/V8mO76GyCZ21MOdfDQC/1UTHztJVUEGTIXw1HO3aAn3LOsKMPegvF0ZdFyU+5 xv8xkgtbrIBxSA6TzsAu6E+JhksJw9KeEQ4bcaKND7EttnGGelawBB+FeRQiNDYt 6hlSdaX/hHn76tGGx0eJZ/qpdESo8WJvOgaQrt41s1RlfCFnMWmQxDeRY6Dj47LN aB2pONw41gG9OfrPcGi/ =f70p -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Sat, Apr 24, 2010 at 11:42:53PM +0800, Buganini wrote: > No luck here, it's still keeping scanning channels. > > --Buganini > > On Thu, Apr 15, 2010 at 1:34 AM, Ian FREISLICH wrote: > > Buganini wrote: > >> Hi, I got a Lenovo G450 with > >> siba_b...@pci0:4:0:0: class=0x028000 card=0x04b514e4 chip=0x431514e4 > >> rev=0x01 hdr=0x00 > >> ?? ?? vendor ?? ?? = 'Broadcom Corporation' > >> ?? ?? device ?? ?? = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' > >> ?? ?? class ?? ?? ??= network > >> > >> > >> 4315 is not in supported list, but however the driver took the device > >> bwn_v4_lp_ucode.ko was not loaded automatically, so I loaded it > >> manually ifconfig scan seem freeze, I can `ifconfig list scan` later > >> and found access point correctly, but I can't associate with them, it > >> just keep scanning channels. > > > > I found that if I 'ifconfig wlan0 destroy' followed by 'ifconfig > > wlan0 create wlandev bwn0' it works. > > > > /etc/rc.conf: > > --- > > wlans_bwn0="wlan0" > > ifconfig_wlan0="WPA DHCP" > > --- > > > > The corollery is that it doesn't work first time on reboot. ??I need > > to either '/etc/rc.d/netif restart' and if that panics the machine, > > destroy wlan0 and then restart netif. > > > > Then wlan0/bwn0 associates correctly with this device. If you're a CURRENT user could you please show me the result of `netstat -ni' after updating latest CURRENT and keeping scanning channels? In LP-PHY AFAIK there's a DMA Fatal error issue which isn't solved yet. regards, Weongyo Jeong ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Fri, Apr 23, 2010 at 06:44:25PM -0500, James R. Van Artsdalen wrote: > I have a Dell Zino HD (Mac mini clone, with eSATA ports) that uses the > BCM4353 chip (called a Dell 1520 card) > > no...@pci0:2:0:0:class=0x028000 card=0x000e1028 chip=0x435314e4 > rev=0x01 hdr=0x00 > vendor = 'Broadcom Corporation' > class = network > > Should I expect this to work with to work here or try the NDIS driver? BCM4353 uses N PHY so it's not supported by bwn(4). I think NDIS driver is only a way to try currently. regards, Weongyo Jeong ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Sat, Apr 24, 2010 at 12:33:02AM +0200, Gustau P?rez wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > En/na Weongyo Jeong ha escrit: > > On Wed, Mar 03, 2010 at 11:10:14AM +0200, Alexandr Rybalko wrote: > >> On Wed, 3 Mar 2010 00:28:33 -0800 > >> Weongyo Jeong wrote: > > > I've been testing the driver for a few time with AMD64/CURRENT. A > few time ago I started to see messages like : > > bwn0: unsupported rate 0 > > I've checked the code and I found it seems to fail when trying to > check the TX rate at if_bw.c:9561 (in bwn_ieeerate2hwrate > routine the rate parameter is 0). I checked where bwn_ieeerate2hwrate > is called, to see how 'rate' is calculated. This is where I got lost :( > > My AP is FreeBSD 8.0 box with an atheros card. My hostapd works > with both WPA2-PSK and WPA2-EAP (although > I thinks this is not the problem) but with default values for rates > and friends. I then forced my hostapd to use only a subset of transmit > rates (with supported_rates and basic_rates) with no luck. > > My laptop is a DELL D630 with a BCM4310 UART adapter. > > Any need info will be provided and any help will be appreciated. First I think we need to know that where rate == 0 comes from. Rate information on TX could be got from the following points: tp->mgmtrate tp->mcastrate tp->ucastrate ni->ni_txrate Could you please test these variables to narrow this problem down? regards, Weongyo Jeong ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
No luck here, it's still keeping scanning channels. --Buganini On Thu, Apr 15, 2010 at 1:34 AM, Ian FREISLICH wrote: > Buganini wrote: >> Hi, I got a Lenovo G450 with >> siba_b...@pci0:4:0:0: class=0x028000 card=0x04b514e4 chip=0x431514e4 >> rev=0x01 hdr=0x00 >> vendor = 'Broadcom Corporation' >> device = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' >> class = network >> >> >> 4315 is not in supported list, but however the driver took the device >> bwn_v4_lp_ucode.ko was not loaded automatically, so I loaded it >> manually ifconfig scan seem freeze, I can `ifconfig list scan` later >> and found access point correctly, but I can't associate with them, it >> just keep scanning channels. > > I found that if I 'ifconfig wlan0 destroy' followed by 'ifconfig > wlan0 create wlandev bwn0' it works. > > /etc/rc.conf: > --- > wlans_bwn0="wlan0" > ifconfig_wlan0="WPA DHCP" > --- > > The corollery is that it doesn't work first time on reboot. I need > to either '/etc/rc.d/netif restart' and if that panics the machine, > destroy wlan0 and then restart netif. > > Then wlan0/bwn0 associates correctly with this device. > > Ian > > -- > Ian Freislich > ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
I have a Dell Zino HD (Mac mini clone, with eSATA ports) that uses the BCM4353 chip (called a Dell 1520 card) no...@pci0:2:0:0:class=0x028000 card=0x000e1028 chip=0x435314e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' class = network Should I expect this to work with to work here or try the NDIS driver? ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 En/na Weongyo Jeong ha escrit: > On Wed, Mar 03, 2010 at 11:10:14AM +0200, Alexandr Rybalko wrote: >> On Wed, 3 Mar 2010 00:28:33 -0800 >> Weongyo Jeong wrote: > I've been testing the driver for a few time with AMD64/CURRENT. A few time ago I started to see messages like : bwn0: unsupported rate 0 I've checked the code and I found it seems to fail when trying to check the TX rate at if_bw.c:9561 (in bwn_ieeerate2hwrate routine the rate parameter is 0). I checked where bwn_ieeerate2hwrate is called, to see how 'rate' is calculated. This is where I got lost :( My AP is FreeBSD 8.0 box with an atheros card. My hostapd works with both WPA2-PSK and WPA2-EAP (although I thinks this is not the problem) but with default values for rates and friends. I then forced my hostapd to use only a subset of transmit rates (with supported_rates and basic_rates) with no luck. My laptop is a DELL D630 with a BCM4310 UART adapter. Any need info will be provided and any help will be appreciated. Best regards, Gus - -- PGP KEY : http://www-entel.upc.edu/gus/gus.asc -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJL0iAeAAoJEH+VVM1WSYnPH+oQAJXnve4bzhB1pzTr1HhMkXCZ hqveStvnbIxvLV0n8RjH1vK5XFK8Cr1zofGb/btfcnIaW2tBuItVLxpbKP3pEnd0 /FKZZ68ngcNmX8jDyQ1ea6JbQNnJbkM3VIOymwoOhz2rDFCG8JiEGNVMeBDkVdgU 1gitBsrNIWo7WLikmskSbgm9Xb5JsHNGxe6C6L7VGKOdd7ywvokihgctXaEd9o52 jFtnmJYnvFT+q6e+SCRpqYpAiBQSwfbQe/qx+oPsaQGwczskwO5YqzKEonY2U/XR GOKe1fPQzzdqKtpa/cDfwPt7H0GbaDdJaBhj1voSfn3/tguKIgYCVU49/jq8V0/a NkF8VDw2j9eDOgTZP+Uub9PJvp5Tn5kG6SsAOjPxV01U5ouRBzVenDTems8JizLH GD1ldRjnRg9o4XqRgee8wUDqiEiTu2n7vwyttp2PtOUrrB4Ed11pNcYGkEyiPuLG K3UhLPlN1lh5lSlNofeD6zq4fDlaXmfxjCBvQRADk2HSaLnCp4hqoqydKvGvG5mg nexYi+XQY17u5PsPKNPKHM/aS5dmsBgrOgMCMXNuC/65YGxS4lca4m3QSYYES+qU dfhrhQ2pD24/ysvYwekd3nVbMXBjtU97a07r2aJPiidQYZ0erTtG7dEHrGFwGXmm XEwHkkANz3NMl/skGJc5 =7IfN -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
Buganini wrote: > Hi, I got a Lenovo G450 with > siba_b...@pci0:4:0:0: class=0x028000 card=0x04b514e4 chip=0x431514e4 > rev=0x01 hdr=0x00 > vendor = 'Broadcom Corporation' > device = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' > class = network > > > 4315 is not in supported list, but however the driver took the device > bwn_v4_lp_ucode.ko was not loaded automatically, so I loaded it > manually ifconfig scan seem freeze, I can `ifconfig list scan` later > and found access point correctly, but I can't associate with them, it > just keep scanning channels. I found that if I 'ifconfig wlan0 destroy' followed by 'ifconfig wlan0 create wlandev bwn0' it works. /etc/rc.conf: --- wlans_bwn0="wlan0" ifconfig_wlan0="WPA DHCP" --- The corollery is that it doesn't work first time on reboot. I need to either '/etc/rc.d/netif restart' and if that panics the machine, destroy wlan0 and then restart netif. Then wlan0/bwn0 associates correctly with this device. Ian -- Ian Freislich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
Hi siba_b...@pci0:1:0:0: class=0x028000 card=0x1508103c chip=0x431514e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' class = network With a fresh -CURRENT and: 72 0xcb104000 9000 siba_bwn.ko 101 0xcb118000 2c000bwn_v4_lp_ucode.ko 112 0xcb144000 3000 firmware.ko 131 0xcb2e 32000if_bwn.ko This NIC works great. You made my day. It even obeys the wireless on-off switch on the front of my netbook. Ian -- Ian Freislich ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
Hi, I got a Lenovo G450 with siba_b...@pci0:4:0:0: class=0x028000 card=0x04b514e4 chip=0x431514e4 rev=0x01 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Broadcom Wireless b/g (BCM4315/BCM22062000)' class = network 4315 is not in supported list, but however the driver took the device bwn_v4_lp_ucode.ko was not loaded automatically, so I loaded it manually ifconfig scan seem freeze, I can `ifconfig list scan` later and found access point correctly, but I can't associate with them, it just keep scanning channels. My uname -ai: FreeBSD Zeta.twbbs.org 9.0-CURRENT FreeBSD 9.0-CURRENT #1: Fri Mar 26 03:42:08 CST 2010 r...@zeta.twbbs.org:/usr/obj/usr/src/sys/ZETA i386 Zeta Is this bug or just lack of support? --Buganini ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Mon, Mar 15, 2010 at 12:43:57AM +0200, Alex RAY wrote: > On Sat, 13 Mar 2010 16:55:58 -0800 > Weongyo Jeong wrote: > > > On Sat, Mar 13, 2010 at 11:12:05PM +0200, Alex RAY wrote: > > > On Fri, 12 Mar 2010 15:13:34 -0800 > > > Weongyo Jeong wrote: > > > > > > > > > > > I thought that your opinion was right and if mem is > > > > 0xf400-0xf4003fff (16 Kb) I thought the device has 4 cores. However > > > > it looks this was wrong according to the below document: > > > > > > > > http://voodoowarez.com/bcm5365p.pdf > > > > > > > > Please see Section 3: PCI Core, PCI Bus (Page 34) that it indicates that > > > > 16Kb, maybe 8 Kb in the old devices is core register region. > > > > > > > > "Accesses to the lower half of the core register region are translated > > > >into system backplane accesses using the PCIBAR0Window register" > > > > "Accesses to offsets 0x1000 to 0x17FF of this region initiate a direct > > > >access to the external SPROM" > > > > > > > > If we just access memory using offset + core and bus_space_read_x > > > > interfaces it would actually not access core register region. > > > > > > > > So without solving this problem it looks it could not remove coreswitch > > > > routines. > > > > > > > > regards, > > > > Weongyo Jeong > > > > > > > > > > Hi, > > > > > > this document about SoC BCM5365P, not about PCI device with PCI to SSB > > > bridge. > > > > Yes it's about SoC BCM5365P but I think the basic concept of Silicon > > Backplane would be same at a PCI device with PCI to SSB bridge. > > > > > I know in SoC`s like BSM5365 (I test it in BCM5354 and BCM5836) core > > > switching is not required. > > > > > > BCM5354 - > > > http://lists.freebsd.org/pipermail/freebsd-mips/2009-June/000421.html > > > BCM5836 - > > > http://lists.freebsd.org/pipermail/freebsd-mips/2010-February/000635.html > > > > The above URLs you mentioned indicates that > > > > siba0: at mem 0x1800-0x18006fff on > > nexus0 > > siba_cc0: at mem 0x1800-0x18000fff irq 0 on siba0 > > bfe0: at mem 0x18001000-0x18001fff irq 1 on > > siba0 > > siba_mips0: at mem 0x18002000-0x18002fff on siba0 > > ohci0: at mem 0x18003000-0x18003fff irq 4 > > on siba0 > > > > siba0 used memory region at starting 0x1800 that I think this is a > > reason why it doesn't require core switching and each cores have their > > own memory region at starting 0x1800. > > > > But in a case of PCI device with PCI to SSB bridge, it normally used > > 0xf400, 0xfe20 or other address which reserved by parent PCI > > bridge. > > > > > With PCI device, when device report memory window > > > 0xf400-0xf4003fff, why we can`t use full window? > > > > Because I'm not a Silicon Backplane expert I could not answer this > > question. But I'd like to make sure that memory window at 0xf400 > > (size 16 Kbytes) comes from PCI BAR0 when pci(4) attached device. > > Moreover I believe size of memory window also comes from PCI BAR0 size > > testing of pci(4). > > > > Of course I think we can try to remap full memory window after > > calculating numbers of core but it looks meaning would be little bit > > different. > > > > > May be You can test your code without core switching? > > > > I tried to remove core switching code in siba_bwn bridge but after > > moment I got stuck to go forward. For example, > > > > I have 1 device which attached with bwn(4) and it has 4 cores: > > > > 0x1800-0x18000fff ChipCommon > > 0x18001000-0x18001fff EMAC > > 0x18002000-0x18002fff PCI > > 0x18003000-0x18003fff PCMCIA > > > > When it attached at siba_bwn it shows its memory region at 0xfe2fe000 - > > 0xfe2f (8 Kbytes). Initial PCI BAR0 value was 0x18002000. > > Yes, You're right. I found another way. > We can use SBtoPCITranslation2 (Offset 0x108) register, in that way we > can access to SSB without coreswitching. > (Page 42) > > Initial access for copy SPROM and preconfigure make via BAR0, then > setup SBtoPCITranslation2 and access to SSB direct. According to the specification, as you mentioned SBtoPCITranslation2 has a field UpperAddress but on field 31:30. It looks 2 bit fields are too limited to use so don't know how to implement it you mentioned. Could you please elaborate or show me details? regards, Weongyo Jeong ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Sat, 13 Mar 2010 16:55:58 -0800 Weongyo Jeong wrote: > On Sat, Mar 13, 2010 at 11:12:05PM +0200, Alex RAY wrote: > > On Fri, 12 Mar 2010 15:13:34 -0800 > > Weongyo Jeong wrote: > > > > > > > > I thought that your opinion was right and if mem is > > > 0xf400-0xf4003fff (16 Kb) I thought the device has 4 cores. However > > > it looks this was wrong according to the below document: > > > > > > http://voodoowarez.com/bcm5365p.pdf > > > > > > Please see Section 3: PCI Core, PCI Bus (Page 34) that it indicates that > > > 16Kb, maybe 8 Kb in the old devices is core register region. > > > > > > "Accesses to the lower half of the core register region are translated > > >into system backplane accesses using the PCIBAR0Window register" > > > "Accesses to offsets 0x1000 to 0x17FF of this region initiate a direct > > >access to the external SPROM" > > > > > > If we just access memory using offset + core and bus_space_read_x > > > interfaces it would actually not access core register region. > > > > > > So without solving this problem it looks it could not remove coreswitch > > > routines. > > > > > > regards, > > > Weongyo Jeong > > > > > > > Hi, > > > > this document about SoC BCM5365P, not about PCI device with PCI to SSB > > bridge. > > Yes it's about SoC BCM5365P but I think the basic concept of Silicon > Backplane would be same at a PCI device with PCI to SSB bridge. > > > I know in SoC`s like BSM5365 (I test it in BCM5354 and BCM5836) core > > switching is not required. > > > > BCM5354 - > > http://lists.freebsd.org/pipermail/freebsd-mips/2009-June/000421.html > > BCM5836 - > > http://lists.freebsd.org/pipermail/freebsd-mips/2010-February/000635.html > > The above URLs you mentioned indicates that > > siba0: at mem 0x1800-0x18006fff on > nexus0 > siba_cc0: at mem 0x1800-0x18000fff irq 0 on siba0 > bfe0: at mem 0x18001000-0x18001fff irq 1 on > siba0 > siba_mips0: at mem 0x18002000-0x18002fff on siba0 > ohci0: at mem 0x18003000-0x18003fff irq 4 on > siba0 > > siba0 used memory region at starting 0x1800 that I think this is a > reason why it doesn't require core switching and each cores have their > own memory region at starting 0x1800. > > But in a case of PCI device with PCI to SSB bridge, it normally used > 0xf400, 0xfe20 or other address which reserved by parent PCI > bridge. > > > With PCI device, when device report memory window > > 0xf400-0xf4003fff, why we can`t use full window? > > Because I'm not a Silicon Backplane expert I could not answer this > question. But I'd like to make sure that memory window at 0xf400 > (size 16 Kbytes) comes from PCI BAR0 when pci(4) attached device. > Moreover I believe size of memory window also comes from PCI BAR0 size > testing of pci(4). > > Of course I think we can try to remap full memory window after > calculating numbers of core but it looks meaning would be little bit > different. > > > May be You can test your code without core switching? > > I tried to remove core switching code in siba_bwn bridge but after > moment I got stuck to go forward. For example, > > I have 1 device which attached with bwn(4) and it has 4 cores: > > 0x1800-0x18000fff ChipCommon > 0x18001000-0x18001fff EMAC > 0x18002000-0x18002fff PCI > 0x18003000-0x18003fff PCMCIA > > When it attached at siba_bwn it shows its memory region at 0xfe2fe000 - > 0xfe2f (8 Kbytes). Initial PCI BAR0 value was 0x18002000. Yes, You're right. I found another way. We can use SBtoPCITranslation2 (Offset 0x108) register, in that way we can access to SSB without coreswitching. (Page 42) Initial access for copy SPROM and preconfigure make via BAR0, then setup SBtoPCITranslation2 and access to SSB direct. > > If your opinion is right the memory region for full window should be > 0xfe2fe000 - 0xfe301fff (16 Kb for 4 core, each core consumes 0x1000 > size) > > Even if I tried to remap memory region from 0xfe2fe000 to 0xfe301fff and > setting PCI BAR0 to 0x1800, another problem is occurred for reading > SPROM data. To access external SPROM it could be possible to access > bus_space_read_2(bt, bh, 0x1000 ~ 0x17ff) at ChipCommon core. But > accessing register in a core could not over 0xfff because maximum size > of a core limited within 0x1000. > > That means internally in Silicon Backplane it has a special meaning if > it try to access over 0x1000 or 0x2000 which mentioned a quote at > Section 3: PCI Core, PCI Bus (Page 34). > > I guess you're thinking that we could access EMAC core using > bus_space_read_2(bt, bh, 0x1000 ~ 0x1fff) after setting full memory > window. But it looks it's not possible. > > regards, > Weongyo Jeong -- Alex RAY ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Sat, Mar 13, 2010 at 11:12:05PM +0200, Alex RAY wrote: > On Fri, 12 Mar 2010 15:13:34 -0800 > Weongyo Jeong wrote: > > > > > I thought that your opinion was right and if mem is > > 0xf400-0xf4003fff (16 Kb) I thought the device has 4 cores. However > > it looks this was wrong according to the below document: > > > > http://voodoowarez.com/bcm5365p.pdf > > > > Please see Section 3: PCI Core, PCI Bus (Page 34) that it indicates that > > 16Kb, maybe 8 Kb in the old devices is core register region. > > > > "Accesses to the lower half of the core register region are translated > >into system backplane accesses using the PCIBAR0Window register" > > "Accesses to offsets 0x1000 to 0x17FF of this region initiate a direct > >access to the external SPROM" > > > > If we just access memory using offset + core and bus_space_read_x > > interfaces it would actually not access core register region. > > > > So without solving this problem it looks it could not remove coreswitch > > routines. > > > > regards, > > Weongyo Jeong > > > > Hi, > > this document about SoC BCM5365P, not about PCI device with PCI to SSB > bridge. Yes it's about SoC BCM5365P but I think the basic concept of Silicon Backplane would be same at a PCI device with PCI to SSB bridge. > I know in SoC`s like BSM5365 (I test it in BCM5354 and BCM5836) core > switching is not required. > > BCM5354 - > http://lists.freebsd.org/pipermail/freebsd-mips/2009-June/000421.html > BCM5836 - > http://lists.freebsd.org/pipermail/freebsd-mips/2010-February/000635.html The above URLs you mentioned indicates that siba0: at mem 0x1800-0x18006fff on nexus0 siba_cc0: at mem 0x1800-0x18000fff irq 0 on siba0 bfe0: at mem 0x18001000-0x18001fff irq 1 on siba0 siba_mips0: at mem 0x18002000-0x18002fff on siba0 ohci0: at mem 0x18003000-0x18003fff irq 4 on siba0 siba0 used memory region at starting 0x1800 that I think this is a reason why it doesn't require core switching and each cores have their own memory region at starting 0x1800. But in a case of PCI device with PCI to SSB bridge, it normally used 0xf400, 0xfe20 or other address which reserved by parent PCI bridge. > With PCI device, when device report memory window > 0xf400-0xf4003fff, why we can`t use full window? Because I'm not a Silicon Backplane expert I could not answer this question. But I'd like to make sure that memory window at 0xf400 (size 16 Kbytes) comes from PCI BAR0 when pci(4) attached device. Moreover I believe size of memory window also comes from PCI BAR0 size testing of pci(4). Of course I think we can try to remap full memory window after calculating numbers of core but it looks meaning would be little bit different. > May be You can test your code without core switching? I tried to remove core switching code in siba_bwn bridge but after moment I got stuck to go forward. For example, I have 1 device which attached with bwn(4) and it has 4 cores: 0x1800-0x18000fff ChipCommon 0x18001000-0x18001fff EMAC 0x18002000-0x18002fff PCI 0x18003000-0x18003fff PCMCIA When it attached at siba_bwn it shows its memory region at 0xfe2fe000 - 0xfe2f (8 Kbytes). Initial PCI BAR0 value was 0x18002000. If your opinion is right the memory region for full window should be 0xfe2fe000 - 0xfe301fff (16 Kb for 4 core, each core consumes 0x1000 size) Even if I tried to remap memory region from 0xfe2fe000 to 0xfe301fff and setting PCI BAR0 to 0x1800, another problem is occurred for reading SPROM data. To access external SPROM it could be possible to access bus_space_read_2(bt, bh, 0x1000 ~ 0x17ff) at ChipCommon core. But accessing register in a core could not over 0xfff because maximum size of a core limited within 0x1000. That means internally in Silicon Backplane it has a special meaning if it try to access over 0x1000 or 0x2000 which mentioned a quote at Section 3: PCI Core, PCI Bus (Page 34). I guess you're thinking that we could access EMAC core using bus_space_read_2(bt, bh, 0x1000 ~ 0x1fff) after setting full memory window. But it looks it's not possible. regards, Weongyo Jeong ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Fri, 12 Mar 2010 15:13:34 -0800 Weongyo Jeong wrote: > > I thought that your opinion was right and if mem is > 0xf400-0xf4003fff (16 Kb) I thought the device has 4 cores. However > it looks this was wrong according to the below document: > > http://voodoowarez.com/bcm5365p.pdf > > Please see Section 3: PCI Core, PCI Bus (Page 34) that it indicates that > 16Kb, maybe 8 Kb in the old devices is core register region. > > "Accesses to the lower half of the core register region are translated >into system backplane accesses using the PCIBAR0Window register" > "Accesses to offsets 0x1000 to 0x17FF of this region initiate a direct >access to the external SPROM" > > If we just access memory using offset + core and bus_space_read_x > interfaces it would actually not access core register region. > > So without solving this problem it looks it could not remove coreswitch > routines. > > regards, > Weongyo Jeong > Hi, this document about SoC BCM5365P, not about PCI device with PCI to SSB bridge. I know in SoC`s like BSM5365 (I test it in BCM5354 and BCM5836) core switching is not required. BCM5354 - http://lists.freebsd.org/pipermail/freebsd-mips/2009-June/000421.html BCM5836 - http://lists.freebsd.org/pipermail/freebsd-mips/2010-February/000635.html With PCI device, when device report memory window 0xf400-0xf4003fff, why we can`t use full window? May be You can test your code without core switching? -- Alex RAY ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Wed, Mar 03, 2010 at 11:10:14AM +0200, Alexandr Rybalko wrote: > On Wed, 3 Mar 2010 00:28:33 -0800 > Weongyo Jeong 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 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. It's my pleasure to test your patch. > > >> > >> > > ssb0: mem 0xf400-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: mem 0xf400-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. I thought that your opinion was right and if mem is 0xf400-0xf4003fff (16 Kb) I thought the device has 4 cores. However it looks this was wrong according to the below document: http://voodoowarez.com/bcm5365p.pdf Please see Section 3: PCI Core, PCI Bus (Page 34) that it indicates that 16Kb, maybe 8 Kb in the old devices is core register region. "Accesses to the lower half of the core register region are translated into system backplane accesses using the PCIBAR0Window register" "Accesses to offsets 0x1000 to 0x17FF of this region initiate a direct access to the external SPROM" If we just access memory using offset + core and bus_space_read_x interfaces it would actually not access core register region. So without solving this problem it looks it could not remove coreswitch routines. regards, Weongyo Jeong ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
In message: <261c29701003040928h7aa70b3fm37611f974e0b9...@mail.gmail.com> Miki writes: : Rising FIRMWARE_MAX from 30 to 60 did the trick ! thanks ! : Are there any reasons to have such a "low" default value ? I thought I'd committed this change already :) Warner ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Thursday 04 March 2010 12:28:59 pm Miki wrote: > 2010/3/3 John Baldwin : > > On Tuesday 02 March 2010 2:08:55 pm Miki wrote: > >> 2010/3/1 Weongyo Jeong : > >> > On Sun, Feb 28, 2010 at 08:45:32PM +0100, Miki wrote: > >> >> Hi, > >> >> > >> >> Thanks for the work ! > >> >> > >> >> I have some problems here when I try to create a wlan interface : > >> >> bwn_v4_ucode5: could not load firmware image, error 2 > >> >> bwn0: the fw file(bwn_v4_ucode5) not found > >> > > >> > Did you try to UP the interface withload loading bwn_v4_ucode.ko? If > >> > yes currently bwn(4) doesn't automatically load firmware module so you > >> > need to do it by hand. > >> > > >> > # kldload bwn_v4_ucode > >> > >> OK I have loaded bwn_v4_ucode before if_bwn and it works, > >> my bad, I should have read the man page more carefully. > >> > >> > > >> > The patch for this is ready to commit and it'll be happened soon. > >> > > >> >> I have installed bwn-firmware-kmod from ports but the only files I have > >> >> in > >> >> /boot/modules are bwn_v4_lp_ucode.ko and bwn_v4_ucode.ko. So I tried to > >> >> copy bwn_v4_ucode to bwn_v4_ucode5 and it seems to work : wlan0 is > >> >> created, I can associate to an open Access Point and obtain a DHCP > >> >> lease. > >> >> But if I try to do some network IO (browsing the web) the interface hang > >> >> (I cannot obtain a lease anymore). > >> > > >> > I have a exact same device like you have but I didn't encounter this > >> > issue. > >> > > >> > Are there any messages from bwn(4) when you the interface becomes hang? > >> > One more question, after the interface hang, does the system be hang > >> > also? > >> > >> I have no messages in the log (appart bwn0: need multicast update > >> callback). > >> In fact it's not a hang, it happens only with the AP that permits me > >> to have a web > >> access. I have another AP (sitting next to me) and I don't have the > >> same behavior : > >> I can have and renew my dhcp lease multiple times and configure the AP > >> with its > >> web interface. With the "buggy" AP I can have a dhcp lease only once and > >> nothing > >> more. If I destroy and recreate the wlan interface the same thing happens. > >> I have no such a problem with if_bwi and this AP. > >> > >> > > >> > One thing you can do is that trying the device with PIO mode not DMA > >> > mode using the following tunable variable: > >> > > >> > hw.bwn.usedma > >> > > >> > Its default value is 1 to enable DMA operation so if you set it 0, PIO > >> > mode would be used and could see the message like below: > >> > > >> > bwn0: PIO > >> > > >> > Could you please test with it? > >> > > >> > >> Setting hw.bwn.usedma=0 in loader.conf make no differences > >> > >> by the way, I need to switch from if_bwn to if_bwi to make some test > >> and post the results here, but I have this error message : > >> firmware_register: cannot register image bwi_v3_b0g0initvals5, firmware > >> table full! > >> is this normal ? > > > > Yes, both bwi and bwn use a lot of individual firmware images, so loading > > both of them probably fills up the static array of firmware table entries. > > I think there is a constant in subr_firwmare.c you can increase to make the > > table bigger. > > > > -- > > John Baldwin > > > > Rising FIRMWARE_MAX from 30 to 60 did the trick ! thanks ! > Are there any reasons to have such a "low" default value ? I think the number was chosen somewhat randomly. I do think 30 firmware images is probably more than enough for common cases. One option would be to malloc the table at boot time and make the size configurable via a loader tunable. Otherwise we could just make it dynamic and use a linked-list of some sort instead of the current array. -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
2010/3/3 John Baldwin : > On Tuesday 02 March 2010 2:08:55 pm Miki wrote: >> 2010/3/1 Weongyo Jeong : >> > On Sun, Feb 28, 2010 at 08:45:32PM +0100, Miki wrote: >> >> Hi, >> >> >> >> Thanks for the work ! >> >> >> >> I have some problems here when I try to create a wlan interface : >> >> bwn_v4_ucode5: could not load firmware image, error 2 >> >> bwn0: the fw file(bwn_v4_ucode5) not found >> > >> > Did you try to UP the interface withload loading bwn_v4_ucode.ko? If >> > yes currently bwn(4) doesn't automatically load firmware module so you >> > need to do it by hand. >> > >> > # kldload bwn_v4_ucode >> >> OK I have loaded bwn_v4_ucode before if_bwn and it works, >> my bad, I should have read the man page more carefully. >> >> > >> > The patch for this is ready to commit and it'll be happened soon. >> > >> >> I have installed bwn-firmware-kmod from ports but the only files I have in >> >> /boot/modules are bwn_v4_lp_ucode.ko and bwn_v4_ucode.ko. So I tried to >> >> copy bwn_v4_ucode to bwn_v4_ucode5 and it seems to work : wlan0 is >> >> created, I can associate to an open Access Point and obtain a DHCP lease. >> >> But if I try to do some network IO (browsing the web) the interface hang >> >> (I cannot obtain a lease anymore). >> > >> > I have a exact same device like you have but I didn't encounter this >> > issue. >> > >> > Are there any messages from bwn(4) when you the interface becomes hang? >> > One more question, after the interface hang, does the system be hang >> > also? >> >> I have no messages in the log (appart bwn0: need multicast update callback). >> In fact it's not a hang, it happens only with the AP that permits me >> to have a web >> access. I have another AP (sitting next to me) and I don't have the >> same behavior : >> I can have and renew my dhcp lease multiple times and configure the AP with >> its >> web interface. With the "buggy" AP I can have a dhcp lease only once and >> nothing >> more. If I destroy and recreate the wlan interface the same thing happens. >> I have no such a problem with if_bwi and this AP. >> >> > >> > One thing you can do is that trying the device with PIO mode not DMA >> > mode using the following tunable variable: >> > >> > hw.bwn.usedma >> > >> > Its default value is 1 to enable DMA operation so if you set it 0, PIO >> > mode would be used and could see the message like below: >> > >> > bwn0: PIO >> > >> > Could you please test with it? >> > >> >> Setting hw.bwn.usedma=0 in loader.conf make no differences >> >> by the way, I need to switch from if_bwn to if_bwi to make some test >> and post the results here, but I have this error message : >> firmware_register: cannot register image bwi_v3_b0g0initvals5, firmware >> table full! >> is this normal ? > > Yes, both bwi and bwn use a lot of individual firmware images, so loading > both of them probably fills up the static array of firmware table entries. > I think there is a constant in subr_firwmare.c you can increase to make the > table bigger. > > -- > John Baldwin > Rising FIRMWARE_MAX from 30 to 60 did the trick ! thanks ! Are there any reasons to have such a "low" default value ? Another good news : putting my card in 11b mode solves my problem. FYI it uses to work fine in 11g mode with if_bwi (at OFDM/54Mbs). posting with if_bwn ! thanks to all ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Tue, Mar 02, 2010 at 07:57:26PM +0100, Gustau P?rez wrote: > En/na John Baldwin ha escrit: > > On Monday 01 March 2010 3:22:34 pm Gustau P?rez wrote: > > > >> En/na Weongyo Jeong ha escrit: > >> > >>> On Fri, Feb 26, 2010 at 04:21:06PM -0800, Xin LI wrote: > >>> > >>> > Hi, Weongyo, > > On 2010/02/25 16:51, Weongyo Jeong wrote: > > > > FYI bwn(4) driver is committed into FreeBSD tree. I think the driver > > supports your LP PHY device. After cvsup please try to rebuild siba_bwn > > and bwn modules. > > > > Could you please test with it? Please let me know and send me your > > full dmesg when you encounters the following problems: > > > > - if the driver doesn't work or is unstable. > > - if it prints debugging or verbose messages. > > > > > Great! Thanks for the work! > > Is it possible to MFC the work back to 8-STABLE at some point? > > > >>> Of course yes. AFAIK it could be compiled and works without problems on > >>> 8-STABLE; I checked it. :-) > >>> > >>> > >>> > >>I'm trying to run it in STABLE right now. When kldloading if_bwm > >> (following the given instructions, the other modules are kldloaded) it > >> complains with : > >> > >> link_elf_obj: symbol _mtx_assert undefined > >> > >>looks like it fails in if_bwnvar.h. Culprit is this define : > >> > >> #defineBWN_ASSERT_LOCKED(sc) > >> mtx_assert(&(sc)->sc_mtx, MA_OWNED) > >> > >>Do I need witness enabled to run this ? Is there any way to run it in > >> STABLE or do I need to run CURRENT ? > >> > > > > It sounds like you have INVARIANTS defined when the module was built, but > > your > > kernel does not have INVARIANT_SUPPORT defined. > > > > >That did it. Thank you. After recompiling and rebooting the kernel, I > noticed via dmesg that when kldloading ssb the module complains with : > > ssb0: mem > 0xf9ffc000-0xf9ff irq 17 at device 0.0 on pci12 > ssb0: unsupportted coreid 0x817 > >When kldloading if_bwn (after bwn_v4_ucode) the machine freezes. I > guess my hard isn't supported yet. It looks you're using old bwn(4) sources. Could you test it with sources on HEAD? You should use and compile siba_bwn module and bwn module on HEAD. regards, Weongyo Jeong ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Tuesday 02 March 2010 2:08:55 pm Miki wrote: > 2010/3/1 Weongyo Jeong : > > On Sun, Feb 28, 2010 at 08:45:32PM +0100, Miki wrote: > >> Hi, > >> > >> Thanks for the work ! > >> > >> I have some problems here when I try to create a wlan interface : > >> bwn_v4_ucode5: could not load firmware image, error 2 > >> bwn0: the fw file(bwn_v4_ucode5) not found > > > > Did you try to UP the interface withload loading bwn_v4_ucode.ko? If > > yes currently bwn(4) doesn't automatically load firmware module so you > > need to do it by hand. > > > > # kldload bwn_v4_ucode > > OK I have loaded bwn_v4_ucode before if_bwn and it works, > my bad, I should have read the man page more carefully. > > > > > The patch for this is ready to commit and it'll be happened soon. > > > >> I have installed bwn-firmware-kmod from ports but the only files I have in > >> /boot/modules are bwn_v4_lp_ucode.ko and bwn_v4_ucode.ko. So I tried to > >> copy bwn_v4_ucode to bwn_v4_ucode5 and it seems to work : wlan0 is > >> created, I can associate to an open Access Point and obtain a DHCP lease. > >> But if I try to do some network IO (browsing the web) the interface hang > >> (I cannot obtain a lease anymore). > > > > I have a exact same device like you have but I didn't encounter this > > issue. > > > > Are there any messages from bwn(4) when you the interface becomes hang? > > One more question, after the interface hang, does the system be hang > > also? > > I have no messages in the log (appart bwn0: need multicast update callback). > In fact it's not a hang, it happens only with the AP that permits me > to have a web > access. I have another AP (sitting next to me) and I don't have the > same behavior : > I can have and renew my dhcp lease multiple times and configure the AP with > its > web interface. With the "buggy" AP I can have a dhcp lease only once and > nothing > more. If I destroy and recreate the wlan interface the same thing happens. > I have no such a problem with if_bwi and this AP. > > > > > One thing you can do is that trying the device with PIO mode not DMA > > mode using the following tunable variable: > > > > hw.bwn.usedma > > > > Its default value is 1 to enable DMA operation so if you set it 0, PIO > > mode would be used and could see the message like below: > > > > bwn0: PIO > > > > Could you please test with it? > > > > Setting hw.bwn.usedma=0 in loader.conf make no differences > > by the way, I need to switch from if_bwn to if_bwi to make some test > and post the results here, but I have this error message : > firmware_register: cannot register image bwi_v3_b0g0initvals5, firmware > table full! > is this normal ? Yes, both bwi and bwn use a lot of individual firmware images, so loading both of them probably fills up the static array of firmware table entries. I think there is a constant in subr_firwmare.c you can increase to make the table bigger. -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Wed, 3 Mar 2010 00:28:33 -0800 Weongyo Jeong 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 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: mem 0xf400-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: mem 0xf400-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 Украина ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Mon, Mar 01, 2010 at 10:32:40AM +0200, Alexandr Rybalko wrote: > On Sun, 28 Feb 2010 01:52:59 -0800 > Weongyo Jeong wrote: > > >> On Sat, Feb 27, 2010 at 01:15:35AM +0200, Alex RAY wrote: > >> > Hi Weongyo, > >> > > >> > Can new siba release operate in systems like in this SVG image? > >> > System example: CPU BCM5836 + Wi-Fi BCM4318 > >> > >> Recent changes of siba(4) by myself doesn't change code flow, layout and > >> doesn't include enhancements if you're an user of SENTRY5 mips CPU (like > >> BCM5836) > >> > >> All I did on recent changes were to put common routines or codes which > >> could be used for original siba(4). These codes are only used for > >> bwn(4) driver currently and don't be merged with original siba(4). That > >> means there are two separated codes in current siba(4) so merging two > >> into one is a TODO. > >> > >> I have no idea current siba(4) supports a system using on CPU BCM5836 + > >> Wi-Fi BCM4318 but in theory it should work without problems though I > >> didn't test. > >> > >> > And can we compile siba bus code without pci code? > >> > >> I think it looks that it could be possible to compile without pci code. > >> But makes sure that your device doesn't have PCI core. > > 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. > > ssb0: mem 0xf400-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. regards, Weongyo Jeong ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
En/na John Baldwin ha escrit: > On Monday 01 March 2010 3:22:34 pm Gustau Pérez wrote: > >> En/na Weongyo Jeong ha escrit: >> >>> On Fri, Feb 26, 2010 at 04:21:06PM -0800, Xin LI wrote: >>> >>> Hi, Weongyo, On 2010/02/25 16:51, Weongyo Jeong wrote: > FYI bwn(4) driver is committed into FreeBSD tree. I think the driver > supports your LP PHY device. After cvsup please try to rebuild siba_bwn > and bwn modules. > > Could you please test with it? Please let me know and send me your > full dmesg when you encounters the following problems: > > - if the driver doesn't work or is unstable. > - if it prints debugging or verbose messages. > > Great! Thanks for the work! Is it possible to MFC the work back to 8-STABLE at some point? >>> Of course yes. AFAIK it could be compiled and works without problems on >>> 8-STABLE; I checked it. :-) >>> >>> >>> >>I'm trying to run it in STABLE right now. When kldloading if_bwm >> (following the given instructions, the other modules are kldloaded) it >> complains with : >> >> link_elf_obj: symbol _mtx_assert undefined >> >>looks like it fails in if_bwnvar.h. Culprit is this define : >> >> #defineBWN_ASSERT_LOCKED(sc) >> mtx_assert(&(sc)->sc_mtx, MA_OWNED) >> >>Do I need witness enabled to run this ? Is there any way to run it in >> STABLE or do I need to run CURRENT ? >> > > It sounds like you have INVARIANTS defined when the module was built, but > your > kernel does not have INVARIANT_SUPPORT defined. > > That did it. Thank you. After recompiling and rebooting the kernel, I noticed via dmesg that when kldloading ssb the module complains with : ssb0: mem 0xf9ffc000-0xf9ff irq 17 at device 0.0 on pci12 ssb0: unsupportted coreid 0x817 When kldloading if_bwn (after bwn_v4_ucode) the machine freezes. I guess my hard isn't supported yet. Regards, Gus -- PGP KEY : http://www-entel.upc.edu/gus/gus.asc ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
2010/3/1 Weongyo Jeong : > On Sun, Feb 28, 2010 at 08:45:32PM +0100, Miki wrote: >> Hi, >> >> Thanks for the work ! >> >> I have some problems here when I try to create a wlan interface : >> bwn_v4_ucode5: could not load firmware image, error 2 >> bwn0: the fw file(bwn_v4_ucode5) not found > > Did you try to UP the interface withload loading bwn_v4_ucode.ko? If > yes currently bwn(4) doesn't automatically load firmware module so you > need to do it by hand. > > # kldload bwn_v4_ucode OK I have loaded bwn_v4_ucode before if_bwn and it works, my bad, I should have read the man page more carefully. > > The patch for this is ready to commit and it'll be happened soon. > >> I have installed bwn-firmware-kmod from ports but the only files I have in >> /boot/modules are bwn_v4_lp_ucode.ko and bwn_v4_ucode.ko. So I tried to >> copy bwn_v4_ucode to bwn_v4_ucode5 and it seems to work : wlan0 is >> created, I can associate to an open Access Point and obtain a DHCP lease. >> But if I try to do some network IO (browsing the web) the interface hang >> (I cannot obtain a lease anymore). > > I have a exact same device like you have but I didn't encounter this > issue. > > Are there any messages from bwn(4) when you the interface becomes hang? > One more question, after the interface hang, does the system be hang > also? I have no messages in the log (appart bwn0: need multicast update callback). In fact it's not a hang, it happens only with the AP that permits me to have a web access. I have another AP (sitting next to me) and I don't have the same behavior : I can have and renew my dhcp lease multiple times and configure the AP with its web interface. With the "buggy" AP I can have a dhcp lease only once and nothing more. If I destroy and recreate the wlan interface the same thing happens. I have no such a problem with if_bwi and this AP. > > One thing you can do is that trying the device with PIO mode not DMA > mode using the following tunable variable: > > hw.bwn.usedma > > Its default value is 1 to enable DMA operation so if you set it 0, PIO > mode would be used and could see the message like below: > > bwn0: PIO > > Could you please test with it? > Setting hw.bwn.usedma=0 in loader.conf make no differences by the way, I need to switch from if_bwn to if_bwi to make some test and post the results here, but I have this error message : firmware_register: cannot register image bwi_v3_b0g0initvals5, firmware table full! is this normal ? Thanks for your help ! ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Monday 01 March 2010 3:22:34 pm Gustau Pérez wrote: > En/na Weongyo Jeong ha escrit: > > On Fri, Feb 26, 2010 at 04:21:06PM -0800, Xin LI wrote: > > > >> Hi, Weongyo, > >> > >> On 2010/02/25 16:51, Weongyo Jeong wrote: > >> > >>> FYI bwn(4) driver is committed into FreeBSD tree. I think the driver > >>> supports your LP PHY device. After cvsup please try to rebuild siba_bwn > >>> and bwn modules. > >>> > >>> Could you please test with it? Please let me know and send me your > >>> full dmesg when you encounters the following problems: > >>> > >>> - if the driver doesn't work or is unstable. > >>> - if it prints debugging or verbose messages. > >>> > >> Great! Thanks for the work! > >> > >> Is it possible to MFC the work back to 8-STABLE at some point? > >> > > > > Of course yes. AFAIK it could be compiled and works without problems on > > 8-STABLE; I checked it. :-) > > > > >I'm trying to run it in STABLE right now. When kldloading if_bwm > (following the given instructions, the other modules are kldloaded) it > complains with : > > link_elf_obj: symbol _mtx_assert undefined > >looks like it fails in if_bwnvar.h. Culprit is this define : > > #defineBWN_ASSERT_LOCKED(sc) > mtx_assert(&(sc)->sc_mtx, MA_OWNED) > >Do I need witness enabled to run this ? Is there any way to run it in > STABLE or do I need to run CURRENT ? It sounds like you have INVARIANTS defined when the module was built, but your kernel does not have INVARIANT_SUPPORT defined. -- John Baldwin ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
En/na Weongyo Jeong ha escrit: > On Fri, Feb 26, 2010 at 04:21:06PM -0800, Xin LI wrote: > >> Hi, Weongyo, >> >> On 2010/02/25 16:51, Weongyo Jeong wrote: >> >>> FYI bwn(4) driver is committed into FreeBSD tree. I think the driver >>> supports your LP PHY device. After cvsup please try to rebuild siba_bwn >>> and bwn modules. >>> >>> Could you please test with it? Please let me know and send me your >>> full dmesg when you encounters the following problems: >>> >>> - if the driver doesn't work or is unstable. >>> - if it prints debugging or verbose messages. >>> >> Great! Thanks for the work! >> >> Is it possible to MFC the work back to 8-STABLE at some point? >> > > Of course yes. AFAIK it could be compiled and works without problems on > 8-STABLE; I checked it. :-) > > I'm trying to run it in STABLE right now. When kldloading if_bwm (following the given instructions, the other modules are kldloaded) it complains with : link_elf_obj: symbol _mtx_assert undefined looks like it fails in if_bwnvar.h. Culprit is this define : #defineBWN_ASSERT_LOCKED(sc) mtx_assert(&(sc)->sc_mtx, MA_OWNED) Do I need witness enabled to run this ? Is there any way to run it in STABLE or do I need to run CURRENT ? Regards, Gus -- PGP KEY : http://www-entel.upc.edu/gus/gus.asc ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Sun, Feb 28, 2010 at 08:45:32PM +0100, Miki wrote: > Hi, > > Thanks for the work ! > > I have some problems here when I try to create a wlan interface : > bwn_v4_ucode5: could not load firmware image, error 2 > bwn0: the fw file(bwn_v4_ucode5) not found Did you try to UP the interface withload loading bwn_v4_ucode.ko? If yes currently bwn(4) doesn't automatically load firmware module so you need to do it by hand. # kldload bwn_v4_ucode The patch for this is ready to commit and it'll be happened soon. > I have installed bwn-firmware-kmod from ports but the only files I have in > /boot/modules are bwn_v4_lp_ucode.ko and bwn_v4_ucode.ko. So I tried to > copy bwn_v4_ucode to bwn_v4_ucode5 and it seems to work : wlan0 is > created, I can associate to an open Access Point and obtain a DHCP lease. > But if I try to do some network IO (browsing the web) the interface hang > (I cannot obtain a lease anymore). I have a exact same device like you have but I didn't encounter this issue. Are there any messages from bwn(4) when you the interface becomes hang? One more question, after the interface hang, does the system be hang also? One thing you can do is that trying the device with PIO mode not DMA mode using the following tunable variable: hw.bwn.usedma Its default value is 1 to enable DMA operation so if you set it 0, PIO mode would be used and could see the message like below: bwn0: PIO Could you please test with it? regards, Weongyo Jeong ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Sun, Feb 28, 2010 at 11:56:50PM +, Aditya Sarawgi wrote: > On Wed, Dec 23, 2009 at 11:51:34AM -0800, Weongyo Jeong wrote: > > On Wed, Dec 23, 2009 at 08:18:48AM +, Aditya Sarawgi wrote: > > > On Tue, Dec 22, 2009 at 07:53:31PM -0800, Weongyo Jeong wrote: > > > > Hello, > > > > > > > > Now bwn(4) is available at the public and waiting test and review. The > > > > status of this driver is *alpha* so could make panics, warnings and > > > > errors. Please let me know if you encounter problems. > > > > > > > > The following NICs all I have are only tested on the little endian 64bit > > > > machine and big endian 32bit machine. > > > > > > > > - Broadcom BCM4306 802.11b/g Wireless > > > > - Broadcom BCM4318 802.11b/g Wireless > > > > > > > > I tested basic RX, TX and WPA association as STA mode and checked it > > > > worked. > > > > > > > > As you might know there are still a lot of TODO in the driver so you > > > > could see some verbose messages during testing so please ignore or let > > > > me know it makes problems. > > > > > > > > == How to build and load == > > > > > > > > # cd /usr/src/sys > > > > # fetch http://people.freebsd.org/~weongyo/bwn_20091222.tar.gz > > > > # tar xzf bwn_20091222.tar.gz > > > > # cd modules/ssb > > > > # make && make install > > > > # cd ../.. > > > > # cd modules/bwn > > > > # make && make install > > > > # cd somewhere > > > > # fetch http://people.freebsd.org/~weongyo/bwn_ports_20091222.tar.gz > > > > # tar xzf bwn_ports_20091222.tar.gz > > > > # cd sysutils/b43-fwcutter > > > > # make install clean > > > > # cd ../.. > > > > # cd net/bwn-firmware-kmod > > > > # make install clean > > > > # > > > > # kldload ssb > > > > # kldload bwn_v4_ucode > > > > # kldload if_bwn > > > > > > > > regards, > > > > Weongyo Jeong > > > > > > > > > > Hi, > > > > > > The driver doesn't work with BCM4315, here's what dmesg shows > > > > > > ssb0: mem 0xf400-0xf4003fff > > > irq 19 at device 0.0 on pci6 > > > bwn0 on ssb0 > > > bwn0: unsupported PHY type (5) > > > device_attach: bwn0 attach returned 6 > > > > I see that your device has LP-PHY instead of A/B/G/N PHYs so currently > > it's not supported by bwn(4). > > > > AFAIK linux has a weak but working implementation so we could refer to > > other Open Sources. > > > > regards, > > Weongyo Jeong > > > > Hi, > > It still doesn't work, when I try to do > ifconfig bwn0 scan > I get > ifconfig: unable to get the scan results uses the following commands instead of it that you didn't create the virtual wlan interface: # ifconfig wlan0 create wlandev bwn0 # ifconfig wlan0 up # ifconfig wlan0 scan # ifconfig wlan0 list scan > The device is getting recognized properly > here's the dmesg > > siba_bwn0: mem > 0xf400-0xf4003fff irq 19 at device 0.0 on pci6 > bwn0 on siba_bwn0 > bwn0: WLAN (chipid 0x4312 rev 15) PHY (analog 6 type 5 rev 1) RADIO > (manuf 0x17f ver 0x2062 rev 2) > bwn0: DMA (64 bits) > bwn0: Using 1 MSI messages > bwn0: [FILTER] > > I have loaded the following modules > bwn_v4_ucode.ko Please uses bwn_v4_lp_ucode.ko because your device looks it's LP PHY. > if_bwn.ko > siba_bwn.ko regards, Weongyo Jeong ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Sun, 28 Feb 2010 01:52:59 -0800 Weongyo Jeong wrote: >> On Sat, Feb 27, 2010 at 01:15:35AM +0200, Alex RAY wrote: >> > Hi Weongyo, >> > >> > Can new siba release operate in systems like in this SVG image? >> > System example: CPU BCM5836 + Wi-Fi BCM4318 >> >> Recent changes of siba(4) by myself doesn't change code flow, layout and >> doesn't include enhancements if you're an user of SENTRY5 mips CPU (like >> BCM5836) >> >> All I did on recent changes were to put common routines or codes which >> could be used for original siba(4). These codes are only used for >> bwn(4) driver currently and don't be merged with original siba(4). That >> means there are two separated codes in current siba(4) so merging two >> into one is a TODO. >> >> I have no idea current siba(4) supports a system using on CPU BCM5836 + >> Wi-Fi BCM4318 but in theory it should work without problems though I >> didn't test. >> >> > And can we compile siba bus code without pci code? >> >> I think it looks that it could be possible to compile without pci code. >> But makes sure that your device doesn't have PCI core. >> >> regards, >> Weongyo Jeong >> Can You test your driver without siba_switchcore, I see the device have mapping for all cores on SSB? > ssb0: mem 0xf400-0xf4003fff Think thre is 4 cores. When SSB on nexus, we don`t need core switching, maybe on PCI too. -- Alexandr Rybalko aka Alex RAY ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
Hi, Thanks for the work ! I have some problems here when I try to create a wlan interface : bwn_v4_ucode5: could not load firmware image, error 2 bwn0: the fw file(bwn_v4_ucode5) not found I have installed bwn-firmware-kmod from ports but the only files I have in /boot/modules are bwn_v4_lp_ucode.ko and bwn_v4_ucode.ko. So I tried to copy bwn_v4_ucode to bwn_v4_ucode5 and it seems to work : wlan0 is created, I can associate to an open Access Point and obtain a DHCP lease. But if I try to do some network IO (browsing the web) the interface hang (I cannot obtain a lease anymore). I'm running : FreeBSD acheron.homeunix.org 9.0-CURRENT FreeBSD 9.0-CURRENT #3 r204476M: Sun Feb 28 20:27:03 CET 2010 m...@acheron.homeunix.org:/usr/obj/usr/src/sys/ACHERON amd64 kernel and world are in sync. pciconf -lcv output : siba_b...@pci0:4:0:0: class=0x028000 card=0x70011799 chip=0x432014e4 rev=0x03 hdr=0x00 vendor = 'Broadcom Corporation' device = '802.11b/g Wireless LAN Controller (BCM4309)' class = network verbose dmesg output : siba_bwn0: mem 0xfe6fe000-0xfe6f irq 16 at device 0.0 on pci4 siba_bwn0: Reserved 0x2000 bytes for rid 0x10 type 3 at 0xfe6fe000 bwn0 on siba_bwn0 bwn0: WLAN (chipid 0x4306 rev 5) PHY (analog 2 type 2 rev 2) RADIO (manuf 0x17f ver 0x2050 rev 2) bwn0: DMA (30 bits) bwn0: [MPSAFE] bwn0: [FILTER] bwn0: 11b rates: 1Mbps 2Mbps 5.5Mbps 11Mbps bwn0: 11g rates: 1Mbps 2Mbps 5.5Mbps 11Mbps 6Mbps 9Mbps 12Mbps 18Mbps 24Mbps 36Mbps 48Mbps 54Mbps dmesg output when I create a wlan interface : wlan0: bpf attached wlan0: Ethernet address: 00:11:50:16:c4:47 bwn0: need multicast update callback last message repeated 2 times firmware: 'bwn_v4_ucode5' version 0: 22384 bytes loaded at 0x80c40800 firmware: 'bwn_v4_ucode11' version 0: 29864 bytes loaded at 0x80c45f70 firmware: 'bwn_v4_ucode13' version 0: 32232 bytes loaded at 0x80c4d418 firmware: 'bwn_v4_ucode14' version 0: 31384 bytes loaded at 0x80c55200 firmware: 'bwn_v4_ucode15' version 0: 30488 bytes loaded at 0x80c5cc98 firmware: 'bwn_v4_pcm5' version 0: 1320 bytes loaded at 0x80c643b0 firmware: 'bwn_v4_a0g1initvals5' version 0: 1840 bytes loaded at 0x80c648d8 firmware: 'bwn_v4_a0g0initvals5' version 0: 1840 bytes loaded at 0x80c65008 firmware: 'bwn_v4_b0g0initvals5' version 0: 1840 bytes loaded at 0x80c65738 firmware: 'bwn_v4_b0g0initvals13' version 0: 2080 bytes loaded at 0x80c65e68 firmware: 'bwn_v4_a0g1bsinitvals5' version 0: 158 bytes loaded at 0x80c66688 firmware: 'bwn_v4_a0g0bsinitvals5' version 0: 158 bytes loaded at 0x80c66726 firmware: 'bwn_v4_b0g0bsinitvals5' version 0: 158 bytes loaded at 0x80c667c4 firmware: 'bwn_v4_lp0initvals13' version 0: 3618 bytes loaded at 0x80c66862 firmware: 'bwn_v4_lp0initvals14' version 0: 2064 bytes loaded at 0x80c67684 firmware: 'bwn_v4_lp0initvals15' version 0: 2052 bytes loaded at 0x80c67e94 firmware: 'bwn_v4_lp0bsinitvals13' version 0: 158 bytes loaded at 0x80c68698 firmware: 'bwn_v4_lp0bsinitvals14' version 0: 158 bytes loaded at 0x80c68736 firmware: 'bwn_v4_lp0bsinitvals15' version 0: 158 bytes loaded at 0x80c687d4 firmware: 'bwn_v4_n0bsinitvals11' version 0: 158 bytes loaded at 0x80c68872 bwn0: firmware version (rev 410 patch 2160 date 0x751a time 0x7c0a) wlan0: ieee80211_new_state_locked: pending INIT -> SCAN transition lost Feb 28 19:57:19 acheron kernel: wlan0: link state changed to UP Feb 28 19:57:19 acheron kernel: bwn0: need multicast update callback Feb 28 19:57:19 acheron last message repeated 2 times Feb 28 19:57:19 acheron dhclient: New IP Address (wlan0): 192.168.2.36 Feb 28 19:57:19 acheron dhclient: New Subnet Mask (wlan0): 255.255.255.0 Feb 28 19:57:19 acheron dhclient: New Broadcast Address (wlan0): 192.168.2.255 Feb 28 19:57:19 acheron dhclient: New Routers (wlan0): 192.168.2.1 ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Wed, Dec 23, 2009 at 11:51:34AM -0800, Weongyo Jeong wrote: > On Wed, Dec 23, 2009 at 08:18:48AM +, Aditya Sarawgi wrote: > > On Tue, Dec 22, 2009 at 07:53:31PM -0800, Weongyo Jeong wrote: > > > Hello, > > > > > > Now bwn(4) is available at the public and waiting test and review. The > > > status of this driver is *alpha* so could make panics, warnings and > > > errors. Please let me know if you encounter problems. > > > > > > The following NICs all I have are only tested on the little endian 64bit > > > machine and big endian 32bit machine. > > > > > > - Broadcom BCM4306 802.11b/g Wireless > > > - Broadcom BCM4318 802.11b/g Wireless > > > > > > I tested basic RX, TX and WPA association as STA mode and checked it > > > worked. > > > > > > As you might know there are still a lot of TODO in the driver so you > > > could see some verbose messages during testing so please ignore or let > > > me know it makes problems. > > > > > > == How to build and load == > > > > > > # cd /usr/src/sys > > > # fetch http://people.freebsd.org/~weongyo/bwn_20091222.tar.gz > > > # tar xzf bwn_20091222.tar.gz > > > # cd modules/ssb > > > # make && make install > > > # cd ../.. > > > # cd modules/bwn > > > # make && make install > > > # cd somewhere > > > # fetch http://people.freebsd.org/~weongyo/bwn_ports_20091222.tar.gz > > > # tar xzf bwn_ports_20091222.tar.gz > > > # cd sysutils/b43-fwcutter > > > # make install clean > > > # cd ../.. > > > # cd net/bwn-firmware-kmod > > > # make install clean > > > # > > > # kldload ssb > > > # kldload bwn_v4_ucode > > > # kldload if_bwn > > > > > > regards, > > > Weongyo Jeong > > > > > > > Hi, > > > > The driver doesn't work with BCM4315, here's what dmesg shows > > > > ssb0: mem 0xf400-0xf4003fff > > irq 19 at device 0.0 on pci6 > > bwn0 on ssb0 > > bwn0: unsupported PHY type (5) > > device_attach: bwn0 attach returned 6 > > I see that your device has LP-PHY instead of A/B/G/N PHYs so currently > it's not supported by bwn(4). > > AFAIK linux has a weak but working implementation so we could refer to > other Open Sources. > > regards, > Weongyo Jeong > Hi, It still doesn't work, when I try to do ifconfig bwn0 scan I get ifconfig: unable to get the scan results The device is getting recognized properly here's the dmesg siba_bwn0: mem 0xf400-0xf4003fff irq 19 at device 0.0 on pci6 bwn0 on siba_bwn0 bwn0: WLAN (chipid 0x4312 rev 15) PHY (analog 6 type 5 rev 1) RADIO (manuf 0x17f ver 0x2062 rev 2) bwn0: DMA (64 bits) bwn0: Using 1 MSI messages bwn0: [FILTER] I have loaded the following modules bwn_v4_ucode.ko if_bwn.ko siba_bwn.ko -- Aditya Sarawgi ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Sat, Feb 27, 2010 at 01:15:35AM +0200, Alex RAY wrote: > Hi Weongyo, > > Can new siba release operate in systems like in this SVG image? > System example: CPU BCM5836 + Wi-Fi BCM4318 Recent changes of siba(4) by myself doesn't change code flow, layout and doesn't include enhancements if you're an user of SENTRY5 mips CPU (like BCM5836) All I did on recent changes were to put common routines or codes which could be used for original siba(4). These codes are only used for bwn(4) driver currently and don't be merged with original siba(4). That means there are two separated codes in current siba(4) so merging two into one is a TODO. I have no idea current siba(4) supports a system using on CPU BCM5836 + Wi-Fi BCM4318 but in theory it should work without problems though I didn't test. > And can we compile siba bus code without pci code? I think it looks that it could be possible to compile without pci code. But makes sure that your device doesn't have PCI core. regards, Weongyo Jeong ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Fri, Feb 26, 2010 at 04:21:06PM -0800, Xin LI wrote: > Hi, Weongyo, > > On 2010/02/25 16:51, Weongyo Jeong wrote: > > FYI bwn(4) driver is committed into FreeBSD tree. I think the driver > > supports your LP PHY device. After cvsup please try to rebuild siba_bwn > > and bwn modules. > > > > Could you please test with it? Please let me know and send me your > > full dmesg when you encounters the following problems: > > > > - if the driver doesn't work or is unstable. > > - if it prints debugging or verbose messages. > > Great! Thanks for the work! > > Is it possible to MFC the work back to 8-STABLE at some point? Of course yes. AFAIK it could be compiled and works without problems on 8-STABLE; I checked it. :-) > A colleague of mine has tried to compile the code on 8-STABLE but seems > that it's using some new API I guess... I've asked him to try a > 9-CURRENT kernel but the Atom based netbook would take some while to > compile the code =-) Thank you. regards, Weongyo Jeong ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
compiling FreeBSD to test a netbook (was: Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver)
On Fri, 26 Feb 2010 16:21:06 -0800 Xin LI wrote: > I've asked him to try a > 9-CURRENT kernel but the Atom based netbook would take some while to > compile the code =-) It's very easy/quick to (cross) compile world at a beafy machine and install the system to an USB stick. -- WBR, Boris Samorodov (bsam) Research Engineer, http://www.ipt.ru Telephone & Internet SP FreeBSD Committer, http://www.FreeBSD.org The Power To Serve ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Weongyo, On 2010/02/25 16:51, Weongyo Jeong wrote: > FYI bwn(4) driver is committed into FreeBSD tree. I think the driver > supports your LP PHY device. After cvsup please try to rebuild siba_bwn > and bwn modules. > > Could you please test with it? Please let me know and send me your > full dmesg when you encounters the following problems: > > - if the driver doesn't work or is unstable. > - if it prints debugging or verbose messages. Great! Thanks for the work! Is it possible to MFC the work back to 8-STABLE at some point? A colleague of mine has tried to compile the code on 8-STABLE but seems that it's using some new API I guess... I've asked him to try a 9-CURRENT kernel but the Atom based netbook would take some while to compile the code =-) Cheers, - -- Xin LI http://www.delphij.net/ FreeBSD - The Power to Serve! Live free or die -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.14 (FreeBSD) iQEcBAEBAgAGBQJLiGVyAAoJEATO+BI/yjfBcYgH/2Ruc4z9+MsI3xvVm13YIRaH rxkRIOXCs7ViyKLPPh5bwDQiBeiOY10WL+GFxJSg/pO7NBc+gHzkJDZNt6LJtlst iKPcHPwWdxcPbCU7IhO3sIiuMa5WJfH/Aq8tAhlsovlfJwQiukZ4GuhI510q3qo1 2drYi8Z53Ad67/mExMl0gsk0QKIHK3AraQyDV/xRocqdReM+J7TvqxIi0E4dyqha SFTocul34Hht9iH25fd7WPnSUNp+HRgyA6K5hh5ylKzTf2ojsRN/9YE81C+RVDys nADEFN2w1ufbPepxJ7KURQuwTyf7MLkQdqCpKfWGyS90pDm4mh/5wLBk50rsZTs= =kums -END PGP SIGNATURE- ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
Hi Weongyo, Can new siba release operate in systems like in this SVG image? System example: CPU BCM5836 + Wi-Fi BCM4318 And can we compile siba bus code without pci code? - Cut this to file.svg --- http://www.w3.org/1999/xlink"; xmlns="http://www.w3.org/2000/svg";> Layer 1 SSB SSB MIPS MIPS PCI 802.11 - Cut this to file.svg --- -- Alex RAY ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
Re: Call for Test and Review: bwn(4) - another Broadcom Wireless driver
On Wed, Dec 23, 2009 at 08:18:48AM +, Aditya Sarawgi wrote: > On Tue, Dec 22, 2009 at 07:53:31PM -0800, Weongyo Jeong wrote: > > Hello, > > > > Now bwn(4) is available at the public and waiting test and review. The > > status of this driver is *alpha* so could make panics, warnings and > > errors. Please let me know if you encounter problems. > > > > The following NICs all I have are only tested on the little endian 64bit > > machine and big endian 32bit machine. > > > > - Broadcom BCM4306 802.11b/g Wireless > > - Broadcom BCM4318 802.11b/g Wireless > > > > I tested basic RX, TX and WPA association as STA mode and checked it > > worked. > > > > As you might know there are still a lot of TODO in the driver so you > > could see some verbose messages during testing so please ignore or let > > me know it makes problems. > > > > == How to build and load == > > > > # cd /usr/src/sys > > # fetch http://people.freebsd.org/~weongyo/bwn_20091222.tar.gz > > # tar xzf bwn_20091222.tar.gz > > # cd modules/ssb > > # make && make install > > # cd ../.. > > # cd modules/bwn > > # make && make install > > # cd somewhere > > # fetch http://people.freebsd.org/~weongyo/bwn_ports_20091222.tar.gz > > # tar xzf bwn_ports_20091222.tar.gz > > # cd sysutils/b43-fwcutter > > # make install clean > > # cd ../.. > > # cd net/bwn-firmware-kmod > > # make install clean > > # > > # kldload ssb > > # kldload bwn_v4_ucode > > # kldload if_bwn > > > > regards, > > Weongyo Jeong > > > > Hi, > > The driver doesn't work with BCM4315, here's what dmesg shows > > ssb0: mem 0xf400-0xf4003fff > irq 19 at device 0.0 on pci6 > bwn0 on ssb0 > bwn0: unsupported PHY type (5) > device_attach: bwn0 attach returned 6 FYI bwn(4) driver is committed into FreeBSD tree. I think the driver supports your LP PHY device. After cvsup please try to rebuild siba_bwn and bwn modules. Could you please test with it? Please let me know and send me your full dmesg when you encounters the following problems: - if the driver doesn't work or is unstable. - if it prints debugging or verbose messages. regards, Weongyo Jeong ___ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
