All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] /dev/bus/usb on BR
Date: Mon, 26 Apr 2010 09:02:15 +0200	[thread overview]
Message-ID: <87tyqy4ryg.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <p2l630286c71004252341l5ed447f0sd5cb0c0bf3c68a75@mail.gmail.com> (Nataraj S. Narayan's message of "Mon, 26 Apr 2010 06:41:21 +0000")

>>>>> "Nataraj" == Nataraj S Narayan <natarajsn@gmail.com> writes:

 Nataraj> Hi
 Nataraj> I am on BR git latest.

 Nataraj> I am connecting a Upek fingerprint device to my At91sam9263ek SBC with
 Nataraj> linux-2.6.32 and BR file system using glibc based Codesourcery
 Nataraj> external toolchain.

 Nataraj> Adding the device doesn't add nodes into /proc/bus/usb even though i
 Nataraj> get the following after connecting device.

Your title said /dev/bus/usb, but here you say /proc - /proc/bus/usb is
handled by usbfs, whereas /dev/bus/usb is handled by udev/mdev. Which
one do you mean?

 Nataraj> The same code works well on qemu emulated arm-linux libc
 Nataraj> system ,where the usb system got /dev/bus/usb with populated
 Nataraj> nodes.

What's the difference between that rootfs and this one? Does it work on
your AT91 if you use the qemu rootfs?

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2010-04-26  7:02 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-26  6:41 [Buildroot] /dev/bus/usb on BR Nataraj S Narayan
2010-04-26  6:52 ` Ravi Kumar Kulkarni
2010-04-26  7:20   ` Peter Korsgaard
2010-04-26  7:24     ` Ravi Kumar Kulkarni
2010-04-26  7:26       ` Peter Korsgaard
2010-04-26  7:32         ` Ravi Kumar Kulkarni
2010-04-26  7:02 ` Peter Korsgaard [this message]
     [not found]   ` <x2j630286c71004260020s9acd6240u55ed0215380bc461@mail.gmail.com>
2010-04-26  7:25     ` Peter Korsgaard

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=87tyqy4ryg.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --cc=buildroot@busybox.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.