From: Ben Greear <greearb@candelatech.com>
To: Sebastian Gottschall <s.gottschall@dd-wrt.com>
Cc: ath10k@lists.infradead.org
Subject: Re: More than one ath10k NIC in 3.19.0-rc5?
Date: Tue, 20 Jan 2015 18:49:18 -0800 [thread overview]
Message-ID: <54BF13AE.5010909@candelatech.com> (raw)
In-Reply-To: <54BF0B42.7050101@dd-wrt.com>
On 01/20/2015 06:13 PM, Sebastian Gottschall wrote:
> Am 20.01.2015 um 22:53 schrieb Ben Greear:
>> I tried running a patched version of 3.19.0-rc5 kernel, and it seems to work
>> fine when there is one ath10k NIC in the system, but when there is two it
>> doesn't try to load the firmware.
>>
>> Hacked 3.17.8+ works fine.
>>
>> Anyone tried more than one ath10k NIC in 3.19 kernel?
>>
>> Thanks,
>> Ben
> standard x86 system? i just can say that with 3.18 i have big troubles with the new pci bus code introduced on several embedded devices.
> so maybe the reason is here?
Standard 64-bit x86.
Thanks,
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-01-21 2:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-20 21:53 More than one ath10k NIC in 3.19.0-rc5? Ben Greear
2015-01-21 2:13 ` Sebastian Gottschall
2015-01-21 2:49 ` Ben Greear [this message]
2015-01-21 19:01 ` Ben Greear
2015-01-21 19:47 ` Ben Greear
2015-01-22 21:08 ` More than one ath10k NIC will not load (bisected) Ben Greear
2015-01-23 6:43 ` Michal Kazior
2015-01-23 15:54 ` Ben Greear
2015-01-24 18:53 ` Janusz Dziedzic
2015-02-05 20:50 ` AW: " Conrad Kostecki
2015-02-04 9:07 ` Kalle Valo
2015-02-04 9:35 ` Michal Kazior
2015-02-04 12:02 ` Kalle Valo
2015-02-04 15:23 ` Ben Greear
2015-02-05 6:02 ` Michal Kazior
2015-02-05 6:41 ` Ben Greear
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=54BF13AE.5010909@candelatech.com \
--to=greearb@candelatech.com \
--cc=ath10k@lists.infradead.org \
--cc=s.gottschall@dd-wrt.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.