All of lore.kernel.org
 help / color / mirror / Atom feed
From: "colorant" <colorant@163.com>
To: David Brownell <david-b@pacbell.net>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Question About __REG32 marco
Date: Wed, 21 Nov 2007 13:18:36 +0800	[thread overview]
Message-ID: <00c601c82bfd$f7cce620$16110a0a@LongCheer.net> (raw)
In-Reply-To: 200711201646.42939.david-b@pacbell.net

[-- Attachment #1: Type: text/plain, Size: 782 bytes --]

Hi Dave


> On Tuesday 20 November 2007, colorant wrote:
>> since the index is just 1K, the following definition :
>> 
>> typedef struct { volatile u32 offset[4096]; } __regbase32;
>> 
>> shouldn't be:
>> 
>> typedef struct { volatile u32 offset[1024]; } __regbase32; ?
> 
> Would changing that make a difference in the generated code,
> or turn up any source code errors?
> 
> I'm not sure changing that would matter at all.  And in any
> case, those multiboot patches show the downside of this
> particular idiom... someone may need to take another look
> at the code generation issue, and maybe file some bugs/rfes
> against current GCC versions.
> 
> - Dave
> 

No, the generated code is the same , and I can run up the kernel without problem.

Raymond

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



      reply	other threads:[~2007-11-21  5:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-20 10:39 Question About __REG32 marco colorant
2007-11-20 14:54 ` Woodruff, Richard
2007-11-20 21:26 ` David Brownell
2007-11-21  0:40   ` colorant
2007-11-21  0:46     ` David Brownell
2007-11-21  5:18       ` colorant [this message]

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='00c601c82bfd$f7cce620$16110a0a@LongCheer.net' \
    --to=colorant@163.com \
    --cc=david-b@pacbell.net \
    --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 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.