Hi Andrew,
On Wed, Nov 29, 2023 at 3:27 AM Andrew O'Mahony
wrote:
>
> Hello,
>
> I've just joined the group and would like to just make sure I
> understand the patching process:
>
> I have cloned the code into my own repo, made my changes, and can
> generate a pull request.
>
> Do I put the pull
On Tue, Aug 29, 2023 at 10:51 AM wrote:
>
> From: Yegor Yefremov
>
> ---
> src/ftdi.c | 7 +++
> 1 file changed, 7 insertions(+)
>
> diff --git a/src/ftdi.c b/src/ftdi.c
> index 0a7fb27..e16816e 100644
> --- a/src/ftdi.c
> +++ b/src/ftdi.c
> @@ -3881,
As stated here [1], ft_prog doesn't add these fields when programming
the default values. But when I use their C# bindings and initialize my
eeprom variable as
FTDI.FT4232H_EEPROM_STRUCTURE eeprom = new FTDI.FT4232H_EEPROM_STRUCTURE()
I get all these fields programmed for the FT4232 chip. What
On Thu, Aug 3, 2023 at 11:18 AM Yegor Yefremov
wrote:
>
> On Tue, Aug 1, 2023 at 11:44 AM Yegor Yefremov
> wrote:
> >
> > On Mon, Jul 31, 2023 at 1:53 PM Yegor Yefremov
> > wrote:
> > >
> > > I want to write ca. 25 bytes as user data (my FTDI chips
On Tue, Aug 1, 2023 at 11:44 AM Yegor Yefremov
wrote:
>
> On Mon, Jul 31, 2023 at 1:53 PM Yegor Yefremov
> wrote:
> >
> > I want to write ca. 25 bytes as user data (my FTDI chips are FT2232,
> > FT4232 and FTX). What is my strategy to calculate the user_data_ad
On Mon, Jul 31, 2023 at 1:53 PM Yegor Yefremov
wrote:
>
> I want to write ca. 25 bytes as user data (my FTDI chips are FT2232,
> FT4232 and FTX). What is my strategy to calculate the user_data_addr?
>
> If I set EEPROM defaults via ftdi_eeprom_initdefaults() providing only
>
I want to write ca. 25 bytes as user data (my FTDI chips are FT2232,
FT4232 and FTX). What is my strategy to calculate the user_data_addr?
If I set EEPROM defaults via ftdi_eeprom_initdefaults() providing only
the product string. Then I perform ftdi_eeprom_build() and use its
return value to
Hi Thomas,
On Sat, May 16, 2020 at 9:53 PM Yegor Yefremov
wrote:
>
> Hi Thomas,
>
> On Thu, May 14, 2020 at 11:21 PM Thomas Jarosch
> wrote:
> >
> > Hi Yegor,
> >
> > You wrote on Mon, Apr 13, 2020 at 11:32:47PM +0200:
> > > I think the decod
Hi Thomas,
On Thu, May 14, 2020 at 11:21 PM Thomas Jarosch
wrote:
>
> Hi Yegor,
>
> You wrote on Mon, Apr 13, 2020 at 11:32:47PM +0200:
> > I think the decoding of boolean bit fields all need to be changed
> > to "!!(bit test)", so the in memory value will truely be one or zero.
> >
> > Then we
Hi Åke,
no that I know of, but you can do this sequentially like in this
Debian package [1]. For each build, just specify the required paths to
the related Python version.
[1] https://sources.debian.org/src/libftdi1/1.4-2/debian/rules/
Yegor
On Sun, Apr 5, 2020 at 12:07 PM Åke Rehnman wrote:
Hi Thomas,
On Fri, Feb 7, 2020 at 4:57 PM Yegor Yefremov
wrote:
>
> Hi Thomas,
>
> On Fri, Feb 7, 2020 at 4:50 PM Thomas Jarosch
> wrote:
> >
> > Hi Yegor,
> >
> > You wrote on Thu, Feb 06, 2020 at 02:51:27PM +0100:
> > > Any plans for 1.5-rc1
Hi Thomas,
On Fri, Feb 7, 2020 at 4:50 PM Thomas Jarosch
wrote:
>
> Hi Yegor,
>
> You wrote on Thu, Feb 06, 2020 at 02:51:27PM +0100:
> > Any plans for 1.5-rc1?
>
> yesterday :D
>
> I'm in the middle of an update release crunch period, it will be done by
> March.
> (Microsoft will auto-enable
Hi Thomas,
On Thu, Feb 6, 2020 at 2:41 PM Thomas Jarosch
wrote:
>
> Hi Yegor,
>
> You wrote on Thu, Feb 06, 2020 at 02:37:09PM +0100:
> > From: Yegor Yefremov
> >
> > Signed-off-by: Yegor Yefremov
> > ---
> > .gitignore | 3 +++
> > 1
Hi Thomas,
On Thu, Jan 16, 2020 at 8:42 AM wrote:
>
> From: Yegor Yefremov
>
> Signed-off-by: Yegor Yefremov
> ---
> cmake/FindConfuse.cmake | 2 +-
> examples/async.c| 4 ++--
> examples/serial_test.c | 2 +-
> examples/stream_test.c | 4 ++--
>
On Tue, Jan 7, 2020 at 5:18 PM Dan Dedrick wrote:
>
> These strings are not modified and it doesn't make sense that they ever
> would be. Setting these as const ensures that they will not be modified
> and allows const strings to be passed in without special manipulation.
>
> Specifically a call
Hi Thomas,
I've tested the patch with my software and so far everything seems to
be working.
What is your schedule for a new release?
Cheers,
Yegor
On Thu, Aug 22, 2019 at 3:48 PM Yegor Yefremov
wrote:
>
> Hi Thomas,
>
> this patch is only compile tested.
>
> Regards,
>
Hi Thomas,
this patch is only compile tested.
Regards,
Yegor
On Thu, Aug 22, 2019 at 3:47 PM wrote:
>
> From: Yegor Yefremov
>
> Fixes -Wmisleading-indentation warnings.
> ---
> python/ftdi1.i | 14 --
> 1 file changed, 12 insertions(+), 2 deletions(-)
&g
On Tue, Aug 6, 2019 at 10:43 AM Thomas Jarosch
wrote:
>
> Hi Yegor,
>
> You wrote on Mon, Aug 05, 2019 at 03:46:16PM +0200:
> > I get following compiler warnings when compiling libftdi Python
> > bindings with gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1):
> >
> > Scanning dependencies of target
I get following compiler warnings when compiling libftdi Python
bindings with gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1):
Scanning dependencies of target _ftdi1
[ 22%] Building C object
python/CMakeFiles/_ftdi1.dir/CMakeFiles/_ftdi1.dir/ftdi1PYTHON_wrap.c.o
On Tue, Jun 4, 2019 at 5:22 PM Thomas Jarosch
wrote:
>
> Hello Yegor,
>
> You wrote on Tue, Jun 04, 2019 at 02:09:24PM +0200:
> > > > some files in libftdi mention additional licenses: src/ftdi_stream.c
> > > > (MIT), cmake/UseLibFTDI1.cmake (LGPL 2.1) etc.
> > > >
> > > > Could you reflect all
On Wed, May 29, 2019 at 1:01 PM Yegor Yefremov
wrote:
>
> Hello Thomas,
>
> some files in libftdi mention additional licenses: src/ftdi_stream.c
> (MIT), cmake/UseLibFTDI1.cmake (LGPL 2.1) etc.
>
> Could you reflect all this in the LICENSE file like dropbear does [1]?
>
Hello Thomas,
some files in libftdi mention additional licenses: src/ftdi_stream.c
(MIT), cmake/UseLibFTDI1.cmake (LGPL 2.1) etc.
Could you reflect all this in the LICENSE file like dropbear does [1]?
It would be also great if the project can provide a file containing
all copyright information
On Mon, Oct 29, 2018 at 11:37 AM Yegor Yefremov
wrote:
>
> I have two devices one with FT2232HL and the other with FT232HL. lsusb output
>
> Bus 001 Device 003: ID 0403:6010
>
> and
>
> Bus 001 Device 003: ID 0403:6014
>
> I'm trying to decode EEPROM with this
I have two devices one with FT2232HL and the other with FT232HL. lsusb output
Bus 001 Device 003: ID 0403:6010
and
Bus 001 Device 003: ID 0403:6014
I'm trying to decode EEPROM with this Python code:
import ftdi1 as ftdi
VID_FTDI = 0x0403
PID_FTDI_FT232H = 0x6014
PID_FTDI_FT2232H = 0x6010
Hi Thomas,
sorry for delay.
On Mon, Feb 5, 2018 at 11:36 PM, Thomas Jarosch
<thomas.jaro...@intra2net.com> wrote:
> Hi Yegor,
>
> On 01/03/2018 01:46 PM, Yegor Yefremov wrote:
>> Also disable all options having extra dependencies.
>>
>> If an option is selected m
Also disable all options having extra dependencies.
If an option is selected makes its dependencies as REQUIRED.
Signed-off-by: Yegor Yefremov <yegorsli...@googlemail.com>
---
CMakeLists.txt | 62 ---
CMakeOptions.txt | 8 +++
examples/CMakeLis
On Thu, Dec 28, 2017 at 3:32 PM, Thomas Jarosch
<thomas.jaro...@intra2net.com> wrote:
> Hi Yegor and Samuel,
>
> On Saturday, 23 December 2017 21:45:11 CET Yegor Yefremov wrote:
>> Forget about the STATICLIBS related patch, as libftdi1 creates both
>> dynamic and stati
On Fri, Dec 15, 2017 at 3:19 PM, Yegor Yefremov
<yegorsli...@googlemail.com> wrote:
> Hello Thomas,
>
> On Fri, Dec 15, 2017 at 3:09 PM, <yegorsli...@googlemail.com> wrote:
>> From: Samuel Martin <s.marti...@gmail.com>
>>
>> Remove the STATICLIBS CM
Build shared library:
> cmake -DBUILD_SHARED_LIBS=ON
>
> Build static library:
> cmake -DBUILD_SHARED_LIBS=OFF
>
> Signed-off-by: Samuel Martin <s.marti...@gmail.com>
> Signed-off-by: Yegor Yefremov <yegorsli...@googlemail.com>
> ---
> CMakeLists.tx
Hi Thomas,
On Thu, Apr 20, 2017 at 6:17 PM, Thomas Jarosch
<thomas.jaro...@intra2net.com> wrote:
> Hi Yegor,
>
> On Tuesday, 18 April 2017 11:47:50 CEST Yegor Yefremov wrote:
>> I'm configuring FTX ftdi.CBUS_FUNCTION_0 to ftdi.CBUSX_CLK24 in Linux
>> (ARM machin
I'm configuring FTX ftdi.CBUS_FUNCTION_0 to ftdi.CBUSX_CLK24 in Linux
(ARM machine). After this ttyUSB0 gets disconnected, I can either
rebind it or reload the FTDI drive. Everything as expected. The
problem is, that I get 24MHz output only if I really reboot my ARM
machine.
How can I activate
Hi Thomas,
compiling libftdi with mingw toolchain produces following warnings:
[ 29%] Building C object examples/CMakeFiles/stream_test.dir/stream_test.c.obj
/home/user/Documents/versioned/libftdi/examples/stream_test.c: In
function ‘readCallback’:
Hi Thomas,
On Wed, Feb 22, 2017 at 9:56 AM, Thomas Jarosch
<thomas.jaro...@intra2net.com> wrote:
> Hi Yegor,
>
> On Tuesday, 24 January 2017 15:14:57 CET yegorsli...@googlemail.com wrote:
>> From: Yegor Yefremov <yegorsli...@googlemail.com>
>>
>&g
On Wed, Jun 8, 2016 at 11:52 AM, <yegorsli...@googlemail.com> wrote:
> From: Yegor Yefremov <yegorsli...@googlemail.com>
>
> During checksum calculation in ftdi_eeprom_build() a 16-bit value
> will be read directly from EEPROM (FT230X devices only):
>
> ftd
34 matches
Mail list logo
