public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Troy Kisky <troy.kisky@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] ARM: Update mach-types
Date: Thu, 01 Mar 2012 15:50:07 -0700	[thread overview]
Message-ID: <4F4FFD1F.4080406@boundarydevices.com> (raw)
In-Reply-To: <4F4FF02D.1020804@aribaud.net>

On 3/1/2012 2:54 PM, Albert ARIBAUD wrote:
> Hi Troy,
>
> Le 01/03/2012 22:13, Troy Kisky a ?crit :
>
>> diff --git a/include/configs/ea20.h b/include/configs/ea20.h
>> index b4610d9..da49ae8 100644
>> --- a/include/configs/ea20.h
>> +++ b/include/configs/ea20.h
>> @@ -24,6 +24,18 @@
>>   #define __CONFIG_H
>>
>>   /*
>> + * FIXME: This belongs in mach-types.h.  However, we only pull 
>> mach-types
>> + * from Linus' kernel.org tree.
>> + */
>> +#include<asm/mach-types.h>
>> +#ifdef MACH_TYPE_EA20
>> +#error "MACH_TYPE_EA20 has been defined properly, please remove this."
>> +#else
>> +#define MACH_TYPE_EA20        3002
>> +#endif
>> +
>> +
>> +/*
>
> Sorry if I am being pedantic here, but the "FIXME" comment actually 
> belongs *below* the #include line, not above. Ditto for others.

I put it above because when it is moved to mach-types.h, the include 
should be deleted as well. That is part of the "FIXME."


>
>> diff --git a/include/configs/seaboard.h b/include/configs/seaboard.h
>> index 261f952..8589b1d 100644
>> --- a/include/configs/seaboard.h
>> +++ b/include/configs/seaboard.h
>> @@ -45,6 +45,13 @@
>>
>>   #define CONFIG_BOARD_EARLY_INIT_F
>>
>> +/*
>> + * FIXME: This belongs in mach-types.h.  However, we only pull 
>> mach-types
>> + * from Linus' kernel.org tree.
>> + */
>> +#define machine_is_ventana()    (0)
>
> Not sure I understand why we have a "machine_ix_xxx()" here. Could you 
> explain?
>
> Amicalement,

Because board/nvidia/seaboard/seaboard.c uses machine_is_ventana but 
that machine is no longer
in mach-types.

Thanks
Troy

  reply	other threads:[~2012-03-01 22:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01 21:13 [U-Boot] [PATCH 1/3] gplugd: use CONFIG_MACH_TYPE instead of MACH_TYPE_SHEEVAD Troy Kisky
2012-03-01 21:13 ` [U-Boot] [PATCH 2/3] ventana: define CONFIG_MACH_VENTANA Troy Kisky
2012-03-01 21:30   ` Stephen Warren
     [not found]     ` <4F4FFE7D.7020809@boundarydevices.com>
2012-03-02  1:44       ` Stephen Warren
2012-03-01 21:13 ` [U-Boot] [PATCH 3/3] ARM: Update mach-types Troy Kisky
2012-03-01 21:32   ` Stephen Warren
2012-03-01 21:54   ` Albert ARIBAUD
2012-03-01 22:50     ` Troy Kisky [this message]
2012-03-02  7:00       ` Wolfgang Denk
2012-03-02 17:45         ` Stephen Warren
2012-03-02 19:37           ` Troy Kisky
2012-03-02 20:08             ` Stephen Warren
2012-03-02 21:07       ` Troy Kisky
2012-03-03 10:15 ` [U-Boot] [PATCH 1/3] gplugd: use CONFIG_MACH_TYPE instead of MACH_TYPE_SHEEVAD Stefano Babic

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=4F4FFD1F.4080406@boundarydevices.com \
    --to=troy.kisky@boundarydevices.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox