Re: Seeking support to get USB Host Interface (Mass Storage) working with Linux 2.6.35

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Devices can be found inside sysfs (check my previous post) If you don't have mknod you have the following possibilities:
- get busybox. There are also bionic builds of busybox, so it should work without problems.
- write an mknod command, ad it's actually only a basic kernel call. You will have to do this for the reset partition table ioctl call anyway
- modify init.rc and ueventd.rc so they will pre-create the appropriate block devices. The major and minor numbers for sdx are known, and they don't change

 SztupY

Umakanta Patro <umakanta.patro@xxxxxxxxxxxxxxxxx> wrote:

>Hi Kishon,
>
>Thanks for your reply.
>
>But unfortunately I don't have udev/mdev, as I am working with an 
>Android file system. Also as there is no busybox, so I am not able to 
>find the mknod command.
>
>Also the output of cat /proc/devices does not give any usb devices 
>listed under the Block Devices category, and the output is as follows:
>
>> # cat /proc/devices
>> Character devices:
>>   1 mem
>>   2 pty
>>   3 ttyp
>>   4 /dev/vc/0
>>   4 tty
>>   4 ttyS
>>   5 /dev/tty
>>   5 /dev/console
>>   5 /dev/ptmx
>>   7 vcs
>>  10 misc
>>  13 input
>>  29 fb
>>  81 video4linux
>>  90 mtd
>> 128 ptm
>> 136 pts
>> 180 usb
>> 188 ttyUSB
>> 189 usb_device
>> 251 daq_usbgpio
>> 252 memalloc
>> 253 hx170dec
>> 254 rtc
>>
>> Block devices:
>>   1 ramdisk
>> 259 blkext
>>   7 loop
>>   8 sd
>>  31 mtdblock
>>  65 sd
>>  66 sd
>>  67 sd
>>  68 sd
>>  69 sd
>>  70 sd
>>  71 sd
>> 128 sd
>> 129 sd
>> 130 sd
>> 131 sd
>> 132 sd
>> 133 sd
>> 134 sd
>> 135 sd
>> 179 mmc
>
>Please guide me in this case on what steps need to be taken.
>
>Thanks & regards,
>Umakanta Patro
>
>
>
>On 1/27/2012 11:51 AM, ABRAHAM, KISHON VIJAY wrote:
>> Hi,
>>
>> On Fri, Jan 27, 2012 at 10:23 AM, Umakanta Patro
>> <umakanta.patro@xxxxxxxxxxxxxxxxx>  wrote:
>>>
>>> Dear All,
>>>
>>> Currently I am working on an AT91SAM9M260 based embedded board with linux
>>> 2.6.35 ported to it (With Android file system).
>>>
>>> In this I am trying to use the USB Host port as a Mass storage function.
>>>
>>> For this I have configured my kernel with the following configurations:
>>>> /CONFIG_USB_SUPPORT=y
>>>> CONFIG_USB_ARCH_HAS_HCD=y
>>>> CONFIG_USB_ARCH_HAS_OHCI=y
>>>> CONFIG_USB_ARCH_HAS_EHCI=y
>>>> CONFIG_USB=y
>>>> CONFIG_USB_DEBUG=y
>>>> # CONFIG_USB_ANNOUNCE_NEW_DEVICES is not set
>>>> /
>>> /
>>>
>>> /
>>>> /#
>>>> # Miscellaneous USB options
>>>> #
>>>> CONFIG_USB_DEVICEFS=y
>>>> # CONFIG_USB_DEVICE_CLASS is not set
>>>> # CONFIG_USB_DYNAMIC_MINORS is not set
>>>> # CONFIG_USB_MON is not set
>>>> # CONFIG_USB_WUSB is not set
>>>> # CONFIG_USB_WUSB_CBAF is not set
>>>>
>>>> /
>>>> /#
>>>> # USB Host Controller Drivers
>>>> #
>>>> # CONFIG_USB_C67X00_HCD is not set
>>>> CONFIG_USB_EHCI_HCD=y
>>>> # CONFIG_USB_EHCI_ROOT_HUB_TT is not set
>>>> # CONFIG_USB_EHCI_TT_NEWSCHED is not set
>>>> # CONFIG_USB_OXU210HP_HCD is not set
>>>> # CONFIG_USB_ISP116X_HCD is not set
>>>> # CONFIG_USB_ISP1760_HCD is not set
>>>> # CONFIG_USB_ISP1362_HCD is not set
>>>> CONFIG_USB_OHCI_HCD=y
>>>> # CONFIG_USB_OHCI_BIG_ENDIAN_DESC is not set
>>>> # CONFIG_USB_OHCI_BIG_ENDIAN_MMIO is not set
>>>> CONFIG_USB_OHCI_LITTLE_ENDIAN=y
>>>> # CONFIG_USB_SL811_HCD is not set
>>>> # CONFIG_USB_R8A66597_HCD is not set
>>>> # CONFIG_USB_HWA_HCD is not set
>>>> # CONFIG_USB_MUSB_HDRC is not set
>>>> # CONFIG_USB_GADGET_MUSB_HDRC is not set
>>>> /
>>>> /#
>>>> # USB Device Class drivers
>>>> #
>>>> # CONFIG_USB_ACM is not set
>>>> # CONFIG_USB_PRINTER is not set
>>>> # CONFIG_USB_WDM is not set
>>>> # CONFIG_USB_TMC is not set
>>>> /
>>> /
>>> /
>>>> /#
>>>> # also be needed; see USB_STORAGE Help for more info
>>>> #
>>>> CONFIG_USB_STORAGE=y
>>>> CONFIG_USB_STORAGE_DEBUG=y
>>>> # CONFIG_USB_STORAGE_DATAFAB is not set
>>>> # CONFIG_USB_STORAGE_FREECOM is not set
>>>> CONFIG_USB_STORAGE_ISD200=y
>>>> # CONFIG_USB_STORAGE_USBAT is not set
>>>> # CONFIG_USB_STORAGE_SDDR09 is not set
>>>> # CONFIG_USB_STORAGE_SDDR55 is not set
>>>> # CONFIG_USB_STORAGE_JUMPSHOT is not set
>>>> # CONFIG_USB_STORAGE_ALAUDA is not set
>>>> # CONFIG_USB_STORAGE_ONETOUCH is not set
>>>> # CONFIG_USB_STORAGE_KARMA is not set
>>>> # CONFIG_USB_STORAGE_CYPRESS_ATACB is not set
>>>> # CONFIG_USB_LIBUSUAL is not set/
>>>
>>>> /#
>>>> # SCSI device support
>>>> #
>>>> CONFIG_SCSI_MOD=y
>>>> # CONFIG_RAID_ATTRS is not set
>>>> CONFIG_SCSI=y
>>>> CONFIG_SCSI_DMA=y
>>>> # CONFIG_SCSI_TGT is not set
>>>> # CONFIG_SCSI_NETLINK is not set
>>>> CONFIG_SCSI_PROC_FS=y
>>>>
>>>> #
>>>> # SCSI support type (disk, tape, CD-ROM)
>>>> #
>>>> CONFIG_BLK_DEV_SD=y
>>>> # CONFIG_CHR_DEV_ST is not set
>>>> # CONFIG_CHR_DEV_OSST is not set
>>>> # CONFIG_BLK_DEV_SR is not set
>>>> # CONFIG_CHR_DEV_SG is not set
>>>> # CONFIG_CHR_DEV_SCH is not set
>>>> CONFIG_SCSI_MULTI_LUN=y
>>>> CONFIG_SCSI_CONSTANTS=y
>>>> # CONFIG_SCSI_LOGGING is not set
>>>> # CONFIG_SCSI_SCAN_ASYNC is not set
>>>> CONFIG_SCSI_WAIT_SCAN=m/
>>>
>>> And with this configuration when I plug in a Mass storage device, I get the
>>> following console message
>>>
>>>> *usb 1-2: new high speed USB device using atmel-ehci and address 2
>>>> usb 1-2: New USB device found, idVendor=0951, idProduct=1607
>>>> usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
>>>> usb 1-2: Product: DataTraveler 2.0
>>>> usb 1-2: Manufacturer: Kingston
>>>> usb 1-2: SerialNumber: 5B831B00044D
>>>> scsi0 : usb-storage 1-2:1.0
>>>> scsi 0:0:0:0: Direct-Access     Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI:
>>>> 0 CCS
>>>> sd 0:0:0:0: [sda] 3919872 512-byte logical blocks: (2.00 GB/1.86 GiB)
>>>> sd 0:0:0:0: [sda] Write Protect is off
>>>> sd 0:0:0:0: [sda] Assuming drive cache: write through
>>>> sd 0:0:0:0: [sda] Assuming drive cache: write through
>>>>   sda:
>>>>   sda1
>>>> sd 0:0:0:0: [sda] Assuming drive cache: write through
>>>> sd 0:0:0:0: [sda] Attached SCSI removable disk*
>>>
>>> This mass storage device is FAT32 formatted.But unfortunately, when I try to
>>> check for the /dev/sda1 I don't find any node created. Also with the USB
>> Device nodes are created automatically if you have mdev/udev utility
>> in your fs. Alternatively you can create a device node yourself by
>> using mknod utility passing the major and minor number (see cat
>> /proc/devices).
>>
>> Thanks
>> Kishon
>>
>
>
>--
>To unsubscribe from this list: send the line "unsubscribe linux-usb" in
>the body of a message to majordomo@xxxxxxxxxxxxxxx
>More majordomo info at  http://vger.kernel.org/majordomo-info.html
��.n��������+%������w��{.n�����{���)��jg��������ݢj����G�������j:+v���w�m������w�������h�����٥



[Index of Archives]     [Linux Media]     [Linux Input]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Old Linux USB Devel Archive]

  Powered by Linux