public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: "Taru Varshney" <taru.varshney@intervideo.com>
To: linux-omap-open-source@linux.omap.com
Subject: Need help to understand a #pragma statment.
Date: Thu, 3 Aug 2006 19:09:07 +0530	[thread overview]
Message-ID: <20060803125117.EB139CC02C@pf2.intervideo.com> (raw)
In-Reply-To: <20060803130336.GA18147@atomide.com>

 

Hi all,
I'm trying to load bootloader on DM320's Flash memory. Flash writer is
working fine. But it's somebody else's code. I'm not able to understand what
the folowing line in the flash Writer code is doing:

#pragma DATA_SECTION (ucBOOT320Code,".bin"). 

Can anybody help me to understand the above line ??

Thanks in Advance,
Taru
  

  reply	other threads:[~2006-08-03 13:39 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-01 16:44 Pending July patches Dirk Behme
2006-08-03 11:17 ` Tony Lindgren
2006-08-03 12:08   ` Komal Shah
2006-08-03 13:03     ` GPMC timings for smc91x on 24xx (WAS: Pending July patches) Tony Lindgren
2006-08-03 13:39       ` Taru Varshney [this message]
2006-08-04 11:05     ` Pending July patches Tony Lindgren
2006-08-04 13:20       ` [PATCH] ARM: OMAP: Fix lcd_ams_delta to use new PWL defines Jonathan McDowell
2006-08-07 15:22         ` Tony Lindgren
2006-08-08  8:33           ` mcbsp Arnold
2006-08-08 21:33           ` 2.6.18-rc4 / generic irq etc Jonathan McDowell
2006-08-09  7:26             ` Tony Lindgren
2006-08-04 14:40       ` Pending July patches lamikr
2006-08-07 15:23         ` Tony Lindgren
2006-08-07 23:56           ` lamikr
2006-08-08  1:30             ` andrzej zaborowski
2006-08-10  4:41               ` andrzej zaborowski
2006-08-10  7:32                 ` Tony Lindgren
2006-08-10  8:07                   ` andrzej zaborowski
2006-08-10 10:45                     ` Tony Lindgren

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=20060803125117.EB139CC02C@pf2.intervideo.com \
    --to=taru.varshney@intervideo.com \
    --cc=linux-omap-open-source@linux.omap.com \
    /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