From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
To: Sean Young <sean@mess.org>
Cc: Andy Walls <awalls.cx18@gmail.com>,
Jarod Wilson <jwilson@redhat.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Aya Mahfouz <mahfouz.saif.elyazal@gmail.com>,
linux-media@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: staging: media: lirc: lirc_zilog.c: replace custom print macros with dev_* and pr_*
Date: Mon, 17 Nov 2014 12:59:09 -0200 [thread overview]
Message-ID: <20141117125909.2729440b@recife.lan> (raw)
In-Reply-To: <20141109213517.GA1349@gofer.mess.org>
Em Sun, 9 Nov 2014 21:35:17 +0000
Sean Young <sean@mess.org> escreveu:
> On Thu, Nov 06, 2014 at 08:56:47AM -0500, Andy Walls wrote:
> > On November 6, 2014 8:54:28 AM EST, Andy Walls <awalls.cx18@gmail.com> wrote:
> > >Sean,
> > >
> > >Ir-kbd-i2c was never intended for Tx.
> > >
> > >You can transmit *short* arbitrary pulse-space streams with the zilog
> > >chip, by feeding it a parameter block that has the pulse timing
> > >information and then subsequently has been obfuscated. The firmware
> > >file that LIRC uses in userspace is full of predefined versions of
> > >these things for RC5 and NEC IIRC. This LIRC firmware file also holds
> > >the (de)obfuscation key.
> > >
> > >I've got a bunch of old notes on this stuff from essentially reverse
> > >engineering the firmware in the Z8. IANAL, but to me, its use in
> > >developing in-kernel stuff could be dubious.
> > >
> > >Regards,
> > >Andy
>
> Very interesting.
>
> I had considered reverse engineering the z8 firmware but I never found a
> way to access it. I guess we have three options:
>
> 1. I could use Andy's notes to implement Tx. I have not seen the original
> firmware code so I'm not contaminated by reverse engineering it. IANAL
> but I thought this is an acceptable way of writing a driver.
>
> 2. Hauppauge could prove us with documentation to write a driver with.
I tried to get some info about that, but they are unable to get anything
related to this design so far.
So, I think that, if you have some time to dedicate to it, the best would
be to go for option #1.
> 3. Leave it as-is, lirc_zilog will eventually be deleted from staging as it
> can't be ported to rc-core.
>
>
> Sean
> --
> To unsubscribe from this list: send the line "unsubscribe linux-media" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-11-17 14:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 13:06 staging: media: lirc: lirc_zilog.c: replace custom print macros with dev_* and pr_* Dan Carpenter
2014-10-31 14:26 ` Aya Mahfouz
2014-10-31 14:35 ` Dan Carpenter
2014-11-01 20:05 ` Aya Mahfouz
2014-11-06 12:46 ` Sean Young
2014-11-06 13:05 ` Mauro Carvalho Chehab
2014-11-06 13:21 ` Sean Young
[not found] ` <697D038C-4BD9-4113-8E7E-B89BACF09AC2@gmail.com>
2014-11-06 13:56 ` Andy Walls
2014-11-09 21:35 ` Sean Young
2014-11-17 14:59 ` Mauro Carvalho Chehab [this message]
2014-11-20 12:38 ` Sean Young
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=20141117125909.2729440b@recife.lan \
--to=mchehab@osg.samsung.com \
--cc=awalls.cx18@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=jwilson@redhat.com \
--cc=linux-media@vger.kernel.org \
--cc=mahfouz.saif.elyazal@gmail.com \
--cc=sean@mess.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.