Re: [linux-usb-devel] [PATCH] USB: Only enable autosuspend by default on certain device classes

2007-08-03 Thread Adam Kropelin
Dave Jones wrote: On Fri, Aug 03, 2007 at 05:31:52PM +0200, Jiri Kosina wrote: Plus if you're connected to such a device for monitoring purposes you're probably powered by it as well, so you have little to gain from suspend even if it works. I currently don't have any HID UPS by hand to verif

Re: [linux-usb-devel] [PATCH] USB: Only enable autosuspend by default on certain device classes

2007-08-03 Thread Adam Kropelin
Dave Jones wrote: On Fri, Aug 03, 2007 at 04:43:16PM +0200, Jiri Kosina wrote: On Fri, 3 Aug 2007, Matthew Garrett wrote: Windows will autosuspend hubs, bluetooth devices, HID devices Hi Matthew, are you sure about windows suspending the HID devices in runtime? I have never seen LEDs of USB

Re: [1/3] 2.6.23-rc1: known regressions with patches v3

2007-07-30 Thread Adam Kropelin
PS Monitoring Problems References : http://lkml.org/lkml/2007/7/27/334 Last known good : 2.6.20.6 Submitter : Nick Pasich <[EMAIL PROTECTED]> Caused-By : Handled-By : Adam Kropelin <[EMAIL PROTECTED]> Patch : http://lkml.org/lkml/2007/7/29/164 Status

[PATCH] usb-serial: Fix edgeport regression on non-EPiC devices

2007-07-29 Thread Adam Kropelin
Fix serious regression on non-EPiC edgeport usb-serial devices. Baud rate and MCR/LCR registers are not being written on these models due to apparent copy-n-paste errors introduced with EPiC support. Failure reported by Nick Pasich <[EMAIL PROTECTED]>. Signed-off-by: Adam Kropelin &

Re: [linux-usb-devel] Edgeport UPS Monitoring Problems

2007-07-29 Thread Adam Kropelin
From: "Nick Pasich" <[EMAIL PROTECTED]> Here's the dmesg output .. [...] Jul 29 05:20:07 NICK2 kernel: drivers/usb/serial/io_edgeport.c: LCR - write to send_cmd_write_uart_register register 0x03 Jul 29 05:20:07 NICK2 kernel: drivers/usb/serial/io_edgeport.c: SendCmdWriteUartReg - Not writi

Re: [linux-usb-devel] Edgeport UPS Monitoring Problems

2007-07-28 Thread Adam Kropelin
Andrew Morton wrote: On Fri, 27 Jul 2007 13:37:08 -0700 Nick Pasich <[EMAIL PROTECTED]> wrote: Greg/Peter/Al, added linux-usb-devel. I've been using the edgeport 4 port USB to Serial Converter to monitor APC Smart UPS's via apcupsd for quite awhile on various Linux boxes. I just upgraded

Re: [linux-usb-devel] [RFC] HID bus design overview.

2007-04-05 Thread Adam Kropelin
Jiri Kosina wrote: On Wed, 4 Apr 2007, Adam Kropelin wrote: On Apcupsd we've recently introduced a libusb-based driver that does all HID parsing in userspace. Not only does that free us from hiddev, it also frees us from the umpteen other proprietary HID interfaces across various plat

Re: [linux-usb-devel] [RFC] HID bus design overview.

2007-04-04 Thread Adam Kropelin
Jiri Kosina wrote: On Wed, 4 Apr 2007, Adam Kropelin wrote: I apologize for picking up this thread late and asking what may be a question with an obvious answer... Will hiddev still exist after hidraw and the HID bus redesign work is done? I have a widely-deployed userspace app that relies on

Re: [linux-usb-devel] [RFC] HID bus design overview.

2007-04-04 Thread Adam Kropelin
Jiri Kosina wrote: On Tue, 3 Apr 2007, Li Yu wrote: What's the position of hidraw? It only is used when all other driver is not usable on some report? or, it should be stick every working device. Current implementation (as you can see it in -mm or in my hid.git tree) is creating hidraw interf

Re: 2.6.20-rc7: known regressions (v2) (part 1)

2007-02-03 Thread Adam Kropelin
Eric W. Biederman wrote: "Adam Kropelin" <[EMAIL PROTECTED]> writes: Can I get the corresponding lspci -xxx output. I suspect the BIOS did not program the hypertransport MSI mapping capabilities correctly. All it has to do is set the enable but still, occasionally BIOS write

Re: 2.6.20-rc7: known regressions (v2) (part 1)

2007-02-03 Thread Adam Kropelin
Eric W. Biederman wrote: Auke Kok <[EMAIL PROTECTED]> writes: maybe I've been unclear, but here's how e1000 detects link changes: 1) by checking every 2 seconds in the watchdog by reading PHY registers 2) by receiving an interrupt from the NIC with the LSI bit in the interrupt control register

Re: 2.6.20-rc7: known regressions (v2) (part 1)

2007-02-03 Thread Adam Kropelin
Auke Kok wrote: Adam Kropelin wrote: I've never had this device work 100% with MSI on any kernel version I've tested so far. But I'm not the original reporter of the problem, and I believe for him it was a true regression where a previous kernel wored correctly. maybe I'

Re: 2.6.20-rc7: known regressions (v2) (part 1)

2007-02-03 Thread Adam Kropelin
Eric W. Biederman wrote: Auke Kok <[EMAIL PROTECTED]> writes: None of the MSI code in e1000 has changed significantly either. as far as I can see, the msi code in e1000 has not changed since 2.6.18. Nonetheless there's no way I can debug any of this without a system. [...] Perhaps Adam can git-b

Re: MSI failure on nForce 430 (WAS: intel 82571EB gigabit fails to see link on 2.6.20-rc5 in-tree e1000 driver (regression))

2007-02-02 Thread Adam Kropelin
On Fri, Feb 02, 2007 at 09:25:38AM -0800, Auke Kok wrote: > Adrian Bunk wrote: > > On Sat, Jan 20, 2007 at 02:34:37PM -0500, Adam Kropelin wrote: > >> (cc: list trimmed and thread moved to linux-pci) > >> > >> I have a PCI-E e1000 card that does not see i

Re: MSI failure on nForce 430 (WAS: intel 82571EB gigabit fails to see link on 2.6.20-rc5 in-tree e1000 driver (regression))

2007-01-20 Thread Adam Kropelin
Adam Kropelin wrote: I've attached the contents dmesg, 'lspci -vvv', and 'cat /proc/interrupts' from 2.6.20-rc5. Actually attached this time. --Adam proc-irq-2.6.20-rc5 Description: Binary data dmesg-2.6.20-rc5 Description: Binary data lspci-2.6.20-rc5 Description: Binary data

MSI failure on nForce 430 (WAS: intel 82571EB gigabit fails to see link on 2.6.20-rc5 in-tree e1000 driver (regression))

2007-01-20 Thread Adam Kropelin
(cc: list trimmed and thread moved to linux-pci) I have a PCI-E e1000 card that does not see interrupts on 2.6.20-rc5 unless CONFIG_PCI_MSI is disabled. An e1000 maintainer indicated that the PHY state is correct, it's just that the interrupt is not getting thru to the kernel. Interestingly, o

Re: intel 82571EB gigabit fails to see link on 2.6.20-rc5 in-tree e1000 driver (regression)

2007-01-19 Thread Adam Kropelin
Auke Kok wrote: Adam Kropelin wrote: I haven't been able to test rc5-mm yet because it won't boot on this box. Applying git-e1000 directly to -rc4 or -rc5 results in a number of rejects that I'm not sure how to fix. Some are obvious, but the others I'm unsure of. that wo

Re: intel 82571EB gigabit fails to see link on 2.6.20-rc5 in-tree e1000 driver (regression)

2007-01-19 Thread Adam Kropelin
Auke Kok wrote: Adam Kropelin wrote: I am experiencing the no-link issue on a 82572EI single port copper PCI-E card. I've only tried 2.6.20-rc5, so I cannot tell if this is a regression or not yet. Will test older kernel soon. Can provide details/logs if you want 'em. we&

Re: intel 82571EB gigabit fails to see link on 2.6.20-rc5 in-tree e1000 driver (regression)

2007-01-17 Thread Adam Kropelin
> Allen Parker wrote: >> Allen Parker wrote: >>> From what I've been able to gather, other Intel Pro/1000 chipsets >>> work fine in 2.6.20-rc5. If the e1000 guys need any assistance >>> testing, I'll be more than happy to volunteer myself as a guinea pig >>> for patches. >> >> I wasn't aware t

Re: [2.6 patch] drivers/block/nbd.c: don't defer compile error to runtime

2005-09-02 Thread Adam Kropelin
Adrian Bunk wrote: > If we can detect a problem at compile time, the compilation should > fail. [...] > if (sizeof(struct nbd_request) != 28) { > - printk(KERN_CRIT "nbd: sizeof nbd_request needs to be 28 in > order to work!\n" ); > - return -EIO; > + e

Re: [linux-usb-devel] [PATCH] hiddev: output reports are dropped when HIDIOCSREPORT is called in short succession

2005-08-22 Thread Adam Kropelin
Stefan Nickl wrote: Hi, when trying to make the hiddev driver issue several Set_Report control transfers to a custom device with 2.6.13-rc6, only the first transfer in a row is carried out, while others immediately following it are silently dropped. This happens where hid_submit_report() (in hi

Re: [patch] inotify for 2.6.11

2005-04-05 Thread Adam Kropelin
I've been meaning to play with inotify for a while now and finally made time for it tonight. I'm not much of a GUI guy, so I'm mostly interested in exploring the command line applications of inotify --i.e., what sort of havoc can I wreak with it in a script. To that end I sat down tonight a threw

Re: [RFQ] Rules for accepting patches into the linux-releases tree

2005-03-06 Thread Adam Kropelin
Andres Salomon <[EMAIL PROTECTED]> wrote: > On Sat, 05 Mar 2005 11:43:05 +0100, Andries Brouwer wrote: > > On Fri, Mar 04, 2005 at 02:21:46PM -0800, Greg KH wrote: > >> - It must fix a real bug that bothers people (not a, "This could be a > >>problem..." type thing.) > > An obvious fix is an o

Re: Does kernel require IDE enabled in BIOS to access HD, FS errors?

2001-07-08 Thread Adam Kropelin
Jim Roland said: >I expect someone will rebut my comments about the kernel (which is fine, I'm >not a Kernel hacker Okay, I'll take the bait, but I'm not a kernel hacker, either, so someone should feel free to rebut *my* comments as well. >but it is my understanding that the kernel uses your s