[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOiHx=n4a26z=PS02E2KjD2Y3Pp0P0x-5Ns6WRc-WScNF=EO_Q@mail.gmail.com>
Date: Wed, 13 Mar 2013 10:51:33 +0100
From: Jonas Gorski <jogo@...nwrt.org>
To: Paul Bolle <pebolle@...cali.nl>
Cc: Ivo van Doorn <IvDoorn@...il.com>,
Gertjan van Wingerde <gwingerde@...il.com>,
Helmut Schaa <helmut.schaa@...glemail.com>,
"John W. Linville" <linville@...driver.com>,
linux-wireless@...r.kernel.org, users@...x00.serialmonkey.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
John Crispin <blogic@...nwrt.org>
Subject: Re: rt2x00: Kconfig symbols RALINK_RT288X and RALINK_RT305X
On 13 March 2013 09:59, Paul Bolle <pebolle@...cali.nl> wrote:
> 0) Support for rt2800pci (or "the rt2860/rt3090 chipsets") was added in
> v2.6.33 (three years ago). References to the related Kconfig symbols
> RALINK_RT288X and RALINK_RT305X were introduced in that release. So were
> checks for their macros (CONFIG_RALINK_RT288X and CONFIG_RALINK_RT305X).
>
> 1) The Kconfig symbols themselves were never added in mainline. So these
> references and macros appear to be just markers for dead code in
> mainline, as that code will not be built.
>
> 2) This was previously discussed in
> https://lkml.org/lkml/2010/7/14/110 . The patch submitted in that
> message (which would remove all the dead code at the time) did not get
> applied.
>
> 3) What is the current status of the (out of tree) code that adds
> RALINK_RT288X and RALINK_RT305X?
They are now present in 3.9-rc1, see a0b0197c (more specifically
85639910..d3d2b420) :)
The actual accepted Kconfig symbol names are different though, so they
should be changed in rt2x00 to match them (SOC_RT288X and SOC_RT305X).
Jonas
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists