Re: staging: media: lirc: lirc_zilog.c: replace custom print macros with dev_* and pr_*

[Sean Young <sean@mess.org>]

On Mon, Nov 17, 2014 at 12:59:09PM -0200, Mauro Carvalho Chehab wrote:
> 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.

Ok, thanks for asking.

Andy -- if you please send your notes please, I can work on implementing
the driver. I have hardware and time for to work on this.

Thanks

Sean