Hi,

I'm porting Linux on a PowerPC 750FX target board, and I'd like to use a 
Busybox on it on its serial port but I've some problems.
This serial port is specific, and I had to develop my own driver. This 
driver is a classic char driver with read, write, open and release 
functions.
On my first try with this driver and the Busybox getty, I get an error 
message telling me that the device doesn't have any appropriate ioctl. 
So I've added a "fake" ioctl function which alway returns 0, and I've 
managed to get a login prompt like here :

-------------- Start of Linux boot trace --------------
zImage starting: loaded at 0x00400000 (sp: 0x00630ee4)
Allocating 0x357698 bytes for kernel ...
gunzipping (0x00000000 <- 0x0040b000:0x0062f27a)...done 0x312020 bytes

Linux/PowerPC load: console=uartE,9600n8 root=/dev/ram0
Finalizing device tree... flat tree at 0x409bc8
id mach(): done
MMU:enter
MMU:hw init
hash:enter
hash:find piece
hash:patch
hash:done
MMU:mapin
MMU:setio
MMU:exit
setup_arch: bootmem
smd88ng_setup_arch():set_bridge
arch: exit

(none) login: root

--------------  End of Linux boot trace  --------------


I can type my login, press enter, the cursor get on a new line and 
then... nothing !
Here are my inittab, rcs, passwd and group files :

/etc/inittab:
::sysinit:/etc/rcs
::respawn:/sbin/getty -L uartE 9600 vt100

/etc/rcs:
#!/bin/sh
echo "Processing /etc/rcS... "
echo "Mounting Proc"
/bin/mount -t proc proc /proc
/sbin/syslogd
/sbin/klogd
/bin/sh

/etc/passwd:
root::0:0:Super User:/:/bin/sh

/etc/group:
root:x:0:


If I change my inittab to get directly a shell, I get this trace :

-------------- Start of Linux boot trace --------------
zImage starting: loaded at 0x00400000 (sp: 0x00630ee4)
Allocating 0x357698 bytes for kernel ...
gunzipping (0x00000000 <- 0x0040b000:0x0062f11a)...done 0x312020 bytes

Linux/PowerPC load: console=uartE,9600n8 root=/dev/ram0
Finalizing device tree... flat tree at 0x409bc8
id mach(): done
MMU:enter
MMU:hw init
hash:enter
hash:find piece
hash:patch
hash:done
MMU:mapin
MMU:setio
MMU:exit
setup_arch: bootmem
smd88ng_setup_arch():set_bridge
arch: exit

Please press Enter to activate this console.

init: can't log to /dev/tty5
starting pid 72, tty '/dev/uartE': '/bin/sh'

--------------  End of Linux boot trace  --------------

As before, I never get the shell prompt...
The content of the inittab is :
::sysinit:/etc/rcs
uartE::askfirst:-/bin/sh

I really do not know what to do to deal with this problem. Any idea ?
Does Busybox need a driver using the tty layer provided by Linux ?

Best regards,

Hervé Spitz
_______________________________________________
busybox mailing list
[email protected]
http://busybox.net/cgi-bin/mailman/listinfo/busybox

Reply via email to