On Tuesday 02 May 2006 10:06 pm, Michael Helmling wrote:
> > Was it you who removed the copyrights from the "usbnet" driver and
> > changed the author assertion to one "M Subrahmanya Srihdar" ??
> > I'm guessing the latter; the www.moschip.com site implies that
> > its engineering HW is in India.
On Wednesday 03 May 2006 00:09, David Brownell wrote:
> On Tuesday 02 May 2006 11:02 am, Michael Helmling wrote:
> > Hi all,
> >
> > I bought an USB-Ethernet adaptor from delock (www.delock.de) and found it
was
> > not supported by linux from the vendor. So I played a little with lsusb
and
> >
On Tuesday 02 May 2006 5:36 pm, Randy Vinson wrote:
> Greetings,
> I performing some testing, I noticed that I am not prevented from removing
> the
> ehci_hcd module even though the system has drives mounted via ehci_hcd.
> Before
> I start down the path of reporting a BUG, I thought I'd c
On Tue, 02 May 2006 17:36:09 -0700, Randy Vinson <[EMAIL PROTECTED]> wrote:
> This problem was found while executing a "reboot" command with
> a USB floppy drive or a USB hard drive mounted. The hotplug scripts
> were unloading the ehci_hcd module before unmounting the drives.
> This resulted in
Greetings,
I performing some testing, I noticed that I am not prevented from removing the
ehci_hcd module even though the system has drives mounted via ehci_hcd. Before
I start down the path of reporting a BUG, I thought I'd check if this is a
known issue. A quick Google search didn't show any
Randy.Dunlap wrote:
On Tue, 02 May 2006 12:47:20 -0700 Mark McClelland wrote:
Randy.Dunlap wrote:
I downloaded 2.32 and tested it on my ibot2. All that I see is a
kernel log message that says:
/home/rdunlap/builds/ov511-2.32/ovfx2.c: No sensor is detected yet
any time that a viewer app tries
David Hollis wrote:
> That's a good demonstration of testing code before you send it out! I
> meant to move that block that checks the PHY ID below the part where I
> actually read the PHY address but I didn't so it was reading from the
> wrong place. The attached patch seems to behave fine on x8
On Tue, 02 May 2006 12:47:20 -0700 Mark McClelland wrote:
> Randy.Dunlap wrote:
> > I downloaded 2.32 and tested it on my ibot2. All that I see is a
> > kernel log message that says:
> > /home/rdunlap/builds/ov511-2.32/ovfx2.c: No sensor is detected yet
> > any time that a viewer app tries to ope
On Tuesday 02 May 2006 11:02 am, Michael Helmling wrote:
> Hi all,
>
> I bought an USB-Ethernet adaptor from delock (www.delock.de) and found it was
> not supported by linux from the vendor. So I played a little with lsusb and
> found it uses a MCS7830 chip from MosChip semiconductor (moschip.co
Am Dienstag, 2. Mai 2006 22:40 schrieb Ioan Ionita:
> > usb 2-10: new high speed USB device using ehci_hcd and address 5
> > usb 2-10: configuration #1 chosen from 1 choice
> >
> > But no eth1 shows up, and module loading and plugging the device seem to be
> > independent. I manually loaded usbnet
On Tue, May 02, 2006 at 01:42:46PM -0700, Pete Zaitcev wrote:
> However, absent libusual, ub will happily try to drive devices with
> phantom LUNs, devices reporting wrong size, devices choking on INQUIRY -
> with varying degree of success. I imagine that for an arcade, most
> of this makes no diff
At 16:52 02.05.2006, Alan Stern wrote:
On Tue, 2 May 2006, Sancho Dauskardt wrote:
>
> when heavily pollig usb-storage devices with a TEST_UNIT_READY
> command and then removing the device occasionally causes an Oops
near khubd.
> Tried on Kernel 2.6.11.1 and 2.6.16.11.
...
From your logs,
Am Dienstag 02 Mai 2006 22:40 schrieb Ioan Ionita:
> On 5/2/06, Michael Helmling <[EMAIL PROTECTED]> wrote:
> > Thank you very much for the immediate answer.
> > I applied the patch - well, I had to do this manually, for some reason, I
> > assume bad formatting in my mail program, patch -p0 < pa
On Tue, 2 May 2006 15:39:49 -0400, Glenn Maynard <[EMAIL PROTECTED]> wrote:
> Sorry for the silly question, but: if this has to be specified explicitly
> for devices in unusual_devs, why does it not for ordinary devices (which
> aren't in unusual_devs)? That is, why can't this flag be derived (fr
On 5/2/06, Michael Helmling <[EMAIL PROTECTED]> wrote:
Thank you very much for the immediate answer.
I applied the patch - well, I had to do this manually, for some reason, I
assume bad formatting in my mail program, patch -p0 < patch1 didn't work. Or
am I using the wrong command?
You shoud us
Randy.Dunlap wrote:
I downloaded 2.32 and tested it on my ibot2. All that I see is a
kernel log message that says:
/home/rdunlap/builds/ov511-2.32/ovfx2.c: No sensor is detected yet
any time that a viewer app tries to open the device.
You probably just need to modprobe ovcamchip. It doesn't ge
On Mon, May 01, 2006 at 11:33:09PM -0700, Pete Zaitcev wrote:
> On Mon, 01 May 2006 23:00:52 -0700, Phil Dibowitz <[EMAIL PROTECTED]> wrote:
>
> > So what criteria did you use to decide whether to set it to
> > USB_US_TYPE_STOR or "0"? I'm assuming 0 means usb-storage?
>
> No, zero means "runtime
Greg:
The choose_configuration() routine contains code the determine the
device's power source, so that configurations requiring external power can
be ruled out if the device is running on bus power. Unfortunately it
turns out that some devices have errors in their config descriptors and
othe
On 5/2/06, Michael Helmling <[EMAIL PROTECTED]> wrote:
I bought an USB-Ethernet adaptor from delock (www.delock.de) and found it was
not supported by linux from the vendor. So I played a little with lsusb and
found it uses a MCS7830 chip from MosChip semiconductor (moschip.com). On
their homepag
On Tue, 2 May 2006, Olaf Hering wrote:
> On Thu, Nov 17, Alan Stern wrote:
>
> > This patch (as605) removes the private udev->serialize semaphore, relying
> > instead on the locking provided by the embedded struct device's semaphore.
> > The changes are confined to the core, except that the u
Hi all,
I bought an USB-Ethernet adaptor from delock (www.delock.de) and found it was
not supported by linux from the vendor. So I played a little with lsusb and
found it uses a MCS7830 chip from MosChip semiconductor (moschip.com). On
their homepage I found a driver but it only was a precompil
On Mon, May 01, 2006 at 11:33:09PM -0700, Pete Zaitcev wrote:
> On Mon, 01 May 2006 23:00:52 -0700, Phil Dibowitz <[EMAIL PROTECTED]> wrote:
>
> > So what criteria did you use to decide whether to set it to
> > USB_US_TYPE_STOR or "0"? I'm assuming 0 means usb-storage?
>
> No, zero means "runtime
Peter Chubb wrote:
"Daniel" == Daniel Drake <[EMAIL PROTECTED]> writes:
Daniel> I'd accept a patch to hardcode the detection of HP8200 for the
Daniel> HP-id's, but leave the probe in place for the shared ID.
So here is the patch.
Use USB vendor and product IDs to determine whether the attach
On Thu, Apr 27, 2006 at 12:41:28PM -0700, David Brownell wrote:
> There does seem to be agreement that the current FREEE invocation is not
> sufficient. I'm looking at a slightly different solution now ... one which
> unfortunately involves changing drivers, but can indeed allow swsusp resume
> p
On Thu, Nov 17, Alan Stern wrote:
> This patch (as605) removes the private udev->serialize semaphore, relying
> instead on the locking provided by the embedded struct device's semaphore.
> The changes are confined to the core, except that the usb_trylock_device
> routine now uses the return c
On Mon, May 01, Alan Stern wrote:
> You could try running a 2.6.15 kernel with the clear_halt line removed.
This patch breaks it. I havent tried to put the code back into a 2.6.16 kernel.
.git/BISECT_LOG
git-bisect start
# good: [2b10839e32c4c476e9d94492756bb1a3e1ec4aa8] Linux v2.6.14
git-bise
Begin forwarded message:
Date: Tue, 2 May 2006 07:35:20 -0700
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Bugme-new] [Bug 6482] New: USB -UPS Problem on FC5
http://bugzilla.kernel.org/show_bug.cgi?id=6482
Summary: USB -UPS Problem on FC5
Kernel Version: FC 5 2.6.16-
On Tue, 2 May 2006, Sancho Dauskardt wrote:
> Hi all,
>
> when heavily pollig usb-storage devices with a TEST_UNIT_READY
> command and then removing the device occasionally causes an Oops near khubd.
> Tried on Kernel 2.6.11.1 and 2.6.16.11.
>
> To reproduce, run following on a multi-lun card
On Mon, 1 May 2006, Phil Dibowitz wrote:
> Heh. I have faith in you, Pete. =)
>
> So what criteria did you use to decide whether to set it to
> USB_US_TYPE_STOR or "0"? I'm assuming 0 means usb-storage? Maybe I'm
> just tired, but I don't see the code that uses this to make a decision
> on which
On Mon, 1 May 2006, Pete Zaitcev wrote:
> On Sat, 29 Apr 2006 17:49:40 -0700, Phil Dibowitz <[EMAIL PROTECTED]> wrote:
>
> > > Why just certain entries? Why not everything?
> > >
> > > It seems inconsistent (and an invitation for a zillion little patches) to
> > > only apply this to a select fe
On Mon, 1 May 2006, David Brownell wrote:
> I'd go for just removing all the "is it bus powered" logic, given that
> peripheral firmware doesn't seem to handle it reliably enough. A comment
> about those firmware bugs would be useful.
Okay.
> On Monday 01 May 2006, Alan Stern wrote:
> > Now the
On Mon, 1 May 2006, Pete Zaitcev wrote:
> On Mon, 24 Apr 2006 11:55:51 -0400 (EDT), Alan Stern <[EMAIL PROTECTED]>
> wrote:
>
> > Before submitting the patch, it seemed like a good idea to check with you
> > and make sure it doesn't cause any problems. I'd appreciate it if you
> > could try i
Make inputs pollable using sysfs_notify and add support for the Phidget
InterfaceKit 0/16/16. Various cleanups.
Signed-off-by: Sean Young <[EMAIL PROTECTED]>
Signed-off-by: Daniel Saakes <[EMAIL PROTECTED]>
--
--- linux-2.6.16/drivers/usb/misc/phidgetkit.c 2006-05-02 04:26:55.0
+0100
++
Hi all,
when heavily pollig usb-storage devices with a TEST_UNIT_READY
command and then removing the device occasionally causes an Oops near khubd.
Tried on Kernel 2.6.11.1 and 2.6.16.11.
To reproduce, run following on a multi-lun card-reader:
- snip
while [ 1 ]; do
sg_tu
34 matches
Mail list logo
