From: Gabor Juhos <juhosg@openwrt.org>
To: Gertjan van Wingerde <gwingerde@gmail.com>
Cc: John Crispin <blogic@openwrt.org>,
"John W. Linville" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"users@rt2x00.serialmonkey.com" <users@rt2x00.serialmonkey.com>
Subject: Re: [PATCH] rt2x00: make the driver build for Ralink SoC
Date: Thu, 21 Mar 2013 19:03:30 +0100 [thread overview]
Message-ID: <514B4B72.1000607@openwrt.org> (raw)
In-Reply-To: <3D4497AD-8992-47D6-BCF2-5D738B6AC9B4@gmail.com>
2013.03.20. 22:29 keltezéssel, Gertjan van Wingerde írta:
>
>
> Sent from my iPad
>
> On 20 mrt. 2013, at 20:48, John Crispin <blogic@openwrt.org> wrote:
>
>> Fix up the dependencies to make the driver actually compile on Ralink WiSoC.
>>
>> Signed-off-by: John Crispin <blogic@openwrt.org>
>
> I don't think this is a proper way to handle this. rt2x00pci.c was only
> meant to be used for PCI devices; introducing the use of CONFIG_PCI in that file
> doesn't seem appropriate to me.
Well, CONFIG_PCI is also used in rt2800pci.c. The root cause of the problem is
that rt2800pci (despite its name) is used to drive the built-in wireless MAC of
various SoCs. This is because handling of the PCI and of the SoC built-in
devices is quite similar. However regardless of the underlying bus type,
rt2800pci uses several functions exported from rt2x00pci so it should always
select RT2X00_LIB_PCI.
The rt2x00pci_{probe,remove,suspend,resume} handlers from rt2x00pci are not used
by rt2800pci if PCI disabled. However the presence of that functions in rt2x00
causes build error if the driver is compiled with disabled PCI support.
If we properly want to fix the issue, lots of functions should be renamed and
should be moved into separate modules. The name of these new modules could be
rt2x00mmio and rt2800mmio for example.
Adding CONFIG_PCI to rt2x00pci could be a temporary solution until that is not done.
-Gabor
prev parent reply other threads:[~2013-03-21 18:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 19:48 [PATCH] rt2x00: make the driver build for Ralink SoC John Crispin
2013-03-20 21:29 ` Gertjan van Wingerde
2013-03-21 7:35 ` John Crispin
2013-03-27 17:17 ` John W. Linville
2013-03-27 18:25 ` John Crispin
2013-03-27 20:38 ` Gertjan van Wingerde
2013-03-27 20:48 ` John Crispin
2013-03-29 15:02 ` Gabor Juhos
2013-03-21 18:03 ` Gabor Juhos [this message]
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=514B4B72.1000607@openwrt.org \
--to=juhosg@openwrt.org \
--cc=blogic@openwrt.org \
--cc=gwingerde@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=users@rt2x00.serialmonkey.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;
as well as URLs for NNTP newsgroup(s).