On Thu, Oct 25, 2007 at 08:52:48AM -0700, Brooks Talley wrote:
> Thanks to everyone who applied. The OpenBSD approach to setting UFTDI baud
> rates is definitely superior.
>
> However, the root of my problem turned out to be Python. Even with the new
> baud rate hardcoded in the UFTDI kernel m
Thanks to everyone who applied. The OpenBSD approach to setting UFTDI baud
rates is definitely superior.
However, the root of my problem turned out to be Python. Even with the new
baud rate hardcoded in the UFTDI kernel module and manually added to termios.h,
Python was refusing to admit that
On Thu, Oct 25, 2007 at 10:11:36AM +1000, Antony Mawer wrote:
> On 25/10/2007 8:59 AM, Bernd Walter wrote:
> >On Wed, Oct 24, 2007 at 09:53:06AM -0700, Brooks Talley wrote:
> >>Hi, everyone. I'm pulling my hair out in great chunks.
> >>
> >>I need to get Python 2.5, using pyserial 2.2, to open a F
On 25/10/2007 8:59 AM, Bernd Walter wrote:
On Wed, Oct 24, 2007 at 09:53:06AM -0700, Brooks Talley wrote:
Hi, everyone. I'm pulling my hair out in great chunks.
I need to get Python 2.5, using pyserial 2.2, to open a FTDI-based usb to
serial port at 25 baud. The FTDI chip definitely supp
On Wed, Oct 24, 2007 at 09:53:06AM -0700, Brooks Talley wrote:
>
> Hi, everyone. I'm pulling my hair out in great chunks.
>
> I need to get Python 2.5, using pyserial 2.2, to open a FTDI-based usb to
> serial port at 25 baud. The FTDI chip definitely supports this rate.
> The port mounts
Hi, everyone. I'm pulling my hair out in great chunks.
I need to get Python 2.5, using pyserial 2.2, to open a FTDI-based usb to
serial port at 25 baud. The FTDI chip definitely supports this rate. The
port mounts at /dev/cuaU0.
The problem is that
/usr/local/lib/python2.5/site-package
6 matches
Mail list logo
