From: Antony Pavlov <antonynpavlov@gmail.com>
To: Holger Schurig <holgerschurig@gmail.com>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH 08/19] commands: move CMD_MIPS_CPUINFO to commands/Kconfig
Date: Tue, 13 May 2014 16:23:40 +0400 [thread overview]
Message-ID: <20140513162340.c2689ed174c2ad441edceab1@gmail.com> (raw)
In-Reply-To: <CAOpc7mHLsLJehMFkcFeJBGodKEJejiDxgwgWZE2V3-=37BbRHQ@mail.gmail.com>
On Tue, 13 May 2014 13:28:17 +0200
Holger Schurig <holgerschurig@gmail.com> wrote:
> Hi,
>
> i thought about having exactly one CONFIG_CMD_CPUINFO. No need for
> your steps 2. and 3., because both arch/arm/Makefile and
> arch/arm/Makefile could do "obj-$(CONFIG_CMD_CPUINFO) += cpuinfo.o",
> you cannot compile for ARM and MIPS at the same time anyway.
>
You right, steps 2 and 3 are redundunt. I have forgotten that you move Kconfig, but you don't touch cpuinfo.c.
> However, I decided against it. Because then I'd have to remove the
> example "cpuinfo" output from them the Kconfig help.
Can we move example 'cpuinfo' output to *.dox?
> Just that generally I'd like to have output example in the Kconfig, so
> that people see at "make xconfig" time if they want this command or
> not. I, for example, don't want "cpuinfo", I know which CPU is
> soldered into the board :-)
There are pin-to-pin compatible SoC revisions that use just the same package.
cpuinfo can help you to determinate the exact SoC version :)
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2014-05-13 12:13 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-13 8:28 [PATCH 00/19] commands rework patch series Holger Schurig
2014-05-13 8:28 ` [PATCH 01/19] commands: group 'help' output Holger Schurig
2014-05-13 13:48 ` Sascha Hauer
2014-05-13 14:07 ` Holger Schurig
2014-05-13 8:28 ` [PATCH 02/19] commands: harmonize in-barebox documentation Holger Schurig
2014-05-13 8:28 ` [PATCH 03/19] commands: harmonize in-barebox docs with Kconfig docs Holger Schurig
2014-05-13 8:28 ` [PATCH 04/19] commands: CMD_MEMORY -> COMPILE_MEMORY Holger Schurig
2014-05-13 8:28 ` [PATCH 05/19] commands: CMD_DIGEST -> COMPILE_DIGEST Holger Schurig
2014-05-13 8:28 ` [PATCH 06/19] commands: move CMD_ARM_CPUINFO to commands/Kconfig Holger Schurig
2014-05-13 8:28 ` [PATCH 07/19] commands: move CMD_ARM_MMUINFO " Holger Schurig
2014-05-13 8:28 ` [PATCH 08/19] commands: move CMD_MIPS_CPUINFO " Holger Schurig
2014-05-13 11:26 ` Antony Pavlov
2014-05-13 11:28 ` Holger Schurig
2014-05-13 12:23 ` Antony Pavlov [this message]
2014-05-13 12:43 ` Holger Schurig
2014-05-13 13:09 ` Juergen Borleis
2014-05-13 8:28 ` [PATCH 09/19] commands: move CMD_BOOT_ORDER " Holger Schurig
2014-05-13 8:28 ` [PATCH 10/19] commands: move CMD_AT91_BOOT_TEST " Holger Schurig
2014-05-13 8:28 ` [PATCH 11/19] commands: move CMD_AT91MUX " Holger Schurig
2014-05-13 8:28 ` [PATCH 12/19] commands: move CMD_AT91MIX " Holger Schurig
2014-05-13 8:28 ` [PATCH 13/19] commands: HUSH_GETOPT -> CMD_GETOPT Holger Schurig
2014-05-13 8:28 ` [PATCH 14/19] commands: let all network commands depend on NET Holger Schurig
2014-05-13 8:28 ` [PATCH 15/19] commands: introduce CMD_HOST Holger Schurig
2014-05-13 8:28 ` [PATCH 16/19] commands: NET_PING -> CMD_PING Holger Schurig
2014-05-13 8:28 ` [PATCH 17/19] commands: NET_DHCP -> CMD_DHCP Holger Schurig
2014-05-13 8:28 ` [PATCH 18/19] commands: move CMD_IFUP to commands/Kconfig Holger Schurig
2014-05-13 8:28 ` [PATCH 19/19] commands: move CONFIG_LONGHELP " Holger Schurig
2014-05-13 8:30 ` [PATCH 00/19] commands rework patch series Holger Schurig
2014-05-13 8:41 ` Sascha Hauer
2014-05-13 9:00 ` Holger Schurig
2014-05-13 13:46 ` Sascha Hauer
2014-05-14 7:02 ` Sascha Hauer
2014-05-14 13:55 ` Antony Pavlov
2014-05-15 8:09 ` Holger Schurig
2014-05-15 11:52 ` Sascha Hauer
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=20140513162340.c2689ed174c2ad441edceab1@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=holgerschurig@gmail.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