On Sunday 28 May 2006 11:22 am, Bryan O'Donoghue wrote: > Greetings list. > > I hate for my first posting here to be a question, however. > > Would the list have an objection were I to submit a patch to Das U-Boot > the Embedded Bootloader which used VendorID 0x0525 and ProductID 0xa4a6
Assigned to "Linux-USB Serial Gadget" (non-ACM mode) > or VendorID 0x0525 and ProductID 0xa4a7 Assigned to "Linux-USB Serial Gadget (CDC ACM mode)". > to identify gserial and cdc_acm compatible > console's in Das U-Boot ? I kind of druther you didn't use those codes, because you won't actually be using the Linux-USB firmware, or the Linux tty stack. Right? Just something that works well enough to pass characters to and from the U-Boot console layer. That said, USB support in U-Boot is a Good Thing. Those folk who tell me about bringing boards up with RS-232 but no Ethernet have my sympathy. They get much happier once USB works, and decent download speeds are possible! > Keep in mind Das U-Boot would probably be used as a bootloader for Linux, so > it > has been suggested that there would be a completeness to doing it this way. > > Would this in fact be a possibility considering the intention is to emulate > the Linux (VendorID 0x0525/ProductID 0xa4a6) (VendorID 0x0525/ProductID > 0xa4a7) > and nothing else ? Possibility, but not the best one IMO. I don't relish the notion of anyone troubleshooting something with the thought that they're talking to Linux, then finding out that it's nothing of the sort! Instead, how about two codes specifically for U-Boot? I can send you a pair (off-list). Better yet, only support the CDC ACM mode; that way you'll have better MS-Windows interop. - Dave _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
