On Thu, 28 Oct 2004 14:10:31 +0200, Colin Leroy <[EMAIL PROTECTED]> wrote:
> I'm trying to make an usb-serial adapter work. It's a Sagem cable, > 0x079b:0x0027. Using generic driver doesn't seem to work, so here's > my stupid question: how does one determine the chip in a given usb > product ? (Knowing what it is, i'll know if I only have to put in > an extra Id in one of the existing drivers, or write one (hopefully > not ;-)). A few approaches possible, although none is guaranteed. First, you can crack the thing open and read what is written on the chip. It works with non-softcore solutions such as FTDI. Obviously, a softcore cannot be deduced from outside markings. Next, e-mail to the company and request documentation. It does not work often, but it might. Third, get the Windows driver and read the .INF file or the driver itself. If everything else fails, arm yourself with Snoopy and get the traces. Then you either guess which subdriver might work, or use them to write the code. -- Pete ------------------------------------------------------- This Newsletter Sponsored by: Macrovision For reliable Linux application installations, use the industry's leading setup authoring tool, InstallShield X. Learn more and evaluate today. http://clk.atdmt.com/MSI/go/ins0030000001msi/direct/01/ _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
