[00:01] built-in.o is a special object that consists of individual objects mushed together to form built-in.o [00:04] looking4b: does your kernel boot up? [00:16] kinda [00:16] I cannot really tell passed a point [00:17] it might crash at a point but since I am running it blind I am not sure [00:17] I hooked up the debugger and I go through a lot of code and a lot of printk [00:17] but I see nothing on the console/serial port [00:18] I do have the serial driver turn on in the kernel config [00:18] and my BSP specifies my device [00:18] I am not troubleshooting why I am not getting any console output [00:19] I just cannot figure out which serial/uart driver the kernel is using [00:21] i think I found the driver for the coldfire [00:22] under /driver/serial/mcf.c [00:22] but it does not have the uart_console_write function in it === yofel_ is now known as yofel [14:18] Anyone happen to know the URL for the wiki page about cross-compiling kernels? [16:50] hmm I seem to have a kernel build that's stalled with ld hung in stat->__xstat (libfakeroot)->send_get_state->send_get_fakem->semaphore_up->semop seems odd; I'm guessing that's a libfakeroot bug [17:07] Does anybody know how to get the uart/serial port working for the m68knommu coldfire architecture? [17:08] I have been trying for days without success [17:08] it seems like things have been coded for ttyS0 to function as the console but I only have access to UART1 on my hardware which would be ttyS1 [17:09] I do use a hardcoded kernel argument of console=ttyS1 but nothing works [17:22] looking4b: I assume you have the driver built into the kernel, have you got it booted at all? If so can you get a dmesg to see what it thinks that serial device is? [21:17] does ubuntu use modified module-init-tools?