On Thu, Nov 21, 2013 at 02:28:14AM +0000, 김태영 wrote: > Hello? I'm Taeyoung Kim of SystemFW. > > Your opinion is that the vendor and product name should not be hard-coded, > right?
Yes. > > We also agree to your opinion since Tizen platform will be used for many > companies and products. > > > > We have plan to make a XML file for all information of usb configuraitons > > so that we can change Vendor and Product name by modifying just the XML file. > > The plan is for Tizen 3.0. The XML file can be changed by other methodologies, > > and thus we should discuss to find better way to change these informations > easily. For the XML solution, I have some concerns. If this XML config file provides by usb-manager, then every OEM need maintains a fork version, just for a customized XML. Or there will be a cross system OEM customize service (may not really a some kind of service, maybe a partition to store all OEM customize config files), so USB XML config is part of it. usb-manager just go and read, so no fok needed for this purpose. Or these HW infomation should be exported from system-info API or any other such kind API, so usb-manager just as a user of these APIs. The latter two also can be combined into one, like some OEM config files, exported through system-info APIs but not readable from file access. -- Thanks, Chengwei > > > > Until TIzen 2.1.1, we should use the hard-coded information or the hard-coded > information > > should be changed manually by vendor. > > > > Thank you. > > > > - Taeyoung Kim - > > > > ------- Original Message ------- > > Sender : Stoppa, Igor<[email protected]> > > Date : 2013-11-21 00:07 (GMT+09:00) > > Title : 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. > > > -- > cheers, > I > gor > Stoppa > > --------------------------------------------------------------------- > Intel Finland Oy > Registered Address: PL 281, 00181 Helsinki > Business Identity Code: 0357606 - 4 > Domiciled in Helsinki > > This e-mail and any attachments may contain confidential material for > the sole use of the intended recipient(s). Any review or distribution > by others is strictly prohibited. If you are not the intended > recipient, please contact the sender and delete all copies. > > > > > > Taeyoung, Kim | SW Engineer > > System S/W Lab./ S/W Platform Team > > Software R&D Center > > SAMSUNG ELECTRONICS CO., LTD. > > Mobile +82.10.5133.9902 > > E_mail [email protected] > > > > [cid] > > *
signature.asc
Description: Digital signature
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
