Phil Dibowitz wrote:
Stephen Warren wrote:
OK. Here's a complete version, with concordance.c integration. It works
for all the files in harmony_usb_logs, and a file of each type that I
got from the Website.
I applied it, but with a few changes - see the CVS list for the actual diff,
but
Stephen Warren wrote:
Phil Dibowitz wrote:
Stephen Warren wrote:
OK. Here's a complete version, with concordance.c integration. It works
for all the files in harmony_usb_logs, and a file of each type that I
got from the Website.
I applied it, but with a few changes - see the CVS list for the
Stephen Warren wrote:
On Wed, April 2, 2008 2:36 am, Phil Dibowitz wrote:
Stephen Warren wrote:
In congruity, I have some code to identify the action to take for a
specific EzHex/EZUp file, without relying on any facet of the filename.
I'm curious as to what you use to figure it out... there
Stephen Warren wrote:
Here's an early version of the patch. It's not yet suitable for merging;
it doesn't yet do IR learn stuff, and I haven't tested it since the
latest CVS updates. That said, it should give an idea where I'm going if
you want to comment on it.
I'd rather you didn't return
Stephen Warren wrote:
In congruity, I have some code to identify the action to take for a
specific EzHex/EZUp file, without relying on any facet of the filename.
I'm curious as to what you use to figure it out... there are some tells like
firmware has 'TYPEFirmware_Main/TYPE' and 'NAMEUpgrading
On Wed, April 2, 2008 2:36 am, Phil Dibowitz wrote:
Stephen Warren wrote:
In congruity, I have some code to identify the action to take for a
specific EzHex/EZUp file, without relying on any facet of the filename.
I'm curious as to what you use to figure it out... there are some tells
like
Phil Dibowitz wrote:
Your code flow suggestions sound good.
I was actually going to nuke all of the read_*_from_file garbage when I got
the patch to abstract that out - I'm still planning on doing that in the
next day or so, so if you want you can just concentrate on porting your
Stephen Warren wrote:
On Wed, April 2, 2008 2:36 am, Phil Dibowitz wrote:
Stephen Warren wrote:
In congruity, I have some code to identify the action to take for a
specific EzHex/EZUp file, without relying on any facet of the filename.
I'm curious as to what you use to figure it out... there
Phil Dibowitz wrote:
Phil Dibowitz wrote:
Your code flow suggestions sound good.
I was actually going to nuke all of the read_*_from_file garbage when I got
the patch to abstract that out - I'm still planning on doing that in the
next day or so, so if you want you can just concentrate on
