On 05/21/2014 11:07 AM, John Syn wrote:
On 5/21/14, 8:56 AM, "Ross Morrison" <r...@buy-ei.com> wrote:

Hi all,

My previous email was incorrect, the USB Host port on the BBB works fine
with the USB ASIC AX88x72A based Ethernet Dongle. So back to scratching
my head....

I have identified in the dmesg output a 4 line difference between our
custom board and the BBB.

Our custom board:
[    1.562682] usbcore: registered new interface driver usbhid
[    1.568560] usbhid: USB HID core driver
[    1.573609] ashmem: initialized
[    1.577327] logger: created 256K log 'log_main'
[    1.582363] logger: created 256K log 'log_events'
[    1.587701] logger: created 256K log 'log_radio'
[    1.592803] logger: created 256K log 'log_system'
missing output
[    1.600106] TCP: cubic registered
[    1.603776] NET: Registered protocol family 10
[    1.609549] NET: Registered protocol family 17




BBB:
[    1.963408] usbhid: USB HID core driver
[    1.968565] ashmem: initialized
[    1.972295] logger: created 256K log 'log_main'
[    1.977338] logger: created 256K log 'log_events'
[    1.982576] logger: created 256K log 'log_radio'
[    1.987699] logger: created 256K log 'log_system'
[    1.992702] usb usb1: usb wakeup-resume
[    1.992745] usb usb1: usb auto-resume
[    1.992768] hub 1-0:1.0: hub_resume
[    1.992808] hub 1-0:1.0: port 1: status 0101 change 0001
[    1.995817] TCP: cubic registered
[    1.999469] NET: Registered protocol family 10
[    2.005445] NET: Registered protocol family 17

So, my question is what would trigger the USB drivers to skip the steps
that generate the 4 output messages above? Or, what source file would I
look at to determine what conditions would prevent the drivers from
proceeding and displaying the above messages?

Any suggestions would be greatly appreciated.
In your kernel source folder, issue the following command:
git grep cubic

The missing ouput is:

[    1.992702] usb usb1: usb wakeup-resume
[    1.992745] usb usb1: usb auto-resume
[    1.992768] hub 1-0:1.0: hub_resume
[    1.992808] hub 1-0:1.0: port 1: status 0101 change 0001

Not the:

[    1.995817] TCP: cubic registered

Thanks for the idea though..
Ross

There are only a few references so it should be easy for you to determine why this doesnšt happen. Regards, John
Once again, with 3.15 our hardware and USB works perfect.

Thanks,

Ross

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


--
For more options, visit http://beagleboard.org/discuss
--- You received this message because you are subscribed to the Google Groups "BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to