> >> > >> udi = > >> '/org/freedesktop/Hal/devices/usb_device_fca_4_155FF3210780674CC49459D03AE08189ACFE3799_if1_scsi_host_scsi_device_lun0' > > snip > >> usb.version_bcd = 272 (0x110) (int) > > > > Which part of that said it was an 8830? All I saw was generic devices. > > Is it important that we know it is an 8830 (or any other model number) > rather than it is a blackberry and what mode it is in?
Depends on how far up the stack your thinking. I'm thinking about what we do when your device is auto detected in Conduit, or when your displaying the drive on the desktop. Without a model number you can't create a useful name, you can't tell what it supports (until you try and use some feature and have it barf) you can't tie some pretty icons to it or even a device photo. I already have HAL fdi files and scripts(python) written which use barry to fill in these details into HAL. HAL is an interface used by many things don't forget, the phone may function, but our users won't _feel_ like we know what we're doing unless we can identify the device. What I feel is that instead of me running barry discover the information could be made available via a serial node. although if Chris would include my fdi/hal stuff in the distrobution I'd at least get feedback about it. Regards, Martin ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Barry-devel mailing list Barry-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/barry-devel
