[linux-usb-devel] Re: 2.4.22-pre10 compile failure USB HID
Greg KH wrote: On Fri, Aug 01, 2003 at 12:31:24PM -0700, Samuel Flory wrote: I'm seeing a linking issue when I compile USB HID support directly into the kernel. Looking at my kernel config it looks like it might have something to do with the fact that I'm compiling CONFIG_INPUT, CONFIG_INPUT_KEYBDEV, and CONFIG_INPUT_MOUSEDEV as modules. Should CONFIG_USB_HID depend on one, or all of the above. Yes, that configuration will not work. I think this has been discussed many times on the lists in the past, and the end agreement is, "Don't try to do that." :) It's not an easy configuration language fix from what I remember. I'll take a look it. It seems to work if you compile in the rest of the HID stuff. -- Once you have their hardware. Never give it back. (The First Rule of Hardware Acquisition) Sam Flory <[EMAIL PROTECTED]> --- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa0013ave/direct;at.aspnet_072303_01/01 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] 2.4.22-pre10 compile failure USB HID
I'm seeing a linking issue when I compile USB HID support directly into the kernel. Looking at my kernel config it looks like it might have something to do with the fact that I'm compiling CONFIG_INPUT, CONFIG_INPUT_KEYBDEV, and CONFIG_INPUT_MOUSEDEV as modules. Should CONFIG_USB_HID depend on one, or all of the above. ld -m elf_i386 -T /stuff/src/linux-2.4.22-pre10/arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o init/version.o init/do_mounts.o \ --start-group \ arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o \ drivers/acpi/acpi.o drivers/char/char.o drivers/block/block.o drivers/misc/misc.o drivers/net/net.o drivers/net/fc/fc.o drivers/net/appletalk/appletalk.o drivers/atm/atm.o drivers/ide/idedriver.o drivers/scsi/scsidrv.o drivers/message/fusion/fusion.o drivers/cdrom/driver.o drivers/pci/driver.o drivers/net/pcmcia/pcmcia_net.o drivers/video/video.o drivers/usb/usbdrv.o drivers/media/media.o drivers/md/mddev.o \ net/network.o \ /stuff/src/linux-2.4.22-pre10/arch/i386/lib/lib.a /stuff/src/linux-2.4.22-pre10/lib/lib.a /stuff/src/linux-2.4.22-pre10/arch/i386/lib/lib.a \ --end-group \ -o vmlinux drivers/usb/usbdrv.o(.text+0x1dd9b): In function `hidinput_hid_event': : undefined reference to `input_event' drivers/usb/usbdrv.o(.text+0x1de1d): In function `hidinput_hid_event': : undefined reference to `input_event' drivers/usb/usbdrv.o(.text+0x1de7c): In function `hidinput_hid_event': : undefined reference to `input_event' drivers/usb/usbdrv.o(.text+0x1defc): In function `hidinput_hid_event': : undefined reference to `input_event' drivers/usb/usbdrv.o(.text+0x1e0c8): In function `hidinput_connect': : undefined reference to `input_register_device' drivers/usb/usbdrv.o(.text+0x1e0e2): In function `hidinput_connect': : undefined reference to `input_register_device' drivers/usb/usbdrv.o(.text+0x1e247): In function `hidinput_disconnect': : undefined reference to `input_unregister_device' drivers/usb/usbdrv.o(.text+0x1dde0): In function `hidinput_hid_event': : undefined reference to `input_event' make: *** [vmlinux] Error 1 -- Once you have their hardware. Never give it back. (The First Rule of Hardware Acquisition) Sam Flory <[EMAIL PROTECTED]> # # Automatically generated make config: don't edit # CONFIG_X86=y # CONFIG_SBUS is not set CONFIG_UID16=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # Loadable module support # CONFIG_MODULES=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # Processor type and features # # CONFIG_M386 is not set # CONFIG_M486 is not set # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set CONFIG_MPENTIUMIII=y # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MELAN is not set # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y # CONFIG_RWSEM_GENERIC_SPINLOCK is not set CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_X86_L1_CACHE_SHIFT=5 CONFIG_X86_HAS_TSC=y CONFIG_X86_GOOD_APIC=y CONFIG_X86_PGE=y CONFIG_X86_USE_PPRO_CHECKSUM=y CONFIG_X86_F00F_WORKS_OK=y CONFIG_X86_MCE=y # CONFIG_TOSHIBA is not set # CONFIG_I8K is not set # CONFIG_MICROCODE is not set # CONFIG_X86_MSR is not set # CONFIG_X86_CPUID is not set # CONFIG_NOHIGHMEM is not set # CONFIG_HIGHMEM4G is not set CONFIG_HIGHMEM64G=y CONFIG_HIGHMEM=y CONFIG_X86_PAE=y CONFIG_HIGHIO=y # CONFIG_MATH_EMULATION is not set CONFIG_MTRR=y CONFIG_SMP=y # CONFIG_X86_NUMA is not set # CONFIG_X86_TSC_DISABLE is not set CONFIG_X86_TSC=y CONFIG_HAVE_DEC_LOCK=y # # General setup # CONFIG_NET=y CONFIG_X86_IO_APIC=y CONFIG_X86_LOCAL_APIC=y CONFIG_PCI=y # CONFIG_PCI_GOBIOS is not set # CONFIG_PCI_GODIRECT is not set CONFIG_PCI_GOANY=y CONFIG_PCI_BIOS=y CONFIG_PCI_DIRECT=y CONFIG_ISA=y CONFIG_PCI_NAMES=y CONFIG_EISA=y # CONFIG_MCA is not set CONFIG_HOTPLUG=y # # PCMCIA/CardBus support # CONFIG_PCMCIA=m CONFIG_CARDBUS=y CONFIG_TCIC=y CONFIG_I82092=y CONFIG_I82365=y # # PCI Hotplug Support # # CONFIG_HOTPLUG_PCI is not set # CONFIG_HOTPLUG_PCI_COMPAQ is not set # CONFIG_HOTPLUG_PCI_COMPAQ_NVRAM is not set # CONFIG_HOTPLUG_PCI_IBM is not set # CONFIG_HOTPLUG_PCI_ACPI is not set CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_KCORE_ELF=y # CONFIG_KCORE_AOUT is not set # CONFIG_BINFMT_AOUT is not set CONFIG_BINFMT_ELF=y # CONFIG_BINFMT_MISC is not set CONFIG_PM=y CONFIG_APM=m # CONFIG_APM_IGNORE_USER_SUSPEND is not set # CONFIG_APM_DO_ENABLE is not set # CONFIG_APM_CPU_IDLE is not set # CONFIG_APM_DISPLAY_BLANK is not set # CONFIG_APM_RTC_IS_GMT is not set # CONFIG_APM_ALLOW_INTS is not set # CONFIG_APM_REAL_MODE_POWER_OFF is
[linux-usb-devel] Re: USB serial
Greg KH wrote: and you should be fine. On Wed, May 28, 2003 at 02:22:55PM -0700, Samuel Flory wrote: I seem to be getting a lot of the following in dmesg: drivers/usb/serial/usb-serial.c: serial_write - port 0, 1 byte(s) drivers/usb/serial/keyspan.c: keyspan_write - for port 0 (1 chars), flip=1 drivers/usb/serial/keyspan.c: keyspan_write - endpoint 2 flip 1 drivers/usb/serial/keyspan.c: usb_submit_urb(write bulk) failed (-19) Are you sure you are trying to write to a USB device that is still present in the system? That error (-ENODEV) would indicate otherwise... It may have been bumped loose as I can't get the errors any more. On the plus side everything works if I turn off hardware flow control in minicom. -- There is no such thing as obsolete hardware. Merely hardware that other people don't want. (The Second Rule of Hardware Acquisition) Sam Flory <[EMAIL PROTECTED]> --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Re: USB serial
Samuel Flory wrote: It appears that I can recieve fine. If I `echo "Can you see" >/dev/ttyS1 on the system that I'm connected to. I can see this in minicom. It seems to be sending stuff out that is the issue. I seem to be getting a lot of the following in dmesg: drivers/usb/serial/usb-serial.c: serial_write - port 0, 1 byte(s) drivers/usb/serial/keyspan.c: keyspan_write - for port 0 (1 chars), flip=1 drivers/usb/serial/keyspan.c: keyspan_write - endpoint 2 flip 1 drivers/usb/serial/keyspan.c: usb_submit_urb(write bulk) failed (-19) drivers/usb/serial/usb-serial.c: serial_tiocmget - port 0 drivers/usb/serial/usb-serial.c: serial_chars_in_buffer = port 0 drivers/usb/serial/usb-serial.c: serial_chars_in_buffer = port 0 drivers/usb/serial/usb-serial.c: serial_write - port 0, 1 byte(s) drivers/usb/serial/keyspan.c: keyspan_write - for port 0 (1 chars), flip=0 drivers/usb/serial/keyspan.c: keyspan_write - endpoint 1 flip 0 drivers/usb/serial/keyspan.c: usb_submit_urb(write bulk) failed (-19) Ps- This is under 2.5.70 now. -- There is no such thing as obsolete hardware. Merely hardware that other people don't want. (The Second Rule of Hardware Acquisition) Sam Flory <[EMAIL PROTECTED]> --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
[linux-usb-devel] Re: USB serial
Greg KH wrote: On Fri, May 23, 2003 at 10:08:07AM -0700, Samuel Flory wrote: Under 2.5.69-bk6 the kernel sees both the keyspan, and iogear (PL-2303) and assigns ttyUSB. Minicom will open the port, but I don't see anything in response to my key strokes. Is the flow control and other line settings set up properly in minicom for you? The data should be flowing. You can load the drivers with "debug=1" to see the data in the kernel debug log if you have any questions about that. It appears that I can recieve fine. If I `echo "Can you see" >/dev/ttyS1 on the system that I'm connected to. I can see this in minicom. It seems to be sending stuff out that is the issue. I seem to be getting a lot of the following in dmesg: drivers/usb/serial/usb-serial.c: serial_write - port 0, 1 byte(s) drivers/usb/serial/keyspan.c: keyspan_write - for port 0 (1 chars), flip=1 drivers/usb/serial/keyspan.c: keyspan_write - endpoint 2 flip 1 drivers/usb/serial/keyspan.c: usb_submit_urb(write bulk) failed (-19) drivers/usb/serial/usb-serial.c: serial_tiocmget - port 0 drivers/usb/serial/usb-serial.c: serial_chars_in_buffer = port 0 drivers/usb/serial/usb-serial.c: serial_chars_in_buffer = port 0 drivers/usb/serial/usb-serial.c: serial_write - port 0, 1 byte(s) drivers/usb/serial/keyspan.c: keyspan_write - for port 0 (1 chars), flip=0 drivers/usb/serial/keyspan.c: keyspan_write - endpoint 1 flip 0 drivers/usb/serial/keyspan.c: usb_submit_urb(write bulk) failed (-19) drivers/usb/serial/usb-serial.c: serial_tiocmget - port 0 drivers/usb/serial/usb-serial.c: serial_chars_in_buffer = port 0 drivers/usb/serial/usb-serial.c: serial_chars_in_buffer = port 0 drivers/usb/serial/usb-serial.c: serial_write - port 0, 1 byte(s) drivers/usb/serial/keyspan.c: keyspan_write - for port 0 (1 chars), flip=1 drivers/usb/serial/keyspan.c: keyspan_write - endpoint 2 flip 1 drivers/usb/serial/keyspan.c: usb_submit_urb(write bulk) failed (-19) -- There is no such thing as obsolete hardware. Merely hardware that other people don't want. (The Second Rule of Hardware Acquisition) Sam Flory <[EMAIL PROTECTED]> --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
