Re: Linux 3.0 release

From: Yoshinori Sato
Date: Wed Jul 27 2011 - 11:22:43 EST

Next message: Arnd Bergmann: "Re: [PATCH] bitops: Use volatile in generic atomic bitops."
Previous message: Eric Dumazet: "[PATCH] vfs: avoid taking locks if inode not in lists"
In reply to: Arnaud Lacombe: "Re: Linux 3.0 release"
Next in thread: Arnaud Lacombe: "Re: Linux 3.0 release"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

At Mon, 25 Jul 2011 11:50:43 -0400,
Arnaud Lacombe wrote:
>
> Hi,
>
> On Sun, Jul 24, 2011 at 10:21 PM, Yoshinori Sato
> <ysato@xxxxxxxxxxxxxxxxxxxx> wrote:
> > At Sun, 24 Jul 2011 18:04:59 -0400,
> > Arnaud Lacombe wrote:
> >>
> >> Hi,
> >>
> >> On Thu, Jul 21, 2011 at 10:59 PM, Linus Torvalds
> >> <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:
> >> >
> >> > So there it is. Gone are the 2.6.<bignum> days, and 3.0 is out.
> >> > [...]
> >> For the record, if anybody cares, arch/h8300 no longer configure since 2.6.38:
> >>
> >> % make ARCH=h8300 menuconfig
> >> make: h8300-elf-gcc: Command not found
> >> Â HOSTCC Âscripts/basic/fixdep
> >> Â HOSTCC Âscripts/kconfig/conf.o
> >> Â HOSTCC Âscripts/kconfig/lxdialog/checklist.o
> >> Â HOSTCC Âscripts/kconfig/lxdialog/inputbox.o
> >> Â HOSTCC Âscripts/kconfig/lxdialog/menubox.o
> >> Â HOSTCC Âscripts/kconfig/lxdialog/textbox.o
> >> Â HOSTCC Âscripts/kconfig/lxdialog/util.o
> >> Â HOSTCC Âscripts/kconfig/lxdialog/yesno.o
> >> Â HOSTCC Âscripts/kconfig/mconf.o
> >> Â SHIPPED scripts/kconfig/zconf.tab.c
> >> Â SHIPPED scripts/kconfig/lex.zconf.c
> >> Â SHIPPED scripts/kconfig/zconf.hash.c
> >> Â HOSTCC Âscripts/kconfig/zconf.tab.o
> >> Â HOSTLD Âscripts/kconfig/mconf
> >> scripts/kconfig/mconf Kconfig
> >> arch/h8300/Kconfig:198: can't open file "drivers/serial/Kconfig"
> >> make[1]: *** [menuconfig] Error 1
> >> make: *** [menuconfig] Error 2
> >>
> >> Yes, I know I have no h8300-elf-gcc, but it does not change the fact
> >> that the arch tries to include a non-existent file. It's been broken
> >> by:
> >>
> >> commit ab4382d27412e7e3e7c936e8d50d8888dfac3df8
> >> Author: Greg Kroah-Hartman <gregkh@xxxxxxx>
> >> Date: Â Thu Jan 13 12:10:18 2011 -0800
> >>
> >> Â Â tty: move drivers/serial/ to drivers/tty/serial/
> >>
> >> Â Â The serial drivers are really just tty drivers, so move them to
> >> Â Â drivers/tty/ to make things a bit neater overall.
> >> Â Â This is part of the tty/serial driver movement proceedure as proposed by
> >> Â Â Arnd Bergmann and approved by everyone involved a number of months ago.
> >>
> >> Â Â Cc: Arnd Bergmann <arnd@xxxxxxxx>
> >> Â Â Cc: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
> >> Â Â Cc: Geert Uytterhoeven <geert@xxxxxxxxxxxxxx>
> >> Â Â Cc: Rogier Wolff <R.E.Wolff@xxxxxxxxxxxx>
> >> Â Â Cc: Michael H. Warfield <mhw@xxxxxxxxxxxx>
> >> Â Â Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxx>
> >>
> >> Â- Arnaud
> >
> > Please try this fix.
> > Signed-off-by: Yoshinori Sato <ysato@xxxxxxxxxxxxxxxxxxxx>
> >
> > diff --git a/arch/h8300/Kconfig b/arch/h8300/Kconfig
> > index 091ed61..910e5ad 100644
> > --- a/arch/h8300/Kconfig
> > +++ b/arch/h8300/Kconfig
> > @@ -89,125 +89,7 @@ endmenu
> >
> > Âsource "net/Kconfig"
> >
> > -source "drivers/base/Kconfig"
> > -
> > -source "drivers/mtd/Kconfig"
> > -
> > -source "drivers/block/Kconfig"
> > -
> > -source "drivers/ide/Kconfig"
> > -
> > -source "arch/h8300/Kconfig.ide"
> > -
> > -source "drivers/net/Kconfig"
> > -
> > -#
> > -# input - input/joystick depends on it. As does USB.
> > -#
> > -source "drivers/input/Kconfig"
> > -
> > -menu "Character devices"
> > -
> > -config VT
> > - Â Â Â bool "Virtual terminal"
> > - Â Â Â ---help---
> > - Â Â Â Â If you say Y here, you will get support for terminal devices with
> > - Â Â Â Â display and keyboard devices. These are called "virtual" because you
> > - Â Â Â Â can run several virtual terminals (also called virtual consoles) on
> > - Â Â Â Â one physical terminal. This is rather useful, for example one
> > - Â Â Â Â virtual terminal can collect system messages and warnings, another
> > - Â Â Â Â one can be used for a text-mode user session, and a third could run
> > - Â Â Â Â an X session, all in parallel. Switching between virtual terminals
> > - Â Â Â Â is done with certain key combinations, usually Alt-<function key>.
> > -
> > - Â Â Â Â The setterm command ("man setterm") can be used to change the
> > - Â Â Â Â properties (such as colors or beeping) of a virtual terminal. The
> > - Â Â Â Â man page console_codes(4) ("man console_codes") contains the special
> > - Â Â Â Â character sequences that can be used to change those properties
> > - Â Â Â Â directly. The fonts used on virtual terminals can be changed with
> > - Â Â Â Â the setfont ("man setfont") command and the key bindings are defined
> > - Â Â Â Â with the loadkeys ("man loadkeys") command.
> > -
> > - Â Â Â Â You need at least one virtual terminal device in order to make use
> > - Â Â Â Â of your keyboard and monitor. Therefore, only people configuring an
> > - Â Â Â Â embedded system would want to say N here in order to save some
> > - Â Â Â Â memory; the only way to log into such a system is then via a serial
> > - Â Â Â Â or network connection.
> > -
> > - Â Â Â Â If unsure, say Y, or else you won't be able to do much with your new
> > - Â Â Â Â shiny Linux system :-)
> > -
> > -config VT_CONSOLE
> > - Â Â Â bool "Support for console on virtual terminal"
> > - Â Â Â depends on VT
> > - Â Â Â ---help---
> > - Â Â Â Â The system console is the device which receives all kernel messages
> > - Â Â Â Â and warnings and which allows logins in single user mode. If you
> > - Â Â Â Â answer Y here, a virtual terminal (the device used to interact with
> > - Â Â Â Â a physical terminal) can be used as system console. This is the most
> > - Â Â Â Â common mode of operations, so you should say Y here unless you want
> > - Â Â Â Â the kernel messages be output only to a serial port (in which case
> > - Â Â Â Â you should say Y to "Console on serial port", below).
> > -
> > - Â Â Â Â If you do say Y here, by default the currently visible virtual
> > - Â Â Â Â terminal (/dev/tty0) will be used as system console. You can change
> > - Â Â Â Â that with a kernel command line option such as "console=tty3" which
> > - Â Â Â Â would use the third virtual terminal as system console. (Try "man
> > - Â Â Â Â bootparam" or see the documentation of your boot loader (lilo or
> > - Â Â Â Â loadlin) about how to pass options to the kernel at boot time.)
> > -
> > - Â Â Â Â If unsure, say Y.
> > -
> > -config HW_CONSOLE
> > - Â Â Â bool
> > - Â Â Â depends on VT && !S390 && !UM
> > - Â Â Â default y
> > -
> > -comment "Unix98 PTY support"
> > -
> > -config UNIX98_PTYS
> > - Â Â Â bool "Unix98 PTY support"
> > - Â Â Â ---help---
> > - Â Â Â Â A pseudo terminal (PTY) is a software device consisting of two
> > - Â Â Â Â halves: a master and a slave. The slave device behaves identical to
> > - Â Â Â Â a physical terminal; the master device is used by a process to
> > - Â Â Â Â read data from and write data to the slave, thereby emulating a
> > - Â Â Â Â terminal. Typical programs for the master side are telnet servers
> > - Â Â Â Â and xterms.
> > -
> > - Â Â Â Â Linux has traditionally used the BSD-like names /dev/ptyxx for
> > - Â Â Â Â masters and /dev/ttyxx for slaves of pseudo terminals. This scheme
> > - Â Â Â Â has a number of problems. The GNU C library glibc 2.1 and later,
> > - Â Â Â Â however, supports the Unix98 naming standard: in order to acquire a
> > - Â Â Â Â pseudo terminal, a process opens /dev/ptmx; the number of the pseudo
> > - Â Â Â Â terminal is then made available to the process and the pseudo
> > - Â Â Â Â terminal slave can be accessed as /dev/pts/<number>. What was
> > - Â Â Â Â traditionally /dev/ttyp2 will then be /dev/pts/2, for example.
> > -
> > - Â Â Â Â The entries in /dev/pts/ are created on the fly by a virtual
> > - Â Â Â Â file system; therefore, if you say Y here you should say Y to
> > - Â Â Â Â "/dev/pts file system for Unix98 PTYs" as well.
> > -
> > - Â Â Â Â If you want to say Y here, you need to have the C library glibc 2.1
> > - Â Â Â Â or later (equal to libc-6.1, check with "ls -l /lib/libc.so.*").
> > - Â Â Â Â Read the instructions in <file:Documentation/Changes> pertaining to
> > - Â Â Â Â pseudo terminals. It's safe to say N.
> > -
> > -source "drivers/char/pcmcia/Kconfig"
> > -
> > -source "drivers/serial/Kconfig"
> > -
> > -source "drivers/i2c/Kconfig"
> > -
> > -source "drivers/hwmon/Kconfig"
> > -
> > -source "drivers/usb/Kconfig"
> > -
> > -source "drivers/uwb/Kconfig"
> > -
> > -endmenu
> > -
> > -source "drivers/staging/Kconfig"
> > +source "drivers/Kconfig"
> >
> > Âsource "fs/Kconfig"
> >
> > diff --git a/arch/h8300/include/asm/types.h b/arch/h8300/include/asm/types.h
> > index bb2c91a..b9e79bc 100644
> > --- a/arch/h8300/include/asm/types.h
> > +++ b/arch/h8300/include/asm/types.h
> > @@ -1,29 +1 @@
> > -#ifndef _H8300_TYPES_H
> > -#define _H8300_TYPES_H
> > -
> > -#include <asm-generic/int-ll64.h>
> > -
> > -#if !defined(__ASSEMBLY__)
> > -
> > -/*
> > - * This file is never included by application software unless
> > - * explicitly requested (e.g., via linux/types.h) in which case the
> > - * application is Linux specific so (user-) name space pollution is
> > - * not a major issue. ÂHowever, for interoperability, libraries still
> > - * need to be careful to avoid a name clashes.
> > - */
> > -
> > -typedef unsigned short umode_t;
> > -
> > -/*
> > - * These aren't exported outside the kernel to avoid name space clashes
> > - */
> > -#ifdef __KERNEL__
> > -
> > -#define BITS_PER_LONG 32
> > -
> > -#endif /* __KERNEL__ */
> > -
> > -#endif /* __ASSEMBLY__ */
> > -
> > -#endif /* _H8300_TYPES_H */
> > +#include <asm-generic/types.h>
> > diff --git a/arch/h8300/include/asm/unistd.h b/arch/h8300/include/asm/unistd.h
> > index 2c3f8e6..7cdb4ea 100644
> > --- a/arch/h8300/include/asm/unistd.h
> > +++ b/arch/h8300/include/asm/unistd.h
> > @@ -325,11 +325,37 @@
> > Â#define __NR_move_pages Â Â Â Â Â Â Â Â317
> > Â#define __NR_getcpu Â Â Â Â Â Â318
> > Â#define __NR_epoll_pwait Â Â Â 319
> > -#define __NR_setns Â Â Â Â Â Â 320
> > +#define __NR_utimensat Â Â Â Â 320
> > +#define __NR_signalfd Â Â Â Â Â321
> > +#define __NR_timerfd_create Â Â322
> > +#define __NR_eventfd Â Â Â Â Â 323
> > +#define __NR_fallocate Â Â Â Â 324
> > +#define __NR_timerfd_settime Â 325
> > +#define __NR_timerfd_gettime Â 326
> > +#define __NR_signalfd4 Â Â Â Â 327
> > +#define __NR_eventfd2 Â Â Â Â Â328
> > +#define __NR_epoll_create1 Â Â 329
> > +#define __NR_dup3 Â Â Â Â Â Â Â330
> > +#define __NR_pipe2 Â Â Â Â Â Â 331
> > +#define __NR_inotify_init1 Â Â 332
> > +#define __NR_preadv Â Â Â Â Â Â333
> > +#define __NR_pwritev Â Â Â Â Â 334
> > +#define __NR_rt_tgsigqueueinfo 335
> > +#define __NR_perf_event_open Â 336
> > +#define __NR_recvmmsg Â Â Â Â Â337
> > +#define __NR_fanotify_init Â Â 338
> > +#define __NR_fanotify_mark Â Â 339
> > +#define __NR_prlimit64 Â Â Â Â 340
> > +#define __NR_name_to_handle_at 341
> > +#define __NR_open_by_handle_at Â342
> > +#define __NR_clock_adjtime Â Â 343
> > +#define __NR_syncfs Â Â Â Â Â Â 344
> > +#define __NR_sendmmsg Â Â Â Â Â345
> > +#define __NR_setns Â Â Â Â Â Â 346
> >
> > Â#ifdef __KERNEL__
> >
> > -#define NR_syscalls 321
> > +#define NR_syscalls 347
> >
> > Â#define __ARCH_WANT_IPC_PARSE_VERSION
> > Â#define __ARCH_WANT_OLD_READDIR
> > diff --git a/arch/h8300/kernel/syscalls.S b/arch/h8300/kernel/syscalls.S
> > index f4b2e67..4cfe56c 100644
> > --- a/arch/h8300/kernel/syscalls.S
> > +++ b/arch/h8300/kernel/syscalls.S
> > @@ -333,8 +333,34 @@ SYMBOL_NAME_LABEL(sys_call_table)
> > Â Â Â Â.long SYMBOL_NAME(sys_ni_syscall) Â Â Â /* sys_move_pages */
> > Â Â Â Â.long SYMBOL_NAME(sys_getcpu)
> > Â Â Â Â.long SYMBOL_NAME(sys_ni_syscall) Â Â Â /* sys_epoll_pwait */
> > - Â Â Â .long SYMBOL_NAME(sys_setns) Â Â Â Â Â Â/* 320 */
> > -
> > + Â Â Â .long SYMBOL_NAME(sys_utimensat) Â Â Â Â Â Â Â Â/* 320 */
> > + Â Â Â .long SYMBOL_NAME(sys_signalfd)
> > + Â Â Â .long SYMBOL_NAME(sys_timerfd_create)
> > + Â Â Â .long SYMBOL_NAME(sys_eventfd)
> > + Â Â Â .long SYMBOL_NAME(sys_fallocate)
> > + Â Â Â .long SYMBOL_NAME(sys_timerfd_settime) Â/* 325 */
> > + Â Â Â .long SYMBOL_NAME(sys_timerfd_gettime)
> > + Â Â Â .long SYMBOL_NAME(sys_signalfd4)
> > + Â Â Â .long SYMBOL_NAME(sys_eventfd2)
> > + Â Â Â .long SYMBOL_NAME(sys_epoll_create1)
> > + Â Â Â .long SYMBOL_NAME(sys_dup3) Â Â Â Â Â Â Â Â Â Â /* 330 */
> > + Â Â Â .long SYMBOL_NAME(sys_pipe2)
> > + Â Â Â .long SYMBOL_NAME(sys_inotify_init1)
> > + Â Â Â .long SYMBOL_NAME(sys_preadv)
> > + Â Â Â .long SYMBOL_NAME(sys_pwritev)
> > + Â Â Â .long SYMBOL_NAME(sys_rt_tgsigqueueinfo) Â Â Â Â/* 335 */
> > + Â Â Â .long SYMBOL_NAME(sys_perf_event_open)
> > + Â Â Â .long SYMBOL_NAME(sys_recvmmsg)
> > + Â Â Â .long SYMBOL_NAME(sys_fanotify_init)
> > + Â Â Â .long SYMBOL_NAME(sys_fanotify_mark)
> > + Â Â Â .long SYMBOL_NAME(sys_prlimit64) Â Â Â Â Â Â Â Â/* 340 */
> > + Â Â Â .long SYMBOL_NAME(sys_name_to_handle_at)
> > + Â Â Â .long SYMBOL_NAME(sys_open_by_handle_at)
> > + Â Â Â .long SYMBOL_NAME(sys_clock_adjtime)
> > + Â Â Â .long SYMBOL_NAME(sys_syncfs)
> > + Â Â Â .long SYMBOL_NAME(sys_sendmmsg)
> > + Â Â Â .long SYMBOL_NAME(sys_setns)
> > +
> > Â Â Â Â.macro Âcall_sp addr
> > Â Â Â Âmov.l Â #SYMBOL_NAME(\addr),er6
> > Â Â Â Âbra Â Â SYMBOL_NAME(syscall_trampoline):8
> >
> With this patch, it configures, at least, but build fails with:
>
> In file included from /src/linux/linux/include/linux/mempolicy.h:70:0,
> from /src/linux/linux/init/main.c:49:
> /src/linux/linux/include/linux/pagemap.h: In function 'fault_in_pages_readable':
> /src/linux/linux/include/linux/pagemap.h:444:2: error: assignment of
> read-only variable '__gu_val'
> /src/linux/linux/include/linux/pagemap.h:450:5: error: assignment of
> read-only variable '__gu_val'
> make[2]: *** [init/main.o] Error 1
> make[1]: *** [init] Error 2
> make: *** [sub-make] Error 2

OK.
I pushing latest code in here.
git.kernel.org/pub/scm/linux/kernel/git/ysato/h8300.git
Please try it.
I using gcc is v4.5.3

> Cross-toolchain is baremetal binutils and gcc for their respective trunk:
>
> $ /src/h8300/obj/destdir/bin/h8300-elf-gcc -v
> Using built-in specs.
> COLLECT_GCC=/src/h8300/obj/destdir/bin/h8300-elf-gcc
> COLLECT_LTO_WRAPPER=/src/h8300/obj/destdir/libexec/gcc/h8300-elf/4.7.0/lto-wrapper
> Target: h8300-elf
> Configured with: ../gcc/configure --prefix=/src/h8300/obj/destdir
> --target=h8300-elf --enable-languages=c
> Thread model: single
> gcc version 4.7.0 20110609 (experimental) (GCC)
>
> - Arnaud
>
> > --
> > Yoshinori Sato
> > <ysato@xxxxxxxxxxxxxxxxxxxx>
> >

--
Yoshinori Sato
<ysato@xxxxxxxxxxxxxxxxxxxx>
--
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/

Next message: Arnd Bergmann: "Re: [PATCH] bitops: Use volatile in generic atomic bitops."
Previous message: Eric Dumazet: "[PATCH] vfs: avoid taking locks if inode not in lists"
In reply to: Arnaud Lacombe: "Re: Linux 3.0 release"
Next in thread: Arnaud Lacombe: "Re: Linux 3.0 release"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]