Page 5 of 6

Re: New Yank555.lu kernels source??

PostPosted: 06 Aug 2013, 20:58
by Perka
I have 2 more kernel I compile, I have added sourcedrop as a remote and now I fetch it so I can cherry-pick the update 11 commit.
resolve the conflicts and then I should be good to go?

Re: New Yank555.lu kernels source??

PostPosted: 06 Aug 2013, 21:01
by yank555
Perka wrote:I have 2 more kernel I compile, I have added sourcedrop as a remote and now I fetch it so I can cherry-pick the update 11 commit.
resolve the conflicts and then I should be good to go?


That's exactly how I use the drop-repo, yes.

JP.

PS: But you should apply in the correct order, in case you haven't applied prior update.

Re: New Yank555.lu kernels source??

PostPosted: 06 Aug 2013, 21:05
by Perka
Yes I have the other updates applied, now compiling, lets see :)

Re: New Yank555.lu kernels source??

PostPosted: 06 Aug 2013, 21:09
by yank555
Fingers crossed :D

Re: New Yank555.lu kernels source??

PostPosted: 06 Aug 2013, 21:21
by Perka
:(

Code: Select all
drivers/video/fbmem.c: In function ‘fb_mmap’:
drivers/video/fbmem.c:1397:6: error: ‘off’ undeclared (first use in this function)
drivers/video/fbmem.c:1397:6: note: each undeclared identifier is reported only once for each function it appears in
drivers/video/fbmem.c:1363:16: warning: unused variable ‘mmio_pgoff’ [-Wunused-variable]
make[2]: *** [drivers/video/fbmem.o] Error 1
make[1]: *** [drivers/video] Error 2
make[1]: *** Waiting for unfinished jobs....
  CC      drivers/usb/core/hub.o
In file included from drivers/usb/core/hub.c:34:0:
drivers/usb/core/sec-dock.h:38:13: warning: ‘call_audiodock_notify’ defined but not used [-Wunused-function]
  CC      drivers/tty/tty_ioctl.o
  CC      drivers/usb/gadget/s3c_udc_otg.o
  CC      drivers/tty/tty_ldisc.o
drivers/usb/core/hub.c: In function ‘hub_thread’:
drivers/usb/core/hub.c:2242:17: warning: ‘portchange’ may be used uninitialized in this function [-Wmaybe-uninitialized]
drivers/usb/core/hub.c:2221:18: note: ‘portchange’ was declared here
drivers/usb/core/hub.c: In function ‘usb_port_resume’:
drivers/usb/core/hub.c:2645:33: warning: ‘portstatus’ may be used uninitialized in this function [-Wmaybe-uninitialized]
drivers/usb/core/hub.c:2645:33: warning: ‘portchange’ may be used uninitialized in this function [-Wmaybe-uninitialized]
  CC      drivers/usb/gadget/android.o
In file included from drivers/usb/gadget/android.c:57:0:
drivers/usb/gadget/f_mtp_samsung.c: In function ‘read_send_work’:
drivers/usb/gadget/f_mtp_samsung.c:772:28: warning: unused variable ‘cdev’ [-Wunused-variable]
In file included from drivers/usb/gadget/android.c:65:0:
drivers/usb/gadget/f_diag.c: In function ‘usb_config_work_func’:
drivers/usb/gadget/f_diag.c:145:21: warning: unused variable ‘s’ [-Wunused-variable]
drivers/usb/gadget/f_diag.c:144:29: warning: unused variable ‘table’ [-Wunused-variable]
drivers/usb/gadget/f_diag.c:143:28: warning: unused variable ‘cdev’ [-Wunused-variable]
drivers/usb/gadget/android.c: In function ‘diag_function_bind_config’:
drivers/usb/gadget/android.c:974:6: warning: unused variable ‘once’ [-Wunused-variable]
In file included from drivers/usb/gadget/android.c:57:0:
drivers/usb/gadget/android.c: At top level:
drivers/usb/gadget/f_mtp_samsung.c:721:13: warning: ‘interrupt_complete’ defined but not used [-Wunused-function]
  CC      drivers/usb/core/hcd.o
  CC      drivers/tty/tty_buffer.o
  CC      drivers/tty/tty_port.o
  CC      drivers/tty/tty_mutex.o
  CC      drivers/usb/core/urb.o
  CC      drivers/tty/pty.o
  CC      drivers/usb/core/message.o
  CC      drivers/tty/sysrq.o
  LD      drivers/tty/ipwireless/built-in.o
  CC      drivers/tty/serial/serial_core.o
  CC      drivers/usb/core/driver.o
  CC      drivers/usb/core/config.o
  CC      drivers/tty/serial/8250.o
  CC      drivers/usb/core/file.o
  CC      drivers/usb/core/buffer.o
  CC      drivers/tty/serial/samsung.o
  CC      drivers/usb/core/sysfs.o
  CC      drivers/tty/serial/s5pv210.o
  CC      drivers/usb/core/endpoint.o
  LD      drivers/tty/serial/built-in.o
  CC      drivers/tty/vt/vt_ioctl.o
  CC      drivers/usb/core/devio.o
  CC      drivers/usb/gadget/multi_config.o
  LD      drivers/usb/gadget/g_android.o
  LD      drivers/usb/gadget/built-in.o
  CC      drivers/usb/host/ehci-hcd.o
  CC      drivers/tty/vt/vc_screen.o
  CC      drivers/tty/vt/selection.o
  CC      drivers/usb/core/notify.o
  CC      drivers/tty/vt/keyboard.o
  CC      drivers/usb/core/generic.o
  CC      drivers/usb/core/quirks.o
  CC      drivers/usb/core/devices.o
  CC      drivers/tty/vt/consolemap.o
  CC      drivers/usb/core/inode.o
  LD      drivers/usb/core/usbcore.o
  LD      drivers/usb/core/built-in.o
  LD      drivers/usb/misc/built-in.o
  CC      drivers/usb/mon/mon_main.o
  CONMK   drivers/tty/vt/consolemap_deftbl.c
  CC      drivers/tty/vt/vt.o
  CC      drivers/usb/mon/mon_stat.o
  CC      drivers/usb/mon/mon_text.o
  CC      drivers/usb/host/ohci-hcd.o
In file included from drivers/usb/host/ohci-hcd.c:101:0:
drivers/usb/host/ohci-dbg.c: In function ‘fill_registers_buffer’:
drivers/usb/host/ohci-dbg.c:642:2: warning: the comparison will always evaluate as ‘true’ for the address of ‘next’ will never be NULL [-Waddress]
drivers/usb/host/ohci-dbg.c:661:3: warning: the comparison will always evaluate as ‘true’ for the address of ‘next’ will never be NULL [-Waddress]
  CC      drivers/usb/mon/mon_bin.o
  LD      drivers/usb/mon/usbmon.o
  LD      drivers/usb/mon/built-in.o
  CC      drivers/usb/notify/host_notify_class.o
  CC      drivers/usb/notify/host_notifier.o
  LD      drivers/usb/host/built-in.o
  CC      drivers/usb/serial/usb-serial.o
  LD      drivers/usb/notify/built-in.o
  CC      drivers/usb/storage/scsiglue.o
  SHIPPED drivers/tty/vt/defkeymap.c
  CC      drivers/tty/vt/consolemap_deftbl.o
  CC      drivers/tty/vt/defkeymap.o
  LD      drivers/tty/vt/built-in.o
  LD      drivers/tty/built-in.o
  CC      drivers/usb/storage/protocol.o
  CC      drivers/usb/serial/generic.o
  CC      drivers/usb/serial/bus.o
  CC      drivers/usb/storage/transport.o
  CC      drivers/usb/serial/pl2303.o
  CC      drivers/usb/storage/usb.o
  CC      drivers/usb/storage/initializers.o
  LD      drivers/usb/serial/usbserial.o
  LD      drivers/usb/serial/built-in.o
  CC      drivers/usb/storage/sierra_ms.o
  CC      drivers/usb/storage/option_ms.o
  CC      drivers/usb/storage/usual-tables.o
  LD      drivers/usb/storage/usb-storage.o
  LD      drivers/usb/storage/built-in.o
  LD      drivers/usb/built-in.o
make: *** [drivers] Error 2

real   6m6.868s
user   15m55.374s
sys   1m27.512s

Re: New Yank555.lu kernels source??

PostPosted: 06 Aug 2013, 21:27
by yank555
There is a merge derp in fbmem.c :(

What is the actual Sammy base you're using ?

JP.

Re: New Yank555.lu kernels source??

PostPosted: 06 Aug 2013, 21:31
by Perka
I use update 10 stock :)

Re: New Yank555.lu kernels source??

PostPosted: 06 Aug 2013, 21:51
by Perka

Re: New Yank555.lu kernels source??

PostPosted: 07 Aug 2013, 02:40
by Perka
Found this by javilonas and it works perfect :)

https://github.com/javilonas/Lonas_KL_G ... ed6d6524ce

Re: New Yank555.lu kernels source??

PostPosted: 07 Aug 2013, 08:50
by yank555
Perka wrote:Found this by javilonas and it works perfect :)

https://github.com/javilonas/Lonas_KL_G ... ed6d6524ce


Well to be honest, I don't see the difference :D

JP.