netdev - Re: [net-next v2 70/71] tile: Move the Tilera driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4E399B3C.4010902@tilera.com>
Date:	Wed, 3 Aug 2011 15:02:20 -0400
From:	Chris Metcalf <cmetcalf@...era.com>
To:	<jeffrey.t.kirsher@...el.com>
CC:	"davem@...emloft.net" <davem@...emloft.net>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
	"gospo@...hat.com" <gospo@...hat.com>,
	"sassmann@...hat.com" <sassmann@...hat.com>
Subject: Re: [net-next v2 70/71] tile: Move the Tilera driver

On 8/3/2011 1:47 AM, Jeff Kirsher wrote:
> On 7/30/2011 11:27 PM, Jeff Kirsher wrote:
>>> Move the Tilera driver into drivers/net/ethernet/tile and
>>> make the necessary Kconfig and Makefile changes.
>>>
>>> CC: Chris Metcalf <cmetcalf@...era.com>
>>> Signed-off-by: Jeff Kirsher <jeffrey.t.kirsher@...el.com>
>>> [...]
>>> +++ b/drivers/net/ethernet/tile/Kconfig
>>> @@ -0,0 +1,28 @@
>>> +#
>>> +# Tilera network device configuration
>>> +#
>>> +
>>> +config NET_VENDOR_TILERA
>>> +	bool "Tilera devices"
>>> +	depends on TILE
>>> +	---help---
>>> +	  If you have a network (Ethernet) card belonging to this class, say Y
>>> +	  and read the Ethernet-HOWTO, available from
>>> +	  <http://www.tldp.org/docs.html#howto>.
>>> +
>>> +	  Note that the answer to this question doesn't directly affect the
>>> +	  kernel: saying N will just cause the configurator to skip all
>>> +	  the questions about Tilera cards. If you say Y, you will be asked for
>>> +	  your specific card in the following questions.
>>> +
>>> +config TILE_NET
>>> +	tristate "Tilera GBE/XGBE network driver support"
>>> +	depends on NET_VENDOR_TILERA && TILE
>>> +	default y
>>> +	select CRC32
>>> +	---help---
>>> +	  This is a standard Linux network device driver for the
>>> +	  on-chip Tilera Gigabit Ethernet and XAUI interfaces.
>>> +
>>> +	  To compile this driver as a module, choose M here: the module
>>> +	  will be called tile_net.
>>>
> [...]
>
> This Kconfig would automatically default to y for TILE kernels and would
> allow you to easily add additional future drivers for Tilera silicon,
> and if you expand to other architectures/systems in the future it would
> also allow for that as well.  Your thoughts?
>
> Otherwise I can have it just as this:
> +config TILE_NET
> +       tristate "Tilera GBE/XGBE network driver support"
> +       depends on TILE
> +       default y
> +       select CRC32
> +       ---help---
> +         This is a standard Linux network device driver for the
> +         on-chip Tilera Gigabit Ethernet and XAUI interfaces.
> +
> +         To compile this driver as a module, choose M here: the module
> +         will be called tile_net.
>
> Because you only have 1 driver, there is no large need to add the
> NET_VENDOR_<blah> and it can always be added in the future if the need
> arises.

Honestly, I think I'd prefer the simple TILE_NET solution.  My sense is
that even for the next generation of the chip, we're likely to keep using
TILE_NET to enable it in the config.  Note that we have done this now for
both tilepro and tilegx, though we haven't pushed the tilegx driver back to
the community yet; look at the conditionals in drivers/net/tile/Makefile to
see what I mean.  So let's stick with the simple thing for now.  Thanks!

-- 
Chris Metcalf, Tilera Corp.
http://www.tilera.com

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html