[ltp] [PATCH] Add support for FIR IrDA for T43/R52

[Henrique de Moraes Holschuh]

On Fri, 02 Jun 2006, Shem Multinymous wrote:
> I still needed a "dongle_id=0x09" parameter. Without dongle_id it
> didn't find any.

Noted.  This depends on luck, then.  It appears to get it right on a reload,
which is... interesting.

> Autodiscovery and irda_dump worked fine. However, using "gnokii
> --identify", it hangs after writing a bytes to the port. Minicom hangs
> too, giving no indication where. So it might be that receive works by
> transmit doesn't. Not sure how to get a more informative report.

That's good enough reason to not submit anything to the kernel team.  Argh.

Now I will have to request something far more "not nice": please someone who
*opened* his T43/R52, tell me the markings on the IrDA bridge chip so that I
can track down the datasheet (if you tell me the markings on all suspicious
chips, like all Winbond and National Semiconductors ships, I can figure out
which one we want).

> Suspending with this module hard-locked the kernel at the end of the
> suspend (and nearly killed my ThinkPad: as usual I just gave the

This is a separate issue, and a bug in the 2.6.17 nsc-ircc most probably.
Argh, well, it appears that module goes back into the hibernate blacklist.
Thanks for the warning...

> kept running because of the hard-lock, so things were damn hot when I
> opened the backpack a couple of hours later...)

Ouch!  The CPU would have entered clock modulation, though, so it would not
fry itself to death anyway, but the other components...

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh