All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Benard <eric@eukrea.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 1/2] dropbear: add 0.53.1
Date: Mon, 07 Mar 2011 11:12:01 +0100	[thread overview]
Message-ID: <4D74AF71.4070105@eukrea.com> (raw)
In-Reply-To: <1299491850.2132.12.camel@phil-desktop>

Hi Phil,

On 07/03/2011 10:57, Phil Blundell wrote:
> On Mon, 2011-03-07 at 10:50 +0100, Eric Benard wrote:
>> Hi Khem,
>>
>> On 06/03/2011 00:08, Khem Raj wrote:
>>> On Sat, Mar 5, 2011 at 1:30 PM, Eric Bénard<eric@eukrea.com>   wrote:
>>>> * 0.53.1 brings some improvements over 0.52 which was released
>>>> more than 2 years ago. For more details, check the changelog here :
>>>> http://matt.ucc.asn.au/dropbear/CHANGES
>>>> * Please note that DROPBEAR_SMALL_CODEis now disabled which may
>>>> increase the size of the binaries.
>>>
>>> can you compare the sizes of .52 and .53.1 so we know how much it will be
>>>>
>> for an armv5 target :
>> 0.53.1 : 228112
>> 0.53.1 + DROPBEAR_SMALL_CODE : 178960
>> 0.52 : 183008
>
> Looks like DROPBEAR_SMALL_CODE is still worth having then.  Why was it
> disabled?
>
the changelog doesn't say it but the comment in option.h says :
/* Set this if you want to use the DROPBEAR_SMALL_CODE option. This can save
several kB in binary size, however will make the symmetrical ciphers (AES, DES
etc) slower (perhaps by 50%). Recommended for most small systems. */

so maybe they prefered to get performance by default instead of saving 50kB.

We can keep this option by adding this to the recipe :
+do_configure_prepend() {
+       echo "#define DROPBEAR_SMALL_CODE" >>${S}/options.h
+}
+

Eric



  reply	other threads:[~2011-03-07 10:13 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-05 21:30 [PATCH 1/2] dropbear: add 0.53.1 Eric Bénard
2011-03-05 21:30 ` [PATCH 2/2] qt4: add 4.7.2 Eric Bénard
2011-04-27 17:37   ` Otavio Salvador
2011-03-05 23:08 ` [PATCH 1/2] dropbear: add 0.53.1 Khem Raj
2011-03-07  9:50   ` Eric Benard
2011-03-07  9:57     ` Phil Blundell
2011-03-07 10:12       ` Eric Benard [this message]
2011-03-07 11:31         ` Phil Blundell
2011-03-08  0:33           ` [PATCH v2] " Eric Bénard
2011-03-08  1:26             ` Khem Raj

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=4D74AF71.4070105@eukrea.com \
    --to=eric@eukrea.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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.