Bug in switching baud rates in burst_ind branch?

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/baseband-devel@lists.osmocom.org/.

Bhaskar11 niceguy108 at gmail.com
Tue Dec 25 14:35:03 UTC 2012


Using burst_ind branch, the code switches to a higher speed in function
serial_up_to_eleven like this:

int serial_up_to_eleven(void)
{
int rv;

/* Attempt custom baudrate */
rv = osmo_serial_set_custom_baudrate(dnload.serial_fd.fd, 406250);
if (rv == 0)
return 0;

#ifdef I_HAVE_A_CP210x /* and I know what I'm doing, I swear ! */
/* Try closest standard baudrate (CP210x reprogrammed adapters) */
rv = osmo_serial_set_baudrate(dnload.serial_fd.fd, B460800);
if (rv == 0)
return 0;
#endif
etc....

If the first attempt to switch to 406250 succeeds, the function exits and
never reaches the I_HAVE_A_CP210x code which would switch to a higher speed!

Is this a bug? Or is the lower speed good enough for burst_ind? In which
case why bother with the I_HAVE_A_CP210x option?

Or have I missed something obvious?

B.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/baseband-devel/attachments/20121225/c9e7426d/attachment.htm>


More information about the baseband-devel mailing list