RE: [PATCH v8 0/2] ommu/exynos: Add IOMMU/System MMU driver forSamsung Exynos
From: Kukjin Kim
Date: Mon Jan 02 2012 - 20:03:02 EST
Joerg Roedel wrote:
>
> On Tue, Jan 03, 2012 at 12:21:30AM +0900, KyongHo Cho wrote:
> > > 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?
> > >
> > Do you?
> > Ok. I will check my configuration with linux-next git.
>
> Compiling my exynos-config with linux-next gives me:
>
> CC arch/arm/kernel/process.o
> In file included from /data/lemmy/linux.trees.git/arch/arm/mach-
> exynos/include/mach/system.h:16:0,
> from
/data/lemmy/linux.trees.git/arch/arm/kernel/process.c:64:
> /data/lemmy/linux.trees.git/arch/arm/plat-samsung/include/plat/system-
> reset.h:19:2: error: #error Fix me up
>
> I better not ask the question how such an #error statement can come
> through to linux-next. But what I can say is that I will not merge
> your code until you guys make sure that your upstream platform code has
> enough quality so that it at least compiles.
>
Hi Joerg,
I already knew that, Russell added it so that I can take the ARM restart
changes seriously.
Since I pushed exynos restart patches to Russell's patch system so please
kindly ignore it.
> I attach the config I used for my compile-test.
>
OK, let me check and if any updates, let you know.
Happy New Year.
Thanks.
Best regards,
Kgene.
--
Kukjin Kim <kgene.kim@xxxxxxxxxxx>, Senior Engineer,
SW Solution Development Team, Samsung Electronics Co., Ltd.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/