From: Randy Dunlap <rdunlap@infradead.org>
To: Rob Landley <rob@landley.net>,
linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Building sh4 without CONFIG_EXPERT.
Date: Fri, 16 May 2014 21:14:33 +0000 [thread overview]
Message-ID: <53767FB9.5040508@infradead.org> (raw)
In-Reply-To: <53700D71.1090201@landley.net>
On 05/11/2014 04:53 PM, Rob Landley wrote:
> I got sh4 to work under QEMU years ago as part of my aboriginal linux
> project, which builds the smallest Linux system capable of rebuilding
> itself natively from source code. (You can download and run the system
> images from http://landley.net/aboriginal/bin if you're curious.)
>
> One of the goals of Aboriginal is to make different architectures behave
> the same way, and one of the ways I do that is by having a basic kernel
> miniconfig file defining the config symbols common across platforms:
>
> http://landley.net/hg/aboriginal/file/1651/sources/baseconfig-linux
>
> And then append target-specific chunks, ala the LINUX_CONFIG sections
> from each of:
>
> http://landley.net/hg/aboriginal/file/1651/sources/targets
>
> The problem is, the sh4 target's target-specific chunk is an INSANE 45
> config symbols (armv5l needs 15 symbols, powerpc needs 16, i686 needs 7,
> mips needs 6...) and the reason for the verbosity is that sh4 forces on
> CONFIG_EXPERT.
>
> As far as I can tell, the only reason sh4 is forcing on CONFIG_EXPERT is
> to get CONFIG_PATA_PLATFORM. The patch to make sh4 _not_ force on
> CONFIG_EXPERT is just:
>
> diff --git a/arch/sh/Kconfig b/arch/sh/Kconfig
> index 834b67c..7d0d44d 100644
> --- a/arch/sh/Kconfig
> +++ b/arch/sh/Kconfig
> @@ -1,7 +1,7 @@
> config SUPERH
> def_bool y
> select ARCH_MIGHT_HAVE_PC_PARPORT
> - select EXPERT
> + select HAVE_PATA_PLATFORM
> select CLKDEV_LOOKUP
> select HAVE_IDE if HAS_IOPORT_MAP
> select HAVE_MEMBLOCK
Since PATA_PLATFORM is:
config PATA_PLATFORM
tristate "Generic platform device PATA support"
depends on EXPERT || PPC || HAVE_PATA_PLATFORM
then any of EXPERT, PPC, or HAVE_PATA_PLATFORM should be sufficient.
and using HAVE_PATA_PLATFORM is more direct and obvious.
Acked-by: Randy Dunlap <rdunlap@infradead.org>
> Which swaps EXPERT for HAVE_PATA_PLATFORM, so I can still provide a hard
> drive qemu can see as /dev/sda. The result builds, boots, and works for
> me in very basic smoke testing, and lets me get my sh4-specific config
> symbol set down to 27 symbols.
>
> (P.S. I have no idea why hitting ctrl-C kills the _emulator_ rather than
> passing it along to the emulated system. The other qemu targets don't do
> that...)
>
> Rob
>
> P.S. I'm using linux 3.14, qemu 2.0, and the sh4 cross compiler
> toolchain from the URL at the top of the post. I can be more explicit if
> you care...
--
~Randy
next prev parent reply other threads:[~2014-05-16 21:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-11 23:53 Building sh4 without CONFIG_EXPERT Rob Landley
2014-05-16 21:14 ` Randy Dunlap [this message]
2015-01-05 9:58 ` Geert Uytterhoeven
2015-01-12 23:00 ` [PATCH] Build superh " Rob Landley
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=53767FB9.5040508@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=rob@landley.net \
/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;
as well as URLs for NNTP newsgroup(s).