Home-Brew IR port. Was - Please Ignore RS232 message. The subject should read IrDA port... Sorry

[Alan Ide]

I was just looking through the LIRC transmitter information, as well as the
neo's CPU information and came across this tidbit in the CPU users manual.

**RS-232C interface
If users want to connect the UART to modem interface (instead of null
modem), nRTS, nCTS, nDSR, nDTR, DCD and nRI signals are needed. In this
case, the users can control these signals with general I/O ports by software
because the AFC does not support the RS-232C interface.**

Since homebrew LIRC transmitters only use the high/low nature of the DTR
signal line I think my original idea of using a software controlled GPIO pin
may still work?? We would just need a driver for LIRC to interface with the
GPIO that cycled the pin high/low at 38400. However that right there could
be the problem, im not even sure if its possible to do that in software,
given the hardware we have. Any ideas?

On 5/11/07, Ian Stirling <openmoko at mauve.plus.com> wrote:
>
> Joe Pfeiffer wrote:
> > Jeff Andros writes:
> >
> >> Chicken and egg hoss, there's also no bluetooth remotes out yet to make
> it
> >> worthwhile to have a bluetooth remote... I like the suggestion of a
> >
> > TV sets come with remotes so routinely that the usual chicken/egg
> > problem doesn't seem to arise.  Hmmm... which may point a different
> > direction:  as long as bluetooth is more expensive than IR...
>
> Alas.
>
> There is yet another wireless standard that's designed almost exactly
> for this.
>
>
> http://www.freescale.com/webapp/sps/site/prod_summary.jsp?code=MC13211&nodeId=01J4Fs25657103
>
> A microcontroller, with 32GPIO and an integrated ZigBee radio, for $2.50
> in 1000's, all in a 9*9mm package.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.openmoko.org/pipermail/openmoko-devel/attachments/20070514/1b9f2a13/attachment.htm