All of lore.kernel.org
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] [PATCH][FDT][UPDATE] Add common memory fixup function
Date: Wed, 28 Nov 2007 17:04:26 -0600	[thread overview]
Message-ID: <474DF3FA.1020809@freescale.com> (raw)
In-Reply-To: <526292C8-CD61-48E1-9A3B-A398E21DBB87@kernel.crashing.org>

Kumar Gala wrote:
> On Nov 28, 2007, at 4:38 PM, Scott Wood wrote:
>> Kumar Gala wrote:
>>> I don't see how to use them w/o going through an additional memcpy.
>>> If you can provide a better solution I'm all for it.  But I don't see 
>>> any reason to hold up the patch at this point.
>>
>> union {
>>     uint8_t tmp[8];
>>     uint64_t mem64;
>>     uint32_t mem32;
>> }
>>
>> int len;
>>
>> if (addrcell && *addrcell == 2) {
>>     mem64 = cpu_to_fdt64(memsize);
>>     len = 8;
>> } else {
>>     mem32 = cpu_to_fdt32(memsize);
>>     len = 4;
>> }
> 
> This gets more complicated with finishing off the rest of temp since you 
> have to use len to figure out an index.

OK, so make mem64/mem32 arrays. :-P

> I'm keeping the code as is since its the simplest version.

Fine, if you don't mind making people's eyes bleed...

Maybe a generic function that takes a buffer pointer, a uint64_t, and a 
numcells?  This is hardly going to be the only place that needs to write 
out a quantity that might be one or two cells.

-Scott

  reply	other threads:[~2007-11-28 23:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-28 21:52 [U-Boot-Users] [PATCH][FDT][UPDATE] Add common memory fixup function Kumar Gala
2007-11-28 22:16 ` Scott Wood
2007-11-28 22:35   ` Kumar Gala
2007-11-28 22:38     ` Scott Wood
2007-11-28 22:48       ` Kumar Gala
2007-11-28 23:04         ` Scott Wood [this message]
2007-11-28 23:12           ` Kumar Gala

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=474DF3FA.1020809@freescale.com \
    --to=scottwood@freescale.com \
    --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.