From: Oleksij Rempel <linux@rempel-privat.de>
To: Adam Williamson <awilliam@redhat.com>,
linux-wireless@vger.kernel.org, ath6kl-devel@qualcomm.com
Subject: Re: Support for Atheros chipset with SDIO ID 0271:0418 ?
Date: Sat, 30 Nov 2013 20:42:19 +0100 [thread overview]
Message-ID: <529A3F9B.6070306@rempel-privat.de> (raw)
In-Reply-To: <1385838681.2566.6.camel@adam.happyassassin.net>
Am 30.11.2013 20:11, schrieb Adam Williamson:
> Hi, folks - I hope this is the appropriate place, it's as close as I
> could manage to Google myself :) I recently bought a Dell Venue 8 Pro -
> a Bay Trail / Valley View-based Intel tablet - to try and get Fedora
> running on it. Among the many things I'm currently fighting :), the
> wireless doesn't work - no driver is loaded, no interface appears at
> all. Using the Device Manager in Windows 8 I've managed to identify it
> as being attached via SDIO and having the device ID 0271:0418 . It calls
> itself a "Dell Wireless 1538", but by the ID and various other details
> about the Windows driver it's clearly a Qualcomm/Atheros part.
>
> So the ath6kl-sdio driver in the kernel advertises support for:
>
> alias: sdio:c*v0271d0401*
> alias: sdio:c*v0271d0400*
> alias: sdio:c*v0271d0301*
> alias: sdio:c*v0271d0300*
>
> Looks pretty close, but no cigar. I'm having trouble finding any more
> information on the chipset than what I've outlined above. It seems most
> likely that it's a variant of the AR6004 for Dell, but that's just my
> best guess.
>
> Is there any hope of getting support for this device in ath6kl or any
> other driver? Thanks!
If this device continued HIF/WMI tradition, then most probably it works
same way like ar5523, ath6kl-sdio or ath9k-htc do.
The question is, do all WMI commands present?
--
Regards,
Oleksij
next prev parent reply other threads:[~2013-11-30 19:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-30 19:11 Support for Atheros chipset with SDIO ID 0271:0418 ? Adam Williamson
2013-11-30 19:42 ` Oleksij Rempel [this message]
2013-11-30 19:48 ` Adrian Chadd
2013-12-04 8:05 ` Adam Williamson
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=529A3F9B.6070306@rempel-privat.de \
--to=linux@rempel-privat.de \
--cc=ath6kl-devel@qualcomm.com \
--cc=awilliam@redhat.com \
--cc=linux-wireless@vger.kernel.org \
/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