From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] dfu: make data buffer size configurable
Date: Sun, 9 Jun 2013 22:01:51 +0200 [thread overview]
Message-ID: <201306092201.51588.marex@denx.de> (raw)
In-Reply-To: <7763C113-3609-44AE-A360-C151816E0DBB@antoniou-consulting.com>
Dear Pantelis Antoniou,
> Heiko,
>
> On Jun 4, 2013, at 1:31 PM, Heiko Schocher wrote:
> > Hello Pantelis,
> >
> > Am 04.06.2013 12:08, schrieb Pantelis Antoniou:
> >> Hi Heiko,
> >>
> >> Just thinking out loud here. Can we have an extra option that
> >> allocates the buffer dynamically based on an env variable?
> >
> > Hmm.. also a possibility... I have here no preferences ...
> >
> > Name: "dfu_data_buf_size" if not defined, or env invalid, use
> > default CONFIG_SYS_DFU_DATA_BUF_SIZE size?
> >
> > But this can be done in a second step, right?
>
> Yes, only as a second step please.
Why not do it like that right away?
btw. sorry, I'm playing dead beetle until next week :-(
Best regards,
Marek Vasut
next prev parent reply other threads:[~2013-06-09 20:01 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-04 9:22 [U-Boot] dfu: make data buffer size configurable Heiko Schocher
2013-06-04 10:08 ` Pantelis Antoniou
2013-06-04 10:31 ` Heiko Schocher
2013-06-04 10:31 ` Pantelis Antoniou
2013-06-09 20:01 ` Marek Vasut [this message]
2013-06-10 4:28 ` Heiko Schocher
2013-06-10 5:48 ` Lukasz Majewski
2013-06-10 7:05 ` Wolfgang Denk
2013-06-10 15:51 ` Tom Rini
2013-06-12 8:36 ` Marek Vasut
2013-06-12 8:49 ` Heiko Schocher
2013-06-04 10:18 ` Lukasz Majewski
2013-06-04 20:04 ` Tom Rini
2013-06-05 4:53 ` Heiko Schocher
2013-06-05 12:43 ` Tom Rini
2013-06-05 14:04 ` Heiko Schocher
2013-06-06 15:55 ` Tom Rini
2013-06-07 6:05 ` Heiko Schocher
2013-06-07 7:28 ` Wolfgang Denk
2013-06-12 4:05 ` [U-Boot] [PATCH v2] " Heiko Schocher
2013-06-12 16:16 ` Tom Rini
2013-06-19 12:25 ` Marek Vasut
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=201306092201.51588.marex@denx.de \
--to=marex@denx.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox