From: vagner <vagnerrener@gmail.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: "ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Qualcomm Atheros Device 0042 (rev 30)
Date: Thu, 7 Jan 2016 18:20:14 +0200 [thread overview]
Message-ID: <568E903E.1040708@gmail.com> (raw)
In-Reply-To: <CA+BoTQmDO2NDEKo+uP5BCts=bX1xVVUcbQynEZNaZUeDDQ8g7w@mail.gmail.com>
On 01/07/2016 02:41 PM, Michal Kazior wrote:
> On 7 January 2016 at 13:15, vagner<vagnerrener@gmail.com> wrote:
>> Hi,
>>
>> Last week I compiled a 4.4-rcX kernel and the dmesg showed me that it was
>> trying to load ath10k, but it failed. So, I gave up and installed 4.3 again.
>> Perhaps I did something wrong, but I hope that the next 4.4 kernel will
>> bring support for my wireless card.
> Just post dmesg from 4.4 once you try again. You could've been missing
> firmware files in paths ath10k expected them to be.
Thx a lot. But, I prefer to wait for the next kernel to see what
happens. Compiling a kernel takes a long time and I do not have much
experience on doing that...
Ant if I go to experimental I am afraid of mixing up my debian and
breaking it.
I'd like to know how to use the windows drive, at least until the
new kernel support my card. But, I know that this is not a fixing-linux
way...
>
>> On the other hand I am waiting for a reply from Pratik Singhal who said he
>> was successful in making his wireless card - also in a lenovo ideapad - to
>> work using a Windows drive...
> You/he probably mean using some firmware-related stuff from windows
> driver package - most likely the eeprom/board file which can be an
> annoying requirement.
>
>
>> By the way, do you know when 4.4-kernel is due?
> According to the crystal ball it's due somewhere next week
> (http://phb-crystal-ball.org/). It's already at -rc8 so I think it's a
> matter of days.
>
> Since you use debian you could use the `experimental` package repo and
> get distro precompiled 4.4-rc8 right now.
>
>
> Michał
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2016-01-07 16:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 19:43 Qualcomm Atheros Device 0042 (rev 30) vagner
2016-01-07 5:39 ` Hsu, Ryan
2016-01-07 10:20 ` vagner
2016-01-07 11:20 ` Michal Kazior
2016-01-07 12:15 ` vagner
2016-01-07 12:41 ` Michal Kazior
2016-01-07 16:20 ` vagner [this message]
[not found] ` <CAGf2gkO_je4Q=0_RsYTQZtRorZU3U5fhoj+6+9gH5mFvNy1vFg@mail.gmail.com>
2016-01-07 10:33 ` vagner
2016-01-07 10:39 ` vagner
2016-01-07 10:51 ` vagner
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=568E903E.1040708@gmail.com \
--to=vagnerrener@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox