From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] Driver model Ethernet issue
Date: Thu, 2 Apr 2015 09:50:30 +0200 [thread overview]
Message-ID: <20150402095030.4aa47cfb@lilith> (raw)
In-Reply-To: <CAPnjgZ0bymyUxsOb8p+WM=thcN2QZS1xSXoEc0R9OKuoKVVLgA@mail.gmail.com>
Hello Simon,
On Mon, 30 Mar 2015 12:03:41 -0600, Simon Glass <sjg@chromium.org>
wrote:
> Also you can argue that buffer management is a reasonable thing to
> provide a method for. Using a buffer to receive a packet, sending that
> packet for processing, and retiring the buffer are all conceptually
> separate things. We could even consider (in the future!) supporting a
> buffer ring in the uclass since all of the drivers I have looked at
> have one.
Just in case: remember that some drivers use SRAM-based buffers while
others use DDR-based buffers. Buffer management should support either
use case. Also, there's more than just buffers; descriptors might be
needed too -- whether they should be generalized or not, I have no
clear idea, though.
Amicalement,
--
Albert.
next prev parent reply other threads:[~2015-04-02 7:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-26 3:10 [U-Boot] Driver model Ethernet issue Simon Glass
[not found] ` <CANr=Z=aogNzMmgw1nD+W_L8P0L-ev6q0H4H_B01qWLMZfzNeGA@mail.gmail.com>
[not found] ` <CANr=Z=asoa5Y2PoMLkV_+pACeT-u6uE9ZPbjLuCWZFcApdYccg@mail.gmail.com>
2015-03-30 18:03 ` Simon Glass
2015-03-30 20:44 ` [U-Boot] [PATCH] dm: eth: Provide a way for drivers to manage packet buffers Joe Hershberger
2015-04-01 3:32 ` Simon Glass
2015-04-01 16:03 ` Joe Hershberger
2015-04-03 23:33 ` Simon Glass
2015-04-04 1:09 ` [U-Boot] [PATCH v2] " Joe Hershberger
2015-04-05 18:31 ` Simon Glass
2015-04-07 18:39 ` Simon Glass
2015-04-02 7:50 ` Albert ARIBAUD [this message]
2015-04-02 14:58 ` [U-Boot] Driver model Ethernet issue Simon Glass
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=20150402095030.4aa47cfb@lilith \
--to=albert.u.boot@aribaud.net \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.