From: Artem Bityutskiy <dedekind1@gmail.com>
To: Bastian Hecht <hechtb@googlemail.com>
Cc: Magnus Damm <magnus.damm@gmail.com>,
Simon Horman <horms@verge.net.au>,
linux-mtd@lists.infradead.org,
Laurent Pichart <laurent.pinchart@ideasonboard.com>,
linux-sh@vger.kernel.org
Subject: Re: [PATCH v2 0/7] SH Mobile sh_flctl driver brush up
Date: Fri, 09 Mar 2012 12:11:52 +0000 [thread overview]
Message-ID: <1331295112.29445.14.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <CABYn4sydNW_S=mivCOCd5RoxeW0T+Q-encFRUps2xYU0_H2GHg@mail.gmail.com>
On Tue, 2012-02-14 at 11:58 +0100, Bastian Hecht wrote:
> Hello Artem,
>
> 2012/2/14 Simon Horman <horms@verge.net.au>:
> > On Mon, Feb 13, 2012 at 03:41:55PM +0200, Artem Bityutskiy wrote:
> >> On Sat, 2012-02-11 at 12:44 +0100, Bastian Hecht wrote:
> >> > This patch series brushs up the sh_flctl.c a bit to make it work with
> >> > the mackerel board. The hardware has changed and this needed to be
> >> > reflected in the NAND host driver.
> >> > On the road some minor enhancements have been incorporated.
> >>
> >> I cannot even compile-test this patch because I get the following error:
> >>
> >>
> >> sh4-linux-gcc: error: command line option '-m4-nofpu' is not supported
> >> by this configuration
> >>
> >>
> >> with the cross-compiler downloaded from here:
> >>
> >> http://kernel.org/pub/tools/crosstool/files/bin/x86_64/4.6.0/x86_64-gcc-4.6.0-nolibc_sh4-linux.tar.bz2
> >>
> >> Could you please describe how could I compile-test it?
> >
> > You may find it easier to build a kernel for mackerel using
> > arch arm and defconfig_mackerel.
> >
> > Personally I have had good experience using Code Sourcery (now part of
> > Mentor Graphics?) G++ lite to compile both arm and sh kernels.
> >
> >
>
> I as well use a Code Sourcery toolchain. arm-none-linux-gnueabi-gcc -v
> states "gcc version 4.4.1 (Sourcery G++ Lite 2010q1-202)". It took me
> quite a bit to find a link to the toolchain as these gpl toolchains
> from Code Sourcery almost seem to be hidden. But here it is if you
> want to give it a try:
I am a bit confused. We have the following in drivers/mtd/nand/Kconfig
config MTD_NAND_SH_FLCTL
tristate "Support for NAND on Renesas SuperH FLCTL"
depends on SUPERH || ARCH_SHMOBILE
help
Several Renesas SuperH CPU has FLCTL. This option enables support
for NAND Flash using FLCTL.
SUPERH and ARCH_SHMOBILE are SH platforms - how can I compile-test your
patch-set with an arm cross-compiler?
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2012-03-09 12:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-11 11:44 [PATCH v2 0/7] SH Mobile sh_flctl driver brush up Bastian Hecht
2012-02-11 11:44 ` [PATCH v2 1/7] mtd: sh_flctl: Expand FLCMNCR register bit field Bastian Hecht
2012-02-18 2:22 ` Laurent Pinchart
2012-02-19 10:34 ` Bastian Hecht
2012-02-11 11:45 ` [PATCH v2 2/7] mtd: sh_flctl: Reorder empty_fifo() calls Bastian Hecht
2012-02-18 2:21 ` Laurent Pinchart
2012-02-11 11:45 ` [PATCH v2 3/7] mtd: sh_flctl: Expand the READID command to 8 bytes Bastian Hecht
2012-02-18 2:20 ` Laurent Pinchart
2012-02-19 10:46 ` Bastian Hecht
2012-02-11 11:45 ` [PATCH v2 4/7] mtd: sh_flctl: Implement NAND_CMD_RNDOUT command Bastian Hecht
2012-02-11 11:45 ` [PATCH v2 5/7] mtd: sh_flctl: Use cached register value for FLCMNCR Bastian Hecht
2012-02-18 2:18 ` Laurent Pinchart
2012-02-19 10:48 ` Bastian Hecht
2012-02-11 11:45 ` [PATCH v2 6/7] mtd: sh_flctl: Add FLHOLDCR register Bastian Hecht
2012-02-18 0:25 ` Laurent Pinchart
2012-02-19 11:04 ` Bastian Hecht
2012-02-11 11:45 ` [PATCH v2 7/7] ARM: mach-shmobile: mackerel: Add the flash controller flctl Bastian Hecht
2012-02-13 13:41 ` [PATCH v2 0/7] SH Mobile sh_flctl driver brush up Artem Bityutskiy
2012-02-14 3:38 ` Simon Horman
2012-02-14 10:58 ` Bastian Hecht
2012-03-09 12:11 ` Artem Bityutskiy [this message]
2012-03-09 12:14 ` Laurent Pinchart
2012-03-09 12:37 ` Artem Bityutskiy
2012-03-09 12:42 ` Laurent Pinchart
2012-03-09 13:22 ` Magnus Damm
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=1331295112.29445.14.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=hechtb@googlemail.com \
--cc=horms@verge.net.au \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@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;
as well as URLs for NNTP newsgroup(s).