Does it make sense that I can no longer send a BREAK signal since I started 
using this laptop and the USB-to-Serial adapter?

* Marr <[EMAIL PROTECTED]> [June 22, 2004 04:27 pm]:
> On Tuesday 22 June 2004 03:12pm, Mark Drummond wrote:
> > On June 22, 2004 02:51 pm, Marr wrote:
> > > Can you please confirm your adapter model number? I cannot find any
> > > reference to adapter model F5U409 on the Belkin site, but there are
> > > several references to 'F5U409' in a Google search, so I know it must
> > > have existed at some point.
> >
> > Definately an F5U409.
>
> OK, good...
>
> (snip)
>
> > > What does this adapter look like? It sounds like it has a DB-9
> > > connector like the F5U109 (http://catalog.belkin.com/
> > > IWCatProductPage.process?Merchant_Id=&Product_Id=91042) but I'm curious
> > > what the differences are.
> >
> > Practically identical. Refer to the sites above.
>
> Yep -- I cannot distinguish any difference.
>
> > Is the 109 USB 1 or USB 2?
>
> The F5U109 is USB1. It seems that the F5U409 is USB1 as well (based on
> 'Spd=12' report in your attachment; I don't know if that's conclusive or
> not though).
>
> Hmmmm.... so it seems that the F5U109 and F5U409 are nearly identical.
>
> > > Therefore, could you please report the USB Vendor ID and Product ID
> > > ('cat / proc/bus/usb/devices') for this device?
> >
> > Attached.
>
> Aha! It turns out that the F5U409 reports the exact same Vendor/Product ID
>
> (and 'Rev=') as my F5U109:
> > P:  Vendor=050d ProdID=0109 Rev= 1.02
> > S:  Manufacturer=Belkin USB PDA Adapter
>
> This means that the 'mct_u232' module should work fine for baud rate
> changes with the F5U409 too. Sorry for the false alarm, but I wanted to be
> sure.
>
> > > There's a bigger issue that concerns me as well, however. The F5U109
> > > adapter and the Sitecom U232-P25 adapter, both of which use the
> > > 'mct_u232' module, use a coded baud rate instead of the conventional
> > > 'baud rate divisor'. In practical terms, this means that your F5U409
> > > (again, assuming it uses a different Product ID than my F5U109) will
> > > (probably) _not_ change baud rate successfully using the 'mct_u232'
> > > driver. Can you confirm or deny this? If you can confirm, I'd like to
> > > further modify the 'mct_u232' module to properly accommodate your
> > > adapter with regard to baud rate changes.
> >
> > I'm not exactly sure what you mean. I've configured minicom to use 9600
> > which is standard for Sun boxes. I have not tried any other rate.
>
> Well, it's a moot point since the F5U409 reports itself as 'F5U109', but if
> that weren't the case, and you tried to change the baud rate of the
> simulated RS-232 port via the F5U409 (e.g. to comply with some attached
> RS-232 device [like a GPS receiver] which was not configured for 9600 bps),
> it would probably have failed, resulting in no communication with your
> RS-232 device.
>
> Many thanks for confirming this info. It looks like no change to the
> 'mct_u232' driver is needed.  I just need to update the 'usb.ids' file to
> reflect the fact that both Belkin devices report the same USB Product ID. I
> also want to update the 'Configure.help' file at some point to reflect the
> fact that both of our Belkin adapters work with the 'mct_u232' kernel
> module.
>
> Bill Marr
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
> digital self defense, top technical experts, no vendor pitches,
> unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> [EMAIL PROTECTED]
> To unsubscribe, use the last form field at:
> https://lists.sourceforge.net/lists/listinfo/linux-usb-users

-- 
we're outta control

Attachment: pgpkqsBrZzKo0.pgp
Description: signature

Reply via email to