From: CACook@quantum-sci.com
To: Michal Kazior <michal.kazior@tieto.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Buss Reset Problem
Date: Thu, 09 Jul 2015 07:11:41 -0700 [thread overview]
Message-ID: <2921819.TX9FEibvXY@andromeda> (raw)
In-Reply-To: <CA+BoTQk1jn=jBNXhrCxy2s=6BzLW=jjTxBk+2Ha+y-PbFQkkMQ@mail.gmail.com>
On Thursday 09 July 2015 15:46:55 Michal Kazior wrote:
> > So that's it for the Doodle Labs ACE-DB-3. It went back yesterday -- doesn't work with Linux.
>
> I think someone complained they couldn't get an XB design to work on
> some of their PCI-E hosts (some Atom laptop even refused to POST with
> the card if I recall correctly). Apparently there's an electrical
> quirk - or at least that was to conclusion back then.
>
>
> > It's not the buss reset problem as I patched quirks.c.
>
> I wonder how much related this could be to Data Bus Error ath10k sees
> when doing cold resets sometimes. Maybe it's good to have the quirk
> fixup nonetheless? But I'm no PCI expert so what do I know.
Yes the problem is very early in boot. In KVM guest almost right after Grub it says that PCIe address does not exist (or is not accessible), and sure enough I check it on the host and it's flipped to "Invalid header". I have to reboot the _host_ to get the card back then.
The card has good specs but Doodle doesn't care about this problem, and I just don't have time to uselessly fiddle with it.
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2015-07-09 14:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-06 15:04 Buss Reset Problem CACook
2015-07-09 13:33 ` CACook
2015-07-09 13:46 ` Michal Kazior
2015-07-09 14:11 ` CACook [this message]
2015-07-10 5:48 ` Michal Kazior
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=2921819.TX9FEibvXY@andromeda \
--to=cacook@quantum-sci.com \
--cc=ath10k@lists.infradead.org \
--cc=michal.kazior@tieto.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.