udev needs the following rule in order to create the correct device node for the Android phone. It works as a mass storage device without this, but won't work with the debugger, which looks for the right type of entry in /dev/bus/usb in order to detect devices. SUBSYSTEM=="usb",ATTR{idVendor}=="0bb4",ATTR{idProduct}=="0c02" Redhat asked that I report this upstream -- I hope this is the right bug tracker for udev. Ref: https://bugzilla.redhat.com/show_bug.cgi?id=468532
Reply-To: akpm@linux-foundation.org (switched to email. Please respond via emailed reply-to-all, not via the bugzilla web interface). On Tue, 28 Oct 2008 08:50:45 -0700 (PDT) bugme-daemon@bugzilla.kernel.org wrote: > http://bugzilla.kernel.org/show_bug.cgi?id=11874 > > Summary: udev rule for Android USB debugging > Product: Other > Version: 2.5 > KernelVersion: 2.6.27 > Platform: All > OS/Version: Linux > Tree: Mainline > Status: NEW > Severity: normal > Priority: P1 > Component: Other > AssignedTo: other_other@kernel-bugs.osdl.org > ReportedBy: luke.hutch@gmail.com > > > udev needs the following rule in order to create the correct device node for > the Android phone. It works as a mass storage device without this, but won't > work with the debugger, which looks for the right type of entry in > /dev/bus/usb > in order to detect devices. > > SUBSYSTEM=="usb",ATTR{idVendor}=="0bb4",ATTR{idProduct}=="0c02" > > Redhat asked that I report this upstream -- I hope this is the right bug > tracker for udev. Ref: https://bugzilla.redhat.com/show_bug.cgi?id=468532 Greg, to whom should Luke send a udev patch? Thanks.
On Tue, Oct 28, 2008 at 10:46:32AM -0700, Andrew Morton wrote: > > Greg, to whom should Luke send a udev patch? The udev team, which can be found at linux-hotplug@vger.kernel.org. kernel.org bugzilla is not for udev, sorry, I'll close this out.
On Tue, Oct 28, 2008 at 10:46:32AM -0700, Andrew Morton wrote: > > udev needs the following rule in order to create the correct device node > for > > the Android phone. It works as a mass storage device without this, but > won't > > work with the debugger, which looks for the right type of entry in > /dev/bus/usb > > in order to detect devices. > > > > SUBSYSTEM=="usb",ATTR{idVendor}=="0bb4",ATTR{idProduct}=="0c02" I really think this is not the correct thing to be doing here, but please bring it up on the linux-hotplug@vger.kernel.org mailing list, with full details of why this ruls is necessary (hint, I don't think it does anything...)
udev bugs are not for kernel.org
It doesn't look like the rule does anything, but the /dev/usb/###/### node is not created without the rule. Why would that be? Shouldn't device nodes always be created when a USB device is plugged in, whether or not the device is recognized by the system? I actually already sent an email to the address you specified already, and it bounced -- I just went back and re-read the bounce message and realized it was because HTML messages are automatically rejected [ :-) ], I just assumed the address didn't exist or something... I will re-send the email now, thanks! Luke On Tue, Oct 28, 2008 at 2:18 PM, Greg KH <greg@kroah.com> wrote: > On Tue, Oct 28, 2008 at 10:46:32AM -0700, Andrew Morton wrote: > > > udev needs the following rule in order to create the correct device > node for > > > the Android phone. It works as a mass storage device without this, but > won't > > > work with the debugger, which looks for the right type of entry in > /dev/bus/usb > > > in order to detect devices. > > > > > > SUBSYSTEM=="usb",ATTR{idVendor}=="0bb4",ATTR{idProduct}=="0c02" > > I really think this is not the correct thing to be doing here, but > please bring it up on the linux-hotplug@vger.kernel.org mailing list, > with full details of why this ruls is necessary (hint, I don't think it > does anything...) > It doesn't look like the rule does anything, but the /dev/usb/###/### node is not created without the rule. Why would that be? Shouldn't device nodes always be created when a USB device is plugged in, whether or not the device is recognized by the system?<br> <br>I actually already sent an email to the address you specified already, and it bounced -- I just went back and re-read the bounce message and realized it was because HTML messages are automatically rejected [ :-) ], I just assumed the address didn't exist or something...<br> <br>I will re-send the email now, thanks!<br><br>Luke<br><br><br><div class="gmail_quote">On Tue, Oct 28, 2008 at 2:18 PM, Greg KH <span dir="ltr"><<a href="mailto:greg@kroah.com">greg@kroah.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">On Tue, Oct 28, 2008 at 10:46:32AM -0700, Andrew Morton wrote:<br> </div><div class="Ih2E3d">> > udev needs the following rule in order to create the correct device node for<br> > > the Android phone. It works as a mass storage device without this, but won't<br> > > work with the debugger, which looks for the right type of entry in /dev/bus/usb<br> > > in order to detect devices.<br> > ><br> > > SUBSYSTEM=="usb",ATTR{idVendor}=="0bb4",ATTR{idProduct}=="0c02"<br> <br> </div>I really think this is not the correct thing to be doing here, but<br> please bring it up on the <a href="mailto:linux-hotplug@vger.kernel.org">linux-hotplug@vger.kernel.org</a> mailing list,<br> with full details of why this ruls is necessary (hint, I don't think it<br> does anything...)<br> </blockquote></div><br>