From: Misbah khan <misbah_khan@engineer.com>
To: linuxppc-embedded@ozlabs.org
Subject: RE: USB configuration
Date: Sun, 16 Dec 2007 21:34:53 -0800 (PST) [thread overview]
Message-ID: <14370084.post@talk.nabble.com> (raw)
In-Reply-To: <BLU106-W35DC430E02A0A1798D8B95CA650@phx.gbl>
I have configured for mass storage device still i am not getting the debug
msg that the kernel has detected the pen drive (after i connect the pen
drive ).
" Initializing USB Mass Storage driver...
usbcore: registered new driver usb-storage
USB Mass Storage support registered.=20
"
----misbah=20
Pedro Luis D. L. wrote:
>=20
>=20
>> From: misbah_khan@engineer.com
>> To: linuxppc-embedded@ozlabs.org
>> Subject: RE: USB configuration
>>=20
>>=20
>> I have inserted a USB card reader, and the following dmesg it shows ....=
.
>>=20
>> ------------------------------------------------------------------------=
-------
>> mpc8272ads: Init
>> PCI: Probing PCI hardware
>> PCI: Cannot allocate resource region 0 of device 0000:00:00.0
>> PCI: Cannot allocate resource region 1 of device 0000:00:00.0
>> SCSI subsystem initialized
>> Linux Kernel Card Services
>> options: [pci] [cardbus]
>> usbcore: registered new driver usbfs
>> usbcore: registered new driver hub
>> Serial: CPM driver $Revision: 0.01 $
>> ttyCPM0 at MMIO 0xf0011a00 (irq =3D 40) is a CPM UART
>> ttyCPM1 at MMIO 0xf0011a60 (irq =3D 43) is a CPM UART
>> io scheduler noop registered
>> io scheduler anticipatory registered
>> io scheduler deadline registered
>> io scheduler cfq registered
>> loop: loaded (max 8 devices)
>> fs_enet.c:v1.0 (Aug 8, 2005)
>> fs_enet: eth0 Phy @ 0x0, type DM9161 (0x0181b881)
>> fs_enet: eth1 Phy @ 0x3, type DM9161 (0x0181b881)
>> Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
>> ide: Assuming 33MHz system bus speed for PIO modes; override with
>> idebus=3Dxx
>> st: Version 20041025, fixed bufsize 32768, s/g segs 256
>> osst :I: Tape driver with OnStream support version 0.99.1
>> osst :I: $Id: osst.c,v 1.70 2003/12/23 14:22:12 wriede Exp $
>> ohci_hcd: 2004 Nov 08 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
>> ohci_hcd: block sizes: ed 64 td 64
>> drivers/usb/serial/usb-serial.c: USB Serial support registered for
>> Generic
>> usbcore: registered new driver usbserial_generic
>> usbcore: registered new driver usbserial
>> drivers/usb/serial/usb-serial.c: USB Serial Driver core v2.0
>> NET: Registered protocol family 2
>> IP: routing cache hash table of 512 buckets, 4Kbytes
>> TCP: Hash tables configured (established 4096 bind 8192)
>> NET: Registered protocol family 1
>> NET: Registered protocol family 17
>> IP-Config: Complete:
>> device=3Deth1, addr=3D192.168.33.136, mask=3D255.255.248.0,
>> gw=3D192.168.32.47,
>> host=3Dcashel, domain=3D, nis-domain=3D(none),
>> bootserver=3D192.168.33.96, rootserver=3D192.168.33.96, rootpath=3D
>> Looking up port of RPC 100003/2 on 192.168.33.96
>> Looking up port of RPC 100005/1 on 192.168.33.96
>> VFS: Mounted root (nfs filesystem).
>> Freeing unused kernel memory: 104k init
>> ------------------------------------------------------------------------=
--------------
>>=20
>=20
> It looks like it is well configured, because the usbfs and hub are loaded=
.
> You could check in your kernel configuration that you enabled USB Mass
> storage driver and attached a pen drive as I suggested before.
> Another possibility is to insert a card in the USB card reader. Then you
> should be able to see with dmesg if it is recognized.
>=20
> Pedro.
>=20
>> This doesent gives me the clear explaination of whether USB is working
>> properly....
>>=20
>> I would appreciate if you could share with me the basic steps to be
>> followed
>> to confirm that the USB support that i had configured is being tested in
>> all
>> aspects.
>>=20
>> Misbah
>>=20
>> Pedro Luis D. L. wrote:
>>>=20
>>>=20
>>>=20
>>>> Date: Thu, 6 Dec 2007 05:27:14 -0800
>>>> From: misbah_khan@engineer.com
>>>> To: linuxppc-embedded@ozlabs.org
>>>> Subject: USB configuration
>>>>=20
>>>>=20
>>>> HI all ...
>>>=20
>>> Hi,
>>>=20
>>>> I have configured the Montavista Kernel for USB support and for
>>>> PPC8272-ADS
>>>> board I need to know that how could i test that my USB is working ????
>>>>=20
>>>=20
>>> Try to attach an USB device, like a pendrive, to an USB port. Then
>>> type:=20
>>> dmesg | tail
>>>=20
>>> If the USB support is working properly, you should see some output
>>> saying
>>> which device have you attached and where is it mapped.
>>> If you plug a memory stick, you can try to mount it and check that the
>>> filesystem is correct.
>>>=20
>>> Pedro.
>>>=20
>>>> Its creating the directory :- /proc/bus/usb/ but doesent contain any
>>>> file
>>>> under it ????
>>>>=20
>>>>=20
>>>> its also creating the directory :- /sys/bus/usb/ but doesent contain
>>>> any
>>>> file under it ????
>>>>=20
>>>>=20
>>>> Please let me know the procedure to test whether my USB configuration
>>>> is
>>>> all
>>>> right ????
>>>>=20
>>>> Thank u=20
>>>> Misbah <><
>>>> --=20
>>>> View this message in context:
>>>> http://www.nabble.com/USB-configuration-tf4956061.html#a14192347
>>>> Sent from the linuxppc-embedded mailing list archive at Nabble.com.
>>>>=20
>>>> _______________________________________________
>>>> Linuxppc-embedded mailing list
>>>> Linuxppc-embedded@ozlabs.org
>>>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>>=20
>>> _________________________________________________________________
>>> Tecnolog=C3=ADa, moda, motor, viajes,=E2=80=A6suscr=C3=ADbete a nuestro=
s boletines para
>>> estar a la =C3=BAltima
>>> http://newsletters.msn.com/hm/maintenanceeses.asp?L=3DES&C=3DES&P=3DWCM=
aintenance&Brand=3DWL&RU=3Dhttp%3a%2f%2fmail.live.com
>>> _______________________________________________
>>> Linuxppc-embedded mailing list
>>> Linuxppc-embedded@ozlabs.org
>>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>>>=20
>>>=20
>>=20
>> --=20
>> View this message in context:
>> http://www.nabble.com/USB-configuration-tf4956061.html#a14206951
>> Sent from the linuxppc-embedded mailing list archive at Nabble.com.
>>=20
>> _______________________________________________
>> Linuxppc-embedded mailing list
>> Linuxppc-embedded@ozlabs.org
>> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>=20
> _________________________________________________________________
> MSN Video.=20
> http://video.msn.com/?mkt=3Des-es
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
>=20
>=20
--=20
View this message in context: http://www.nabble.com/USB-configuration-tp141=
92347p14370084.html
Sent from the linuxppc-embedded mailing list archive at Nabble.com.
next prev parent reply other threads:[~2007-12-17 5:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-06 13:27 USB configuration Misbah khan
2007-12-06 14:10 ` Pedro Luis D. L.
2007-12-07 5:07 ` Misbah khan
2007-12-12 15:23 ` Pedro Luis D. L.
2007-12-17 5:34 ` Misbah khan [this message]
2007-12-17 8:29 ` Pedro Luis D. L.
2007-12-17 15:21 ` Scott Wood
2007-12-18 9:34 ` Misbah khan
2007-12-17 18:33 ` Vitaly Bordug
2007-12-18 9:42 ` Misbah khan
2007-12-18 16:19 ` Scott Wood
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=14370084.post@talk.nabble.com \
--to=misbah_khan@engineer.com \
--cc=linuxppc-embedded@ozlabs.org \
/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.