[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <51432B72.20408@hhi.fraunhofer.de>
Date: Fri, 15 Mar 2013 15:08:50 +0100
From: Thomas Martitz <thomas.martitz@....fraunhofer.de>
To: richard -rw- weinberger <richard.weinberger@...il.com>
CC: "Eric W. Biederman" <ebiederm@...ssion.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"davem@...emloft.net" <davem@...emloft.net>,
"edumazet@...gle.com" <edumazet@...gle.com>,
"herbert@...dor.apana.org.au" <herbert@...dor.apana.org.au>
Subject: Re: Trying to implement secondary loopback
Am 15.03.2013 14:56, schrieb richard -rw- weinberger:
> On Fri, Mar 15, 2013 at 2:49 PM, Thomas Martitz
> <thomas.martitz@....fraunhofer.de> wrote:
>> I want the loopback during development of the NIC hardware. Once the NIC is
>> done I drop the loopback and the card will be used for real networking.
>> Thus, I want the loopback to a) test my driver, and b) test the hardware
>> (for each milestone) as I'm implementing it.
>
> Sorry, I still don't get why you need a loopback device for that.
>
What's wrong with loopback? It's the simplest method to get basic
bidirectional data transfer going.
Can you suggest an alternative approach?
Best regards.
-----
visit us at
OFC 2013 / March 19-21 / Anaheim Convention Center, CA, USA / booth 11807
NABSHOW 2013 / April 8-11 / Las Vegas Convention Center, Nevada, USA / booth C7843
www.hhi.fraunhofer.de/events
--
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
Powered by blists - more mailing lists