public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Patrick Boettcher <pboettcher@kernellabs.com>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: FX2 FW: conversion from Intel HEX to DVB USB "hexline"
Date: Sun, 06 Nov 2011 20:07:31 +0200	[thread overview]
Message-ID: <4EB6CCE3.4020809@iki.fi> (raw)
In-Reply-To: <201111061858.00709.pboettcher@kernellabs.com>

Many thanks!

Actually, I was just started to write similar Python script! You got 
maybe 15min late but still 15min before mine was ready :)

Format was nothing more than convert ASCII hex values to binary bytes 
and stripping out all white spaces and Intel HEX start code ":".

Why it was initially converted to binary and not used Intel HEX as it 
is? I think you know, as a original author, history about that decision?

regards
Antti

On 11/06/2011 07:58 PM, Patrick Boettcher wrote:
> Hi Antti,
>
> On Sunday, November 06, 2011 03:26:20 PM Antti Palosaari wrote:
>> Is there any simple tool (or one liner script :) to convert normal Intel
>> HEX firmware to format used by DVB USB Cypress firmware loader?
>>
>> Or is there some other way those are created?
>>
>> Loader is here:
>> dvb-usb-firmware.c
>> int usb_cypress_load_firmware()
>
> I'm sure that you have found something yourself in the meantime, but I used
> the attached script to convert .hex to binaries.
>
> HTH,
>
> --
> Patrick Boettcher - KernelLabs
> http://www.kernellabs.com/


-- 
http://palosaari.fi/

  reply	other threads:[~2011-11-06 18:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-06 14:26 FX2 FW: conversion from Intel HEX to DVB USB "hexline" Antti Palosaari
2011-11-06 17:58 ` Patrick Boettcher
2011-11-06 18:07   ` Antti Palosaari [this message]
2011-11-06 18:13     ` Patrick Boettcher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EB6CCE3.4020809@iki.fi \
    --to=crope@iki.fi \
    --cc=linux-media@vger.kernel.org \
    --cc=pboettcher@kernellabs.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox