qi: use "\r\n" in serial console?

Timo Juhani Lindfors timo.lindfors at iki.fi
Fri Jun 24 10:49:28 CEST 2011


Fox Mulder <Quakeman1 at gmx.net> writes:
> I don't know picocom but Linux normally uses \n while windows uses \r\n.
> So if qi only use \n it is corrrect for linux.

In files on the disk yes. But I'm talking about serial communiatications
here. If I boot with Qi I see



Qi Bootloader s3c2442  wallwart debian_20100105-1~unrelease0 
                                                             2011-06-06T08:29:17+0000  Copyright (C) 2008 Openmoko, Inc.

                                                                                                                             Detected: Freerunner / GTA02, A6 PCB
                                                                                                                                                                 Battery condition reasonable

                                                                                                                                                                                             Trying kernel: SD Card EXT2 P1 Kernel
                     Card Type: SD 2.0 SDHC / Mfr: 0x02, OEM "TM" / SA08G", rev 0.6 / s/n: 576236754 / date: 12/2010
                                                                                                                        SDHC size: 7592 MiB
                                                                                                                                               Partition: 1 start +52 512-byte blocks, size 16 MiB
                                                                                                                                                                                                      EXT2 open: boot/noboot-GTA02 Open failed
                                 EXT2 open: boot/append-GTA02 OK
                                                                    EXT2 open: boot/uImage-GTA02.bin OK
                                                                                                               Found: "Debian FreeRunner Kernel"
                                                                                                                                                         Size: 2148 KiB
                                                                                                                                                                           EXT2 open: boot/uImage-GTA02.bin OK
                                                                                                                                                                                                                    Cmdline: loglevel=4 console=tty0 console=ttySAC2,115200 init=/sbin/init ro  mtdparts=physmap-flash:-(nor);neo1973-nand:0x00040000(qi),0x00040000(depr-ub-env),0x00800000(kernel),0x000a0000(depr),0x00040000(identity-ext2),0x0f6a0000(rootfs)  g_ether.dev_addr=00:1F:11:01:62:8A g_ether.host_addr=00:1F:11:01:62:8B  root=/dev/mmcblk0p1 rootdelay=1 rootdelay=8 panic=20 mem=127M root=/dev/mmcblk0p2 loglevel=8 rootfstype=ext3 
      Starting --->

                   Uncompressing Linux... done, booting the kernel.
[    0.000000] Linux version 2.6.34-20101212.git049b71de (root at neo) (gcc version 4.6.1 20110611 (prerelease) (Debian 4.6.0-13) ) #1 Fri Jun 17 00:09:05 UTC 2011
[    0.000000] CPU: ARM920T [41129200] revision 0 (ARMv4T), cr=c0007177
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine: GTA02
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] On node 0 totalpages: 32512
[    0.000000] free_area_init_node: node 0, pgdat c0432c00, node_mem_map c0487000
[    0.000000]   Normal zone: 254 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 32258 pages, LIFO batch:7
[    0.000000] CPU S3C2442B (id 0x32440aab)
[    0.000000] S3C24XX Clocks, Copyright 2004 Simtec Electronics
[    0.000000] S3C244X: core 400.000 MHz, memory 100.000 MHz, peripheral 50.000 MHz
[    0.000000] CLOCK: Slow mode (1.500 MHz), fast, MPLL on, UPLL on


so clearly Qi and Linux are sending different line endings.

Can somebody else with a debug board confirm?

-Timo



More information about the community mailing list