Dear All,
In addition, i would like to attached a few debug prints associated
with the scenario's described in my previous email:
> A. When we boot through this kernel(with USB drivers as a kernel
component):
> 1. We see that the boot process detects the on board USB Hub, and
> the boot process fails at the kernel IP-Config routines(the board is
> configured
> to get an IP address through DHCP)
> 2. The serial console does not seem to respond
> 3. At this point, If we connect / dicsonnect a USB Keyboard,Mouse
> device, the driver prints the appropriate messages indicating that
> these devices have been connected / disconnected.
For this scenario, The boot up messages are like this :
;
;
;
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
musb_hdrc: version 6.0, cppi-dma, host, debug=0
musb_hdrc: USB Host mode controller at c8000000 using DMA, IRQ 12
musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
usb usb1: configuration #1 chosen from 1 choice
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
;
;
More boot messages......
;
0x00050000-0x00250000 : "kernel"
<5>0x00250000-0x01000000 : "filesystem"
0x00250000-0x01000000 : "filesystem"
<5>usbmon: debugfs is not available
usbmon: debugfs is not available
<6>Initializing USB Mass Storage driver...
Initializing USB Mass Storage driver...
<6>usbcore: registered new interface driver usb-storage
usbcore: registered new interface driver usb-storage
<6>USB Mass Storage support registered.
USB Mass Storage support registered.
<6>mice: PS/2 mouse device common for all mice
mice: PS/2 mouse device common for all mice
<6>usbcore: registered new interface driver usbhid
usbcore: registered new interface driver usbhid
<6>drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
drivers/hid/usbhid/hid-core.c: v2.6:USB HID core driver
<6>TCP cubic registered
TCP cubic registered
<6>NET: Registered protocol family 1
NET: Registered protocol family 1
<6>NET: Registered protocol family 17
NET: Registered protocol family 17
<5>Sending DHCP requests .Sending DHCP requests ........... timed out!
timed out!
<3>IP-Config: Retrying forever (NFS root)...
IP-Config: Retrying forever (NFS root)...
<5>Sending DHCP requests .Sending DHCP requests ........... timed out!
timed out!
<3>IP-Config: Retrying forever (NFS root)...
IP-Config: Retrying forever (NFS root)...
<5>Sending DHCP requests .Sending DHCP requests ........... timed out!
timed out!
<3>IP-Config: Retrying forever (NFS root)...
IP-Config: Retrying forever (NFS root)...
As you can see, The IP-Config DHCP requests keep failing, IP is not
assigned and the board cannot proceed to boot from NFS. Why would the
USB function cause the IP-Config DHCP routines to fail??
> B. When we boot through this kernel with the USB drivers compiled as
> modules ( HID support compiled within kernel)
> 1. The boot process, IP-Config, launching of shell happens successfully.
> 2. From the shell launched on the serial console, if we insmod
> musb_hdrc.ko, insmod command does not seem to return to console prompt
> and the serial console freezes like described in (A) above. Again
> devices
> connected / disconnected are still reported correctly on the
> frozen serial console.The USB devices seem to work properly, causing
> the serial console to freeze.
In this case, the boot messages are like this:
start of boot.
;
;
;
;
;
<6>NET: Registered protocol family 1
NET: Registered protocol family 1
<6>NET: Registered protocol family 17
NET: Registered protocol family 17
<5>Sending DHCP requests .Sending DHCP requests ...,, OK
OK
IP-Config: Got DHCP answer from 0.0.0.0, IP-Config: Got DHCP answer
from 0.0.0.0, my address is 192.168.1.194
my address is 192.168.1.194
IP-Config: Complete:IP-Config: Complete:
device=eth0
device=eth0, addr=192.168.1.194, addr=192.168.1.194,
mask=255.255.255.0, mask=255.255.255.0, gw=192.168.1.1,
gw=192.168.1.1, .....
;
;
;
;
192.168.1.194 login: root
#insmod ./musb_hdrc.ko
r...@192.168.1.194:~# insmod ./musb_hdrc.ko
<6>musb_hdrc: version 6.0, cppi-dma, host, debug=0
musb_hdrc: version 6.0, cppi-dma, host, debug=0
<7>musb_hdrc: ConfigData=0x06 (UTMI-8, dyn FIFOs, SoftConn)
<7>musb_hdrc: MHDRC RTL version 1.300
<7>musb_hdrc: setup fifo_mode 2
<7>musb_hdrc: 7/9 max ep, 2624/4096 memory
<7>musb_hdrc: hw_ep 0shared, max 64
<7>musb_hdrc: hw_ep 1tx, max 512
<7>musb_hdrc: hw_ep 1rx, max 512
<7>musb_hdrc: hw_ep 2tx, max 512
<7>musb_hdrc: hw_ep 2rx, max 512
<7>musb_hdrc: hw_ep 3shared, max 256
<7>musb_hdrc: hw_ep 4shared, max 256
<6>musb_hdrc: USB Host mode controller at c8050000 using DMA, IRQ 12
musb_hdrc: USB Host mode controller at c8050000 using DMA, IRQ 12
<6>musb_hdrc musb_hdrc: MUSB HDRC host driver
musb_hdrc musb_hdrc: MUSB HDRC host driver
<6>musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
musb_hdrc musb_hdrc: new USB bus registered, assigned bus number 1
<6>usb usb1: configuration #1 chosen from 1 choice
usb usb1: configuration #1 chosen from 1 choice
<6>hub 1-0:1.0: USB hub found
hub 1-0:1.0: USB hub found
<6>hub 1-0:1.0: 1 port detected
hub 1-0:1.0: 1 port detected
r...@192.168.1.194:~# <6>usb 1-1: new high speed USB device using
musb_hdrc and address 2
usb 1-1: new high speed USB device using musb_hdrc and address 2
<6>usb 1-1: configuration #1 chosen from 1 choice
usb 1-1: configuration #1 chosen from 1 choice
<6>hub 1-1:1.0: USB hub found
hub 1-1:1.0: USB hub found
<6>hub 1-1:1.0: 4 ports detected
hub 1-1:1.0: 4 ports detected
;
;
;
[Does not return to # prompt, serial console does not respond]
At this point if i connect,disconnect a USB Keyboard/Mouse/Flash drive.....
;
;
<6>usb 1-1.1: new low speed USB device using musb_hdrc and address 3
usb 1-1.1: new low speed USB device using musb_hdrc and address 3
<6>usb 1-1.1: configuration #1 chosen from 1 choice
usb 1-1.1: configuration #1 chosen from 1 choice
<6>input: USB Mouse as /class/input/input0
input: USB Mouse as /class/input/input0
<6>inputinput: USB HID v1.10 Mouse [USB Mouse] on usb-musb_hdrc-1.1
: USB HID v1.10 Mouse [USB Mouse] on usb-musb_hdrc-1.1
<6>usb 1-1.1: USB disconnect, address 3
usb 1-1.1: USB disconnect, address 3
<6>usb 1-1.1: new low speed USB device using musb_hdrc and address 4
usb 1-1.1: new low speed USB device using musb_hdrc and address 4
<6>usb 1-1.1: configuration #1 chosen from 1 choice
usb 1-1.1: configuration #1 chosen from 1 choice
<6>input: Logitech Logitech USB Keyboard as /class/input/input1
input: Logitech Logitech USB Keyboard as /class/input/input1
<6>inputinput: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard]
on usb-musb_hdrc-1.1
: USB HID v1.10 Keyboard [Logitech Logitech USB Keyboard] on
usb-musb_hdrc-1.1
<6>usb 1-1.1: USB disconnect, address 4
usb 1-1.1: USB disconnect, address 4
<6>usb 1-1.1: new high speed USB device using musb_hdrc and address 5
usb 1-1.1: new high speed USB device using musb_hdrc and address 5
<6>usb 1-1.1: configuration #1 chosen from 1 choice
usb 1-1.1: configuration #1 chosen from 1 choice
<6>usb 1-1.1: USB disconnect, address 5
usb 1-1.1: USB disconnect, address 5
;
;
;
[Still we are not returned to prompt]
Pointer will be appreciated!!
regards,
Deepak
On 4/10/09, Deepak Mundra <deepa...@allaboutif.com> wrote:
>
> Dear All,
>
> We are working on getting the Linux 2.6.23 kernel working on our Custom
> Board.
> Due to a certain legacy driver ( written only for 2.6.23) we are
> forced to use 2.6.23.
> So far most of the Interfaces on our hardware are working perfectly
> fine with the 2.6.23 kernel. However an issue still remains with the
> USB function. I wil describe this to you:
>
> 1. Our board has a onboard hub chip.
> 2. We compile the 2.6.23 kernel with DaVinci musb drivers, USB HID
> device support.
>
> A. When we boot through this kernel(with USB drivers as a kernel
> component):
> 1. We see that the boot process detects the on board USB Hub, and
> the boot process fails at the kernel IP-Config routines(the board is
> configured
> to get an IP address through DHCP)
> 2. The serial console does not seem to respond
> 3. At this point, If we connect / disconnect a USB Keyboard,Mouse
> device, the driver prints the appropriate messages indicating that
> these devices have been connected / disconnected.
>
> B. When we boot through this kernel with the USB drivers compiled as
> modules ( HID support compiled within kernel)
> 1. The boot process, IP-Config, launching of shell happens successfully.
> 2. From the shell launched on the serial console, if we insmod
> musb_hdrc.ko, insmod command does not seem to return to console prompt
> and the serial console freezes like described in (A) above. Again
> devices
> connected / disconnected are still reported correctly on the
> frozen serial console.The USB devices seem to work properly, causing
> the serial console to freeze.
>
> Observing the above two, here is what we tried:
>
> C. With the kernel with the USB drivers compiled as modules and:
> 1. Boot the kernel with the usb musb support compiled as module
> 2. Wait for shell to appear on serial console, start sshd daemon
> from the console shell
> 3. Login to the board via ssh, and insmod musb_hdrc.ko - here the
> insmod returns to the shell!! However, the serial console freezes like
> (A) above.
> 4. USB devices connected / disconnected are detected properly
> 5. The ssh terminal looks to be healthy, allowing running of applications.
>
> Could some one point out what the issue could be?
> I am looking to fix this behaviour in my 2.6.23 kernel tree, and use
> the usb function as a kernel compiled functionality.
>
> I understand the 2.6.23 kernel tree may not be of focus at the moment,
> but a few pointers on the possible solutions would help me
> tremendously as i am trying to get this fixed.
>
> Look forward to some suggestions/pointers.
>
> regards,
> Deepak
>
>
>
>
>
>
>
_______________________________________________
Davinci-linux-open-source mailing list
Davinci-linux-open-source@linux.davincidsp.com
http://linux.davincidsp.com/mailman/listinfo/davinci-linux-open-source
