From: Krzysztof Halasa <khc@pm.waw.pl>
To: "Jon Smirl" <jonsmirl@gmail.com>
Cc: "Bill Gatliff" <bgat@billgatliff.com>,
"ARM Linux Mailing List"
<linux-arm-kernel@lists.arm.linux.org.uk>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: Toggling GPIO at 38Khz
Date: Wed, 08 Oct 2008 23:58:34 +0200 [thread overview]
Message-ID: <m363o292b9.fsf@maximus.localdomain> (raw)
In-Reply-To: <9e4733910810080606ne8bdbb8v81d42069c985ae98@mail.gmail.com> (Jon Smirl's message of "Wed\, 8 Oct 2008 09\:06\:30 -0400")
"Jon Smirl" <jonsmirl@gmail.com> writes:
> These are external boards people buy to use with MythTV. They are most
> commonly used on the x86, but the NSLU2 has been modified to use them
> too.
>
> The hardware can't be changed, people have bought thousands of these devices.
>
> Many people cut up a serial cable and solder it themselves...
Sure but you only need to bit-bang at 36 or so kHz while transmitting,
right? The receive side is a slow one as the receiver chip has an
integrated "demodulator".
If so then personally... I'd abandon the simple TX circuit, and use
a hardware ~36 kHz oscillator, gated by the serial output signal.
I don't think such transmitters are in thousands. Tens, maybe - the
cost of replacing/modifying them all should be insignificant. I guess
one could design and produce such a TXer in less than 20 minutes.
--
Krzysztof Halasa
next prev parent reply other threads:[~2008-10-08 21:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 3:43 Jon Smirl
2008-10-08 6:40 ` Eric Miao
2008-10-09 8:38 ` Andy Green
2008-10-08 12:01 ` Bill Gatliff
2008-10-08 13:06 ` Jon Smirl
2008-10-08 17:00 ` Chris Friesen
2008-10-08 21:58 ` Krzysztof Halasa [this message]
2008-10-08 18:57 ` Remy Bohmer
2008-10-08 22:24 ` Dave Hylands
2008-10-09 2:26 ` Bill Gatliff
2008-10-09 17:53 ` linux-os (Dick Johnson)
[not found] <bkydL-21G-5@gated-at.bofh.it>
2008-10-08 12:15 ` Bodo Eggert
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=m363o292b9.fsf@maximus.localdomain \
--to=khc@pm.waw.pl \
--cc=bgat@billgatliff.com \
--cc=jonsmirl@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®