On Fri, Nov 22, 2013 at 01:15:31PM +0100, Krzysztof Opasiak wrote: > Hi, > > > -----Original Message----- > > From: Stoppa, Igor [mailto:[email protected]] > > Sent: Wednesday, November 20, 2013 4:07 PM > > To: Krzysztof Opasiak > > Cc: Yang Chengwei; Taeyoung Kim; Krogerus, Heikki; > > [email protected] > > Subject: Re: [Dev] usb-manager: set correct usb gadget attributes > > > > Hello, > > > > > > On 20 November 2013 16:43, Krzysztof Opasiak > > <[email protected]> wrote: > > > > > > [snip] > > > > If you have some plans related to > > USB please also introduce them on the list and wiki > > > > > > I would like to provide some background, which might better explain > > what we are after. > > > > Please consider a scenario where we have an unattended testing > > setup which consists > > of one harness PC plus multiple target devices, all connected > > through USB cables. > > > > These devices can either come from different OEMs or belong to the > > same OEM (but > > being different models) or they might be different instances of the > > same product. > > > > We want to be able to address them individually through sdb and > > other tools (some will > > be OEM specific, because different HW platforms have different low > > level protocols). > > > > This, in practice, means that we need to expose the SN. > > > > Other information such as idVendor and idProduct might also help in > > dynamically selecting > > which SW to load on the device. > > Rather than maintaining a DB of HW types vs SN it would be > > preferable to track just the > > Vendor and Product ids. > > Let me summarize and please correct me if I'm wrong. We have a PC in > host mode and multiple devices with tizen in USB device mode. We are > using sdb on the host and we would like to be able to communicate witch > each particular device directly. > > If above is true, it means that we would like to use sdb on a host with > -s option: > > $sdb -h > > -s <serial number> - directs command to the USB device or > emulator with the given serial number.
Yes, that's it. > > Serial number belongs to device descriptor (device strings exactly). So > the issue is that usb-manager should generate unique serials while first I think no, usb-manager doesn't generate the serial number but read from some place, just like the vendor, product, though they're currently hard-coded in usb-manager. That's what we need fix. We do have to provide some API to get such HW infos. > system boot up and it should be configured in each gadget. This solution > is easy to apply but has some issues. How to ensure that Serials will be > globally unique? I men that some other Linux distribution would like to So the serial number provides by product manufator, I think they can ensure their product unique. Or usb-manager may generate one based on [idVender,idProduct,iSerial] triple. > also use sdb but without usb--manager? Maybe we should change sdb and sdb is for Tizen, so I think use it without usb-manager isn't a valid case. > connect to <VendorID> <ProductID> <serial> not only to serial? What do A little complicate, if we can implement this complicate in usb-manager, then I think it's more user friendly. -- Thanks, Chengwei > you think? Maybe there are other requirements which I don't know and > both solutions are wrong? > > -- > BR's > > Krzysztof Opasiak > Samsung R&D Institute Poland > Samsung Electronics > [email protected] > > > >
signature.asc
Description: Digital signature
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
