Date: Fri, 21 Jan 2011 08:31:22 +0300 From: Dmitry Kolosov <onyx@z-up.ru> To: freebsd-mobile@freebsd.org Subject: Re: More if_ath churn coming your way! Message-ID: <201101210831.23094.onyx@z-up.ru> In-Reply-To: <AANLkTimOc%2BE-q5Rba0-qPngPwfUOtec40KL94yXp3112@mail.gmail.com> References: <AANLkTikBpHcimOvSGdppc9CdhWguZNbTUEwan%2BQ172QT@mail.gmail.com> <201101202026.30341.onyx@z-up.ru> <AANLkTimOc%2BE-q5Rba0-qPngPwfUOtec40KL94yXp3112@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> I need to know the output in dmesg of the chipset MAC/PHY revisions. This is for dwl-547 pci card ath1: <Atheros 9280> mem 0xff9b0000-0xff9bffff irq 23 at device 2.0 on pci5 ath1: AR9280 mac 128.2 RF5133 phy 13.0 and this is for mini-pcie card (inside laptop) ath0: <Atheros 9285> mem 0xd7100000-0xd710ffff irq 17 at device 0.0 on pci6 ath0: AR9285 mac 192.2 RF5133 phy 14.0 > If you have access to older chips (so > AR5212/AR5213 and earlier) and would like to help debug this then > please pipe up. I think i have one. ath0: <Atheros 5212> mem 0xff9f0000-0xff9fffff irq 21 at device 0.0 on pci5 ath0: [ITHREAD] ath0: AR2413 mac 7.9 RF2413 phy 4.5 I'm using it as an AP now, instead of new dwl-547 (wich is ath1 and not used), because using ath1 (Atheros 9280) as AP produces many many errors like that: ath0: stuck beacon; resetting (bmiss count 4) in any mode and finally it's refuses to work at all. That's why i can't use my new dwl-547 :( and it just stays for better times. Also i think i have another one inside my old laptop HP Pavilion dv6940er. I will check it out and report back.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201101210831.23094.onyx>