From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Early malloc() summary
Date: Thu, 16 Aug 2012 16:50:27 +0200 [thread overview]
Message-ID: <201208161650.27985.marex@denx.de> (raw)
In-Reply-To: <502CE008.8030808@gmail.com>
Dear Graeme Russ,
[...]
> >> 2) We can pass a pointer to a driver_core struct (or whatever struct it
> >>
> >> is that holds the 'reloc' helper function pointer). We can't pick up
> >> misuse at compile time, but dm_malloc() can print a meaningful
> >> message if it is called pre-relocation with no relocation function.
> >> (We should add a flag to indicate that no relocation helper is
> >> required which may be the case for very simple drivers)
> >
> > Yes, but it would prevent using dm_malloc(size_t size, driver *drv)
> > for one-time buffers inside helper functions - strdup() for instance,
>
> Hmm, I hadn't thought of that
So, we're back to square 1 ?
[...]
Best regards,
Marek Vasut
next prev parent reply other threads:[~2012-08-16 14:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 0:55 [U-Boot] Early malloc() summary Graeme Russ
2012-08-09 12:48 ` Wolfgang Denk
2012-08-11 23:16 ` Marek Vasut
2012-08-14 8:11 ` Tomas Hlavacek
2012-08-14 12:37 ` Marek Vasut
2012-08-14 13:08 ` Albert ARIBAUD
2012-08-14 14:40 ` Marek Vasut
2012-08-14 13:54 ` Graeme Russ
2012-08-14 14:00 ` Marek Vasut
2012-08-16 11:25 ` Graeme Russ
2012-08-16 14:52 ` Marek Vasut
2012-08-16 23:05 ` Graeme Russ
2012-08-14 23:56 ` Marek Vasut
2012-08-16 11:39 ` Graeme Russ
2012-08-15 12:00 ` Tomas Hlavacek
2012-08-16 11:56 ` Graeme Russ
2012-08-16 14:50 ` Marek Vasut [this message]
2012-08-16 23:03 ` Graeme Russ
2012-08-16 23:32 ` Marek Vasut
2012-08-16 23:50 ` Graeme Russ
2012-08-17 0:34 ` Marek Vasut
2012-08-17 1:15 ` Graeme Russ
2012-08-19 13:21 ` Tomas Hlavacek
2012-08-19 23:47 ` Graeme Russ
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=201208161650.27985.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