From: m.szyprowski@samsung.com (Marek Szyprowski)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v8 0/2] ommu/exynos: Add IOMMU/System MMU driver for Samsung Exynos
Date: Tue, 03 Jan 2012 10:37:29 +0100 [thread overview]
Message-ID: <00dc01ccc9fb$4fcb7590$ef6260b0$%szyprowski@samsung.com> (raw)
In-Reply-To: <20120102134229.GZ29877@amd.com>
Hello,
On Monday, January 02, 2012 2:42 PM Joerg Roedel wrote:
> On Thu, Dec 29, 2011 at 09:24:18PM +0900, KyongHo Cho wrote:
> > Changes since v7:
> > - Rebased with the recent commits of the following git branches
> > * git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git/next
> > * git.kernel.org/pub/scm/linux/kernel/git/kgene/linux-samsung.git/for-next
> > - Changed magic numbers into macros
> > - Setting owner of a System MMU in 'iommu' field of dev_archdata
> > - Verbose message in the default fault handler
> > - Some bug fixes.
>
> I still get
>
> LD .tmp_vmlinux1
> /data/cross/gcc-4.6.0-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-ld: no
> machine record defined
> /data/cross/gcc-4.6.0-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-ld: no
> machine record defined
> /data/cross/gcc-4.6.0-nolibc/arm-unknown-linux-gnueabi/bin/arm-unknown-linux-gnueabi-ld: no
> machine record defined
> make[1]: *** [.tmp_vmlinux1] Error 1
>
> when trying to compile ARM/Exynos with 3.2-rc7. Am I doing something
> wrong or is this not expected to work?
Yes, there is something a bit wrong with your kernel configuration. You get this error if
there is no board selected to be compiled-in. Please go to kernel configuration and select
"System Type -> SAMSUNG EXYNOS SoCs Suppport". Then select some hardware board to be
compiled in, for example SMDKV310, SMDKC210 and "Mobile NURI board".
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
next prev parent reply other threads:[~2012-01-03 9:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 12:24 [PATCH v8 0/2] ommu/exynos: Add IOMMU/System MMU driver for Samsung Exynos KyongHo Cho
2012-01-02 13:42 ` Joerg Roedel
2012-01-02 15:21 ` KyongHo Cho
2012-01-02 15:58 ` Joerg Roedel
2012-01-03 1:02 ` Kukjin Kim
2012-01-03 8:15 ` KyongHo Cho
2012-01-03 9:55 ` Russell King - ARM Linux
2012-01-04 15:01 ` Joerg Roedel
2012-01-04 21:26 ` Russell King - ARM Linux
2012-01-05 11:47 ` Joerg Roedel
2012-01-09 0:32 ` KyongHo Cho
2012-01-02 16:35 ` Joerg Roedel
2012-01-03 9:37 ` Marek Szyprowski [this message]
2012-01-03 13:10 ` 'Joerg Roedel'
2012-02-24 13:45 ` Marek Szyprowski
2012-02-24 16:08 ` KyongHo Cho
2012-02-27 15:51 ` Marek Szyprowski
2012-02-27 16:04 ` KyongHo Cho
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='00dc01ccc9fb$4fcb7590$ef6260b0$%szyprowski@samsung.com' \
--to=m.szyprowski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).