From: Darek Marcinkiewicz <reksio@newterm.pl>
To: Jean Delvare <jdelvare@suse.de>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH] net: ec_bhf: Add runtime dependencies
Date: Tue, 27 May 2014 22:30:59 +0200 [thread overview]
Message-ID: <20140527203059.GA25384@newterm.pl> (raw)
In-Reply-To: <20140526212614.6e2610b0@endymion.delvare>
On Mon, May 26, 2014 at 09:26:14PM +0200, Jean Delvare wrote:
> The ec_bhf driver is specific to the Beckhoff CX5020, an embedded PC
> based on a 32-bit Intel Atom CPU. So we can add a dependency on
> X86_32, with COMPILE_TEST as an alternative to still allow for broader
> build-testing.
>
> Signed-off-by: Jean Delvare <jdelvare@suse.de>
> Cc: Darek Marcinkiewicz <reksio@newterm.pl>
> Cc: David S. Miller <davem@davemloft.net>
> ---
> drivers/net/ethernet/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> --- linux-3.15-rc7.orig/drivers/net/ethernet/Kconfig 2014-05-26 09:24:00.555619955 +0200
> +++ linux-3.15-rc7/drivers/net/ethernet/Kconfig 2014-05-26 21:01:32.971410992 +0200
> @@ -39,6 +39,7 @@ source "drivers/net/ethernet/cisco/Kconf
> config CX_ECAT
> tristate "Beckhoff CX5020 EtherCAT master support"
> depends on PCI
> + depends on X86_32 || COMPILE_TEST
> ---help---
> Driver for EtherCAT master module located on CCAT FPGA
> that can be found on Beckhoff CX5020, and possibly other of CX
>
>
It makes sense, just one more comment. It is pretty likely that
this driver also works with CX20** family of Beckhoff embedded PCs, which
have 64bit Intel iCore processor. Unfortunately, I haven't yet had a chance
to get my hands on any of those so cannot tell for sure. Maybe allowing
this driver also for x64 would be slightly better option?
--
DM
next prev parent reply other threads:[~2014-05-27 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-26 19:26 [PATCH] net: ec_bhf: Add runtime dependencies Jean Delvare
2014-05-27 20:30 ` Darek Marcinkiewicz [this message]
2014-05-30 23:32 ` David Miller
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=20140527203059.GA25384@newterm.pl \
--to=reksio@newterm.pl \
--cc=davem@davemloft.net \
--cc=jdelvare@suse.de \
--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).