All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Jellinghaus <aj@leogic.com>
To: Con Kolivas <kernel@kolivas.org>
Cc: linux-kernel@vger.kernel.org, linux-usb-devel@lists.sourceforge.net
Subject: rsdl 30 on 2.6.20.2 breaks user space usb
Date: Thu, 15 Mar 2007 10:54:29 +0100	[thread overview]
Message-ID: <200703151054.29591.aj@leogic.com> (raw)

with plain 2.6.20.2 I get events / called from udev for /proc/bus/usb devices.
with rsdl 0.30 added to the kernel I no longer get called for those devices
(but I do get called for the new /dev/usbdev devices - except that I can't use 
them).

any idea why and what to do? might be related to a race condition.

I can also provide kernel config, dmesg, etc. whatever.
system is x86 with ubuntu edgy installed. I noticed the problem
with openct - the udev helper doesn't get spawned with the rsdl
kernel, while it does get spawned with the normal kernel.

Regards, Andreas

             reply	other threads:[~2007-03-15 10:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-15  9:54 Andreas Jellinghaus [this message]
2007-03-15 10:25 ` rsdl 30 on 2.6.20.2 breaks user space usb Serge Belyshev
2007-03-15 10:53   ` Andreas Jellinghaus

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200703151054.29591.aj@leogic.com \
    --to=aj@leogic.com \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.