I've been using this for a couple weeks now with no issues, for what
little value my OK is, your patch seems to be ready to roll.
-tim
On 2018-05-06 20:16, Tim Chase wrote:
> On 2018-05-03 17:54, Oleksandr Tymoshenko wrote:
> > Tim Chase (free...@tim.thechases.com) wrote:
>
On 2018-05-03 17:54, Oleksandr Tymoshenko wrote:
> Tim Chase (free...@tim.thechases.com) wrote:
> > ppb0 at pci0 dev 28 function 0 "Intel SCH PCIE" rev 0x07: apic 2
> > int 17 ...
> > athn0 at pci2 dev 0 function 0 "Atheros AR9281" rev 0x01: apic 2
> >
On 2018-05-03 17:54, Oleksandr Tymoshenko wrote:
> Tim Chase (free...@tim.thechases.com) wrote:
> > If it makes any difference, booting OpenBSD 6.3 on the machine
> > says they're both successfully on INT 17 (the ath0/athn0 works
> > there)
> >
> > ppb0 at
On 2018-05-04 00:33, Adrian Chadd wrote:
> Yeah it does look like that. I'm sorry, I don't have the
> time/energy to figure out why allocating that interrupt doesn't
> work on FreeBSD. :(
If this is more of an interrupt/kernel thing than a wifi thing, would
this be better moved to a different free
On 2018-05-02 21:10, Tim Chase wrote:
> On 2018-05-02 23:21, Adrian Chadd wrote:
> > CAn you try booting freebsd-head and see if it's any better?
>
> At your advice, I created a boot image of 12.0-CURRENT r333017 but
> see the same "could not map interrupt" in
On 2018-05-02 23:21, Adrian Chadd wrote:
> CAn you try booting freebsd-head and see if it's any better?
At your advice, I created a boot image of 12.0-CURRENT r333017 but
see the same "could not map interrupt" in my dmesg that I got on 11.x
-tim
PS: thanks for the boot-from-a-memstick-snapshot
I just replaced my rubbish BCM in my Dell Inspiron Mini10 (Atom CPU)
with an Atheros mini-PCI and FreeBSD seems to have trouble bringing
it up:
# dmesg | grep ath0
ath0: mem 0xd800-0xd800 irq 17 at device 0.0 on pci2
ath0: could not map interrupt
device_attach: ath0 attach returned 6
Che
