From mboxrd@z Thu Jan  1 00:00:00 1970
From: "David S. Miller" <davem@davemloft.net>
Subject: Re: VJ Channel API - driver level (PATCH)
Date: Thu, 04 May 2006 16:04:32 -0700 (PDT)
Message-ID: <20060504.160432.48902082.davem@davemloft.net>
References: <54AD0F12E08D1541B826BE97C98F99F149E8D5@NT-SJCA-0751.brcm.ad.broadcom.com>
	<445A84E7.1060906@neterion.com>
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Cc: caitlinb@broadcom.com, johnpol@2ka.mipt.ru,
	Leonid.Grossman@neterion.com, shemminger@osdl.org,
	netdev@vger.kernel.org
Return-path: <netdev-owner@vger.kernel.org>
Received: from dsl027-180-168.sfo1.dsl.speakeasy.net ([216.27.180.168]:47031
	"EHLO sunset.davemloft.net") by vger.kernel.org with ESMTP
	id S932354AbWEDXEy (ORCPT <rfc822;netdev@vger.kernel.org>);
	Thu, 4 May 2006 19:04:54 -0400
To: alex@neterion.com
In-Reply-To: <445A84E7.1060906@neterion.com>
Sender: netdev-owner@vger.kernel.org
List-Id: netdev.vger.kernel.org

From: Alex Aizman <alex@neterion.com>
Date: Thu, 04 May 2006 15:49:11 -0700

> So, what are the requirements?

I will say it a 10th time, "we simply don't know yet."

Please be patient and let us design the net channel infrastructure
properly, then we can think clearly about how hardware might support
things.

Hardware folks are jumping the gun and it's very annoying and takes
precious time away from thinking about and working on the
implementation.