linux-kernel - Re: [PATCH] arch: m68k: include: asm: define 'VM_DATA_DEFAULT_FLAGS' no matter whether has 'NOMMU' or not.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 29 Jun 2013 10:26:02 +0200
From:	Geert Uytterhoeven <geert@...ux-m68k.org>
To:	Michael Schmitz <schmitzmic@...il.com>
Cc:	Chen Gang <gang.chen@...anux.com>,
	linux-m68k <linux-m68k@...ts.linux-m68k.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	uClinux development list <uclinux-dev@...inux.org>
Subject: Re: [PATCH] arch: m68k: include: asm: define 'VM_DATA_DEFAULT_FLAGS'
 no matter whether has 'NOMMU' or not.

On Sat, Jun 29, 2013 at 10:01 AM, Michael Schmitz <schmitzmic@...il.com> wrote:
>> The same .config file, also report the compiling error below:
>>
>> drivers/i2c/busses/i2c-ocores.c:81:2: error: implicit declaration of
>> function ‘iowrite8’ [-Werror=implicit-function-declaration]
>> drivers/i2c/busses/i2c-ocores.c:86:2: error: implicit declaration of
>> function ‘iowrite16’ [-Werror=implicit-function-declaration]
>> drivers/i2c/busses/i2c-ocores.c:91:2: error: implicit declaration of
>> function ‘iowrite32’ [-Werror=implicit-function-declaration]
>> drivers/i2c/busses/i2c-ocores.c:96:2: error: implicit declaration of
>> function ‘ioread8’ [-Werror=implicit-function-declaration]
>> drivers/i2c/busses/i2c-ocores.c:101:2: error: implicit declaration of
>> function ‘ioread16’ [-Werror=implicit-function-declaration]
>> drivers/i2c/busses/i2c-ocores.c:106:2: error: implicit declaration of
>> function ‘ioread32’ [-Werror=implicit-function-declaration]
>>
>> Excuse me, I am not quite familiar with the related hardware and m68k,
>> I guess under m68k architecture, we need not this drivers, is it correct ?

Until someone synthesizes the OpenCores i2c core together with the
OpenCores 68000 core (they seem to have one), and tries to run uClinux
on it...

> That would be correct, yes. Perhaps add appropriate dependencies in
> drivers/i2c/Kconfig to allow building I2C drivers
> only on hardware that supports it?

We still want it for compile-coverage.

Now, the issue is that m68knommu doesn't implement ioread8() and
friends, so I'm adding the uClinux list.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/