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 CO
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
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
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:
driv
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
