[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: FBUS speed change to 19200 and 115200
From: |
Pawel Kot |
Subject: |
Re: FBUS speed change to 19200 and 115200 |
Date: |
Wed, 21 Nov 2007 23:21:08 +0100 |
Hi,
On Nov 21, 2007 10:58 PM, Jari Turkia <address@hidden> wrote:
> Pawel Kot wrote:
>
> >> First you need to increase the sleep into 50000 usecs. The command
> >> simply does not sink in very fast.
> > That should not matter. You would just loop more times with 50.
>
> It absolutely matters and no, it will not iterate more. It will just
> delay more.
Ah, ok. select() will return < 0 and we will exit the loop. Committed.
> >> Secondly you cannot free the device instance on FBUS terminate-command.
> > Sorry, I don't get it.
[...]
> So, you'll get three rounds of initialization. In my case the first one
> fails. Then terminate is called. As terminate releases device instance:
> case GN_OP_Terminate:
> FREE(DRVINSTANCE(state));
>
> There will not be a working device handle left for the two other rounds.
> In my case, the third round will do the trick.
Please verify current CVS fix.
take care,
pkot
--
Pawel Kot
- FBUS speed change to 19200 and 115200, Jari Turkia, 2007/11/07
- Re: FBUS speed change to 19200 and 115200, Pawel Kot, 2007/11/07
- Re: FBUS speed change to 19200 and 115200, Jari Turkia, 2007/11/08
- Re: FBUS speed change to 19200 and 115200, Pawel Kot, 2007/11/08
- Re: FBUS speed change to 19200 and 115200, Jari Turkia, 2007/11/21
- Re: FBUS speed change to 19200 and 115200, Pawel Kot, 2007/11/21
- Re: FBUS speed change to 19200 and 115200, Jari Turkia, 2007/11/21
- Re: FBUS speed change to 19200 and 115200,
Pawel Kot <=
- Re: FBUS speed change to 19200 and 115200, Jari Turkia, 2007/11/22