On 3 April 2013 11:16, maksim yevmenkin wrote:
> Hi Adrian !
>
> Thank you for your work. I briefly looked at it and it seems fine to me. I'm
> not able to give it a proper review as I'm traveling internationally
> currently. Having said all that, I think it would be reasonable to commit it
>
Hi Adrian !
Thank you for your work. I briefly looked at it and it seems fine to me. I'm
not able to give it a proper review as I'm traveling internationally currently.
Having said all that, I think it would be reasonable to commit it as is into
head.
Thanks,
Max
On Apr 3, 2013, at 10:52 A
Hi,
Here you go:
http://people.freebsd.org/~adrian/ath/20130401-ath-bluetooth.diff
The ath3k driver in linux does a fair bit more than ath3kfw:
* if it's a subset of chips that needs firmware, it squirts ath3k-1.fw onto it
* there's a subset of chips that get ROM/RAM patches; so if it's one
of
On 2 April 2013 10:21, Maksim Yevmenkin wrote:
> Hi Adrian,
>
>> Please find a patch which does two things:
>>
>
> patch was lost, apparently :)
Oh for gods sake. God damned mailing list setup.
I'll upload the patch soon.
adrian
___
freebsd-current@
Hi Adrian,
Please find a patch which does two things:
>
>
patch was lost, apparently :)
thanks
max
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-
Hi,
Please find a patch which does two things:
* it allows ath3kfw to be given a vendor/productid, in order to load
firmware into other NICs that only have a very basic firmware
(sflash);
* it blacklists all the NICs that have this particular behaviour
(sourced from linux-next btusb.c driver).
I
