Le Tue, 13 Jan 2004 15:57:39 -0500 (EST) Alan Stern <[EMAIL PROTECTED]> a écrit:
> On Tue, 13 Jan 2004, Loic Jaquemet wrote: > > > Hello, > > > > I've bought a Philips-Nike psa128max, which is a 128 Mo mp3 player, > > with firmware update capacity. > > > > Briefly : It doesn't work. ( ~2.4.20 to 2.6.1 ) > > What is it supposed to do? Is it supposed to function like a USB disk > drive, so you can transfer mp3 files between it and your PC? yes. One can 'upload' mp3 file ( and others) on the device. while using it with the redmond OS, it is ( after a few driver inst. ) recognized as a removable disk. >Does the > fact that it has a firmware update capacity mean that it _needs_ a > firmware update in order to work with a PC? > Hemm, not sure. I just know that it can be done. I was just trying to make the différence between a simple usb key and that device. there is 'something' playing the mp3's. So there is maybe a special partition or something dedicated to the firmware... I don't know really ;( But it does'nt _need_ a firmware update to work on the first place. ( after I bought it) > > So if I can help in any kind of way, i would be delighted ;) > > > > relevant /proc/bus/usb/devices : > > > > T: Bus=01 Lev=01 Prnt=01 Port=00 Cnt=01 Dev#= 4 Spd=12 MxCh= 0 > > D: Ver= 1.10 Cls=00(>ifc ) Sub=00 Prot=00 MxPS=64 #Cfgs= 1 > > P: Vendor=0471 ProdID=1125 Rev= 0.83 > > S: Manufacturer=Nike, Inc. > > S: Product=psa[128max > > C:* #Ifs= 1 Cfg#= 1 Atr=c0 MxPwr=100mA > > I: If#= 0 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=ff Driver=(none) > > That Cls=ff(vend.) means the device uses a vendor-specific USB protocol. > > Without knowing that protocol, there's no way to communicate with the > device -- unless the vendor's just happens to be identical to an > existing standard protocol (which occurs more often than you might > think). > actually , there is a similar device, at least by brand & name : the Vendor=0471 ProdID=1120 ( mine is 1125 ) its a Philips & Nike mp3 player too.. see : http://marc.theaimsgroup.com/?l=linux-usb-devel&m=104887595829212&w=2 > > /var/log/kern.log : > > Jan 13 19:31:42 [...] kernel: hub.c: new USB > > device 00:07.2-1, assigned address 6 > > Jan 13 19:31:42 [...] kernel: > > usb.c: USB device 6 (vend/prod 0x471/0x1125) is not claimed by any > > active driver. > > > > > > dmesg : > > hub.c: new USB device 00:07.2-1, assigned address 6 > > usb.c: USB device 6 (vend/prod 0x471/0x1125) is not claimed by any > > active driver. > > This means that none of the existing drivers recognizes the > vendor/product combination as one they already know how to handle. > > > What can I do to help ? > > Answering the questions above will be a start. Maybe the vendor or > manufacturer can supply you with information about how the USB interface > > on the device is intended to work: what protocol it uses and so on. > > Alan Stern -- +--------------------------------------------+ |Jaquemet Loic GnuPG key : 0xEADC0367 | |Eleve ingenieur en informatique FIIFO, ORSAY| +--------------------------------------------+ http://sourceforge.net/projects/ffss/ #wirelessfr @ irc.freenode.net ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
