All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Greear <greearb@candelatech.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: ath10k@lists.infradead.org
Subject: Re: BAR error, failed to get chip id.
Date: Wed, 22 Jan 2014 13:54:39 -0800	[thread overview]
Message-ID: <52E03E1F.8000102@candelatech.com> (raw)
In-Reply-To: <CAA93jw7GShkaY_w5gmbyHpO_rEP_j3hfFRbGZhCB6JBqK0VVzw@mail.gmail.com>

On 01/22/2014 01:49 PM, Dave Taht wrote:
> On Wed, Jan 22, 2014 at 3:33 PM, Ben Greear <greearb@candelatech.com> wrote:
>>
>> I see this fairly often on module reload.  Firmware is modified
>> by me, based on 10.1.389, so if there are firmware fixes since then
>> that address this problem I would not know of it.  Kernel is ath-testing,
>> with some local changes, but nothing pertaining to the pci code.
> 
> I have had pci issues on an older atom box, not on a newer nuc.
> 
> Can try that box again to see what happens.

I'm using a core-i7 low-power system...has been rock solid for ath9k for
a long time, for what that is worth.

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

  reply	other threads:[~2014-01-22 21:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-22 20:33 BAR error, failed to get chip id Ben Greear
2014-01-22 21:49 ` Dave Taht
2014-01-22 21:54   ` Ben Greear [this message]
     [not found] ` <CAJ-VmokveU-WxqboRhdagLwp2E2o-Bic7Pd4LvHaj7TX+rBnYA@mail.gmail.com>
2014-01-23  0:37   ` Ben Greear
     [not found]     ` <CAJ-VmomSpAyESOnBdUHUf__=HC1wp-=otH9-v2PNJbmzLQ6mxg@mail.gmail.com>
2014-01-23  0:49       ` Ben Greear
2014-01-23  6:05     ` Kalle Valo

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=52E03E1F.8000102@candelatech.com \
    --to=greearb@candelatech.com \
    --cc=ath10k@lists.infradead.org \
    --cc=dave.taht@gmail.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.