|
From: | Srinivas Bakki |
Subject: | [Ltib] RE: Sierra 3G modem not working on Phytec Board. (missing USB End Points, only ep00,ep01,ep81 created.) |
Date: | Thu, 15 Jul 2010 08:06:36 +0200 |
Hi Quentin, Just run"cvs update" in your ltib
directory. It'll fetch the updates and in the ltib config you can see the
2.6.34 kernel support. Let me know if you have any problems further. Regards Srinivas Bakki From: Quentin Yang
[mailto:address@hidden Hi Srinivas, Thanks for the reply. I think I’ve enabled USB debug. As in
\ltib-qs\rpm\BUILD\linux-2.6.27.8\.config, I can see “ # #
USB Input Devices # CONFIG_USB_HID=y #
CONFIG_USB_HIDINPUT_POWERBOOK is not set #
CONFIG_HID_FF is not set #
CONFIG_USB_HIDDEV is not set CONFIG_USB_SUPPORT=y CONFIG_USB_ARCH_HAS_HCD=y CONFIG_USB_ARCH_HAS_OHCI=y #
CONFIG_USB_ARCH_HAS_EHCI is not set CONFIG_USB=y CONFIG_USB_DEBUG=y CONFIG_USB_ANNOUNCE_NEW_DEVICES=y ” Also, in ‘
\ltib-qs\rpm\BUILD\linux-2.6.27.8\include\linux\autoconf.h ‘ #define
CONFIG_USB_DEBUG 1 But from the attached ‘console print’ from Phytec board UART5? (Phytec_Console_Log_Missing_UsbDebugMessage.txt) I cannot see any ‘usb-debug’ message. I’ll keep working on this and
get back to you soon. One thing noticeable in the log is: ‘usbmon:
debugfs is not available’ I don’t know why is this??
Seems again to do with File System. --------------------------------------- I am quite new to LTIB. But when I installed LTIB by ‘netinstall’, all kernel 2.6.27.8
source codes turned up automatically under ‘\ltib-qs\rpm\BUILD\linux-2.6.27.8\’
because I chose ‘Leave Kernel Source After build’. In ‘ \ltib-qs\config\platform\phy3250\defconfig.dev ‘ # #
Choose your Kernel # CONFIG_PHY_KERNEL_2_6_27_8=y #
CONFIG_KERNEL_DIR_BUILD is not set #
CONFIG_KERNEL_NONE is not set CONFIG_PKG_KERNEL="kernel-2.6.27.8-lpc32xx" CONFIG_PKG_KERNEL_FORCE=y #
CONFIG_PKG_KERNEL_WANT_CSCOPE is not set CONFIG_PKG_KERNEL_PRECONFIG="GsnKernelPreConfig.config" CONFIG_PKG_KERNEL_WANT_HEADERS=y CONFIG_PKG_KERNEL_WANT_CF=y CONFIG_PKG_KERNEL_LEAVESRC=y CONFIG_SYSCFG_KTARG="uImage" CONFIG_SYSCFG_BOOT_KERNEL="arch/arm/boot/uImage" CONFIG_DISTRO="dist/lfs-5.1" Regarding your suggestion, all lpc3250 patches appear to target
kernel 2.6.27.8, can I use these patches on Linux 2.6.34 ? I
can see \ltib-qs\dist\lfs-5.1\kernel\kernel-2.6.27.8-lpc32xx.spec.in \ltib-qs\dist\lfs-5.1\kernel\kernel-2.6.28.2-lpc313x.spec.in \ltib-qs\dist\lfs-5.1\kernel\kernel-2.6.33-lpc313x.spec.in Lpc313x
got patches for both 2.6.28.2 and 2.6.33 kernel. As attached screen shot, to use Kernel 2.6.34, it looks the only
choice is to choose ‘( ) Local Linux Directory Build’. PLEASE ADVISE WHAT I NEED TO DO TO USE KERNEL 2.6.34 ON Phytec
board? Thanks. LTIB is very new to me at the moment. ---------------Some Info about my current Phytec Linux Build
------------------------------- ‘ linux-2.6.27.8-lpc32xx_full_10_15_09.patch ’ is the patch
that can be downloaded from http://ics.nxp.com/support/software/lpc32xx.bsp.linux/ But, in real, following patches under ‘ \ltib-qs\rpm\SOURCES\ ’
were used when building Phytec Linux Image with LTIB: kernel-arm-2.6.27.8-lpc32xx_8250irqfix.patch kernel-arm-2.6.27.8-lpc32xx_armtskit_update2.patch kernel-arm-2.6.27.8-lpc32xx_dktskit_update3.patch kernel-arm-2.6.27.8-lpc32xx_ea3250.patch kernel-arm-2.6.27.8-lpc32xx_ea3250_update1.patch kernel-arm-2.6.27.8-lpc32xx.patch kernel-arm-2.6.27.8-lpc32xx_update2.patch kernel-arm-2.6.27.8-lpc32xx_update3.patch kernel-arm-2.6.27.8-lpc32xx_update4.patch kernel-arm-2.6.27.8-lpc32xx_update5.patch kernel-arm-2.6.27.8-lpc32xx_update6.patch kernel-arm-2.6.27.8-lpc32xx_update7.patch kernel-arm-2.6.27.8-update1.patch Together with 2.6.27.8 Kernel \ltib-qs\rpm\SOURCES\linux-2.6.27.8.tar.bz2 Are these patches the same, ‘
linux-2.6.27.8-lpc32xx_full_10_15_09.patch ‘ is just a combination of all
patches under ‘\ltib-qs\rpm\SOURCES\’ ?? Best Regards, Quentin From: Srinivas Bakki
[mailto:address@hidden Hi Quentino,
I had a look at the sysfs tree and am not sure why other endpoint files are not
being created. I would need more information to proceed : enable USB debugs and send me the logs. I would
want to look at the enumeration process. Other things you could try - Update to linux 2.6.34 ( present in
ltib) which already has MC8790 support built in. Regards Srinivas Bakki From: Quentin YANG
[mailto:address@hidden Hi Srinivas, On Tue, Jul 13, 2010 at 6:52 PM, Srinivas Bakki <address@hidden>
wrote: Hi Quentin,
Find my response below. Regards Srinivas Bakki From:
Quentin YANG [mailto:address@hidden]
Hi
Srinivas, Do not worry about the /proc/bus/usb
file not found problem. It is there only if you need to access descriptors from
the user space.
I'll have a look at this and get back
soon. Meantime can you send me your sysfs entries for usb ? Both on linux PC
and phytec. So I
think the PROBLEM IS WITH "pnx4008 OHCI" DRIVER, which I guess is the
routine to create USB endpoints. The endpoints files are created by the
kernel NOT the " "pnx4008 OHCI DRIVER ". When the hub succesfully enumerates the device
i.e reads the descriptors and configures the device, the endpoint files are
created.
On
Mon, Jul 12, 2010 at 2:04 PM, Srinivas Bakki <address@hidden>
wrote: Hi Quentin,
Can you try running "mdev -s" after you insert usbserial
and sierra mdules ? Regards Srinivas Bakki From:
ltib-bounces+srinivas.bakki=nxp.com@nongnu.org [mailto:ltib-bounces+srinivas.bakki=nxp.com@nongnu.org] On Behalf Of Quentin YANG Hi, |
[Prev in Thread] | Current Thread | [Next in Thread] |