From mboxrd@z Thu Jan  1 00:00:00 1970
From: Simon Glass <sjg@chromium.org>
Date: Tue, 3 Mar 2015 16:14:15 -0700
Subject: [U-Boot] [RFC PATCH v4 0/23] Add Driver Model support to
	network stack
In-Reply-To: <CANr=Z=bd7rpHQaQPeUKVowqmWXM7VXmHSmhQFUjieQN7=2puEg@mail.gmail.com>
References: <1423618233-11397-1-git-send-email-joe.hershberger@ni.com>
 <1424822552-4366-1-git-send-email-joe.hershberger@ni.com>
 <CAPnjgZ3=Y17BUSM7_ZJSmFUYJD8RdNnE1cFrqjji4EiVhr_9ug@mail.gmail.com>
 <CANr=Z=bd7rpHQaQPeUKVowqmWXM7VXmHSmhQFUjieQN7=2puEg@mail.gmail.com>
Message-ID: <CAPnjgZ1gBsGXOZAoBaf4pLGpXud3s9CGDRG7419zM=baosRwmQ@mail.gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hi Joe,

On 3 March 2015 at 15:29, Joe Hershberger <joe.hershberger@gmail.com> wrote:
> On Sun, Mar 1, 2015 at 10:13 AM, Simon Glass <sjg@chromium.org> wrote:
>
> [snip]
>
>> - I think the recv() method should change before long. The
>> NetReceive() call should be made from the uclass since it is common to
>> all drivers. Then the recv() method can return a packet if it finds
>> one, but not submit it for processing
>
> I looked into doing this and I think it may be more of a step backward.
> Currently devices can directly hand their DMA buffers to the network stack.
> With this change, most drivers would be forced to memcpy each packet into
> the supplied buffer.

I don't see why. The uclass can request the address and length of the buffer.

int (*recv)(char **buffp, int **lenp);

>
> I do plan to rename the function, though.

OK.

Regards,
Simon