All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Christian Lamparter <chunkeey@web.de>
Cc: linux-wireless@vger.kernel.org,
	"John W. Linville" <linville@tuxdriver.com>,
	"Luis R. Rodriguez" <lrodriguez@atheros.com>
Subject: Re: [PATCH 5/5] ar9170: update Makefile, Kconfig and MAINTAINERS
Date: Tue, 24 Mar 2009 08:41:01 +0100	[thread overview]
Message-ID: <1237880461.6147.24.camel@johannes.local> (raw)
In-Reply-To: <200903240126.12692.chunkeey@web.de>

[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]

On Tue, 2009-03-24 at 01:26 +0100, Christian Lamparter wrote:

> Shh, there's a secret plan, see ar9170/main.c
> 
> /*
>  * BIG FAT TODO:
>  *
>  * By the looks of things: these devices share a lot of things like
>  * EEPROM layout/design and PHY code with other Atheros WIFI products.
>  * So this driver/library will eventually become ath9k code... or vice versa ;-)
>  */
> 
> And the ath5k<->ath9k merge could provide some "helper" function for this
> driver as well... (wishful thinking, but anyway...)

_Very_ wishful thinking -- only very small parts of the design are
really shared, the PHY stuff, which happens to be relevant to the
eeprom.

> Meanwhile, what about a config option that can be enabled to
> integrate everything into the front-end module (ar9170usb)?
> ( However, I don't think this config solution will stand a chance ;-) 
>   and we all come to the same "all-in-one works best" conclusion.  )

This seems like a pointless option. Why not just change the Kconfig file
to remove the common option and link both files into one binary,
removing all EXPORT_SYMBOLs?

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2009-03-24  7:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-21 22:11 [PATCH 5/5] ar9170: update Makefile, Kconfig and MAINTAINERS Christian Lamparter
2009-03-23 14:29 ` Johannes Berg
2009-03-24  0:26   ` Christian Lamparter
2009-03-23 23:35     ` Luis R. Rodriguez
2009-03-24  7:41     ` Johannes Berg [this message]
2009-03-24 15:21       ` [PATCH] ar9170: single module build Christian Lamparter

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=1237880461.6147.24.camel@johannes.local \
    --to=johannes@sipsolutions.net \
    --cc=chunkeey@web.de \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=lrodriguez@atheros.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.