From: macpaul at andestech.com <macpaul@andestech.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v7 01/10] nds32: add header files support for nds32
Date: Fri, 8 Apr 2011 15:21:13 +0800 [thread overview]
Message-ID: <50FD90C65C53FB45BADEEBCD84FF07F202F4875B@ATCPCS06.andestech.com> (raw)
Hi Wolfgang,
> This also triggers an erro-r from checkpatch, and indeed this is a
> strange define.
>
> > +#define R0 uregs[1] /* R0 */
> > +#define R1 uregs[2]
> > +#define R2 uregs[3]
> > +#define R3 uregs[4]
>
> NAK. Please use a C struct instead.
After discussed with the colledgue responsor for GDB and ptrace utils, we will fix this in Linux kernel later.
Ans, I'll fix it in the next patch v8.
>
> ...
> > diff --git a/arch/nds32/include/asm/u-boot.h
> b/arch/nds32/include/asm/u-boot.h
> > new file mode 100644
> > index 0000000..fafe4e4
> > --- /dev/null
> > +++ b/arch/nds32/include/asm/u-boot.h
> > @@ -0,0 +1,63 @@
> > +/*
> > + * (C) Copyright 2002
> > + * Sysgo Real-Time Solutions, GmbH <www.elinos.com>
> > + * Marius Groeger <mgroeger@sysgo.de>
> > + *
> > + * Copyright (C) 2011 Andes Technology Corporation
> > + * Copyright (C) 2010 Shawn Lin (nobuhiro at andestech.com)
> > + * Copyright (C) 2011 Macpaul Lin (macpaul at andestech.com)
> ...
> > +#ifndef _U_BOOT_H_
> > +#define _U_BOOT_H_ 1
> > +
> > +#include <environment.h>
> > +
> > +typedef struct bd_info {
> > + int bi_baudrate; /* serial console baudrate */
> > + unsigned long bi_ip_addr; /* IP Address */
> > + unsigned char bi_enetaddr[6]; /* Ethernet adress */
> > +
> > + env_t *bi_env;
> > + unsigned long bi_arch_number; /* unique id for this board */
> > + unsigned long bi_boot_params; /* where this board
> expects params */
> > +
> > + unsigned long bi_memstart; /* start of DRAM memory */
> > + unsigned long bi_memsize; /* size of DRAM memory
> in bytes */
> > + unsigned long bi_flashstart; /* start of FLASH memory */
> > + unsigned long bi_flashsize; /* size of FLASH memory */
> > + unsigned long bi_flashoffset; /* reserved area for
> startup monitor */
> > +
> > + struct /* RAM configuration */
> > + {
> > + unsigned long start;
> > + unsigned long size;
> > + } bi_dram[CONFIG_NR_DRAM_BANKS];
> > +} bd_t;
>
> I wonder which part of this file would be (C) by any of the folks
> listed above?
>
The typedef struct bd_info comes from arch/i386/include/asm/u-boot.h
and arch/arm/include/asm/u-boot.h.
If you grep the author "Marius Groeger <mgroeger@sysgo.de>" then you can find the
the 2 files were in the grep result which was originally referenced.
Hence we put (C) listed above because we have referenced those 2 files.
If you have any suggestion, please let me know.
Best regards,
Macpaul Lin
next reply other threads:[~2011-04-08 7:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-08 7:21 macpaul at andestech.com [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-04-07 12:45 [U-Boot] [PATCH v7 01/10] nds32: add header files support for nds32 Macpaul Lin
2011-04-07 14:55 ` Wolfgang Denk
[not found] ` <BANLkTimhCuOcvMmFrSJGHxYRHyKFXJTc9g@mail.gmail.com>
2011-04-07 15:32 ` Macpaul Lin
2011-04-07 17:00 ` Wolfgang Denk
2011-04-08 7:58 ` Macpaul Lin
2011-04-11 2:05 ` Macpaul Lin
2011-04-29 23:09 ` Wolfgang Denk
2011-04-30 4:09 ` Chih-Min Chao
2011-05-02 9:27 ` Macpaul Lin
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=50FD90C65C53FB45BADEEBCD84FF07F202F4875B@ATCPCS06.andestech.com \
--to=macpaul@andestech.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.