netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Buesch <mb@bu3sch.de>
To: Daniel Drake <ddrake@brontes3d.com>
Cc: netdev@vger.kernel.org, madwifi-devel@lists.sourceforge.net
Subject: Re: ar5k and Atheros AR5005G
Date: Tue, 28 Nov 2006 21:45:08 +0100	[thread overview]
Message-ID: <200611282145.08423.mb@bu3sch.de> (raw)
In-Reply-To: <1164746352.31456.22.camel@systems03.lan.brontes3d.com>

On Tuesday 28 November 2006 21:39, Daniel Drake wrote:
> Hi,
> 
> I'm interested in porting the ar5k driver to Linux after the recent SFLC
> conclusions on the legal status. However, the hardware I have here
> appears to be unsupported by ar5k:
> 
> 01:04.0 0200: 168c:001a (rev 01)
>         Subsystem: 168c:2052
> 
> 01:04.0 Ethernet controller: Atheros Communications, Inc. AR5005G
> 802.11abg NIC (rev 01)
>         Subsystem: Atheros Communications, Inc. Unknown device 2052
>         Flags: bus master, medium devsel, latency 168, IRQ 66
>         Memory at c0100000 (32-bit, non-prefetchable) [size=64K]
>         Capabilities: [44] Power Management version 2
> 
> It is a mini-PCI card.
> 
> Does anyone know how much work would be needed for the ar5k codebase to
> support this hardware?

I started to port this at
http://bu3sch.de/ath/atheros.git/

I dunno how hard it is to add hw support.

-- 
Greetings Michael.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

  reply	other threads:[~2006-11-28 20:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-28 20:39 ar5k and Atheros AR5005G Daniel Drake
2006-11-28 20:45 ` Michael Buesch [this message]
2006-11-29 13:55   ` [Madwifi-devel] " Nick Kossifidis
2006-11-29 14:05     ` Michael Buesch
2006-11-29 14:34       ` Nick Kossifidis
2006-11-29 15:12         ` Michael Buesch
2006-11-29 15:21           ` Dan Williams
2006-11-29 15:30             ` David Kimdon
2006-11-29 15:24           ` David Kimdon
2006-11-29 15:38             ` Michael Buesch
2006-11-29 15:58               ` Michael Renzmann
2006-11-29 16:03                 ` Michael Buesch
2006-11-30  5:33                   ` Michael Renzmann
2006-11-29 16:03               ` [Madwifi-devel] " David Kimdon
2006-11-29 20:13                 ` Stephen Hemminger
2006-12-01 18:35                   ` [Madwifi-devel] " Luis R. Rodriguez
2006-12-01 18:37                     ` Luis R. Rodriguez
2006-12-05 14:39                     ` Michael Renzmann
2006-12-05 15:15                       ` Luis R. Rodriguez
2006-12-05 17:18                         ` Stephen Hemminger
2006-12-05 18:57                           ` Luis R. Rodriguez
2006-11-29 15:47             ` Michael Buesch
2006-11-29 15:56     ` Daniel Drake

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=200611282145.08423.mb@bu3sch.de \
    --to=mb@bu3sch.de \
    --cc=ddrake@brontes3d.com \
    --cc=madwifi-devel@lists.sourceforge.net \
    --cc=netdev@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;
as well as URLs for NNTP newsgroup(s).