community Digest, Vol 65, Issue 28

Martin Gschwandtner martin.gschwandtner at gmail.com
Sat Feb 9 19:02:54 CET 2008


HI!

Ab Mitternacht ist der Bericht freigeschalten.

MfG
Martin

On Feb 9, 2008 12:00 PM,  <community-request at lists.openmoko.org> wrote:
> Send community mailing list submissions to
>         community at lists.openmoko.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         http://lists.openmoko.org/mailman/listinfo/community
> or, via email, send a message with subject or body 'help' to
>         community-request at lists.openmoko.org
>
> You can reach the person managing the list at
>         community-owner at lists.openmoko.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of community digest..."
>
> Today's Topics:
>
>    1. Re: Mono audio output on GTA02? (joerg)
>    2. Re: Mono audio output on GTA02? (Ben Burdette)
>    3. Re: proprietary firmware (joerg)
>    4. Re: Patents and OpenMoko (Sean Moss-Pultz)
>    5. Kill The Clock (Christopher Earl)
>    6. Re: Input Method Development (dda)
>
>
> ---------- Forwarded message ----------
> From: joerg <joerg.twinklephone at gmx.de>
> To: List for OpenMoko community discussion <community at lists.openmoko.org>
> Date: Sat, 9 Feb 2008 01:33:18 +0100
> Subject: Re: Mono audio output on GTA02?
> Am Sa  9. Februar 2008 schrieb Clarke Wixon:
> > joerg <joerg.twinklephone at ...> writes:
> >
> > > The amp is for the speaker(s) only, and GTA02 has only one of
> > > them (mono). That's fine, for one good speaker will yield a better sound
> than
> > > 2 small ones.
> >
> > Unfortunately, I don't think we're getting "one good speaker" in the
> bargain.
> > The second speaker was removed to make room for WiFi, so the remaining
> speaker
> > is likely to be of comparable (identical?) quality to half of the original
> pair.
>
> :-( Anyway, 2 speakers don't make a stereo output yet, when built in such a
> small case. So it's  not so bad to lose one of them.
>
> >
> > But you're right, the headphones should still be fine.
>
> However without circuit diagrams, we can't say for sure what they 've done and
> why. Seems i was wrong with direct connection of HPh to codec chip.
>
> see spec of wolfson mixer codec chip:
> On-chip Headphone Driver with cap-less output option
> - 40mW output power on 16Ω / 3.3V
> - with 16Ω load: SNR 90dB, THD –75dB
> - with 10kΩ load: SNR 94dB, THD –90dB
> On-chip speaker driver with 0.5W into 8R
>
> I don't know why they use a dedicated amp LM4853, which is good for nothing it
> seems:
> near same power, mono *OR* stereo output, no capacitor-free bridge out for
> stereo. Additional parts needed for headphone detection to system.
>
> Sigh...
> j
>
>
>
>
> ---------- Forwarded message ----------
> From: Ben Burdette <bburdette at comcast.net>
> To: List for OpenMoko community discussion <community at lists.openmoko.org>
> Date: Fri, 08 Feb 2008 18:57:37 -0700
> Subject: Re: Mono audio output on GTA02?
>
> > Look again at the LM4853 specs and you'll see that it takes stereo in and
> > drives stereo headphone out or mono speaker out.
> >
> > http://www.national.com/pf/LM/LM4853.html
> >
> >
> Ah, I should have followed the link.  I kind of stopped reading where it
> said "Mono Amplifier" in the wiki.
>
> http://wiki.openmoko.org/wiki/Neo_FreeRunner_GTA02_Hardware#Mono_Amplifier
>
> So its a 'high power' mono amp and low power stereo amp.  That makes
> sense, I feel better now.
>
> Ben
>
>
>
>
> ---------- Forwarded message ----------
> From: joerg <joerg.twinklephone at gmx.de>
> To: List for OpenMoko community discussion <community at lists.openmoko.org>
> Date: Sat, 9 Feb 2008 03:12:11 +0100
> Subject: Re: proprietary firmware
> Am Sa  9. Februar 2008 schrieb Steven Kurylo:
> > > I don't
> > > want to know how 802.11b protocol is handled in the wlan-chip. I want to
> > > have a powerfull bugfree API for the subsystem.
> >
> > In a Free software world, we do want to know.
> Ok, agreed. But where ends SW and starts HW. Dedicated custom processor;
> bootload-firmware; flashrom-fw; OTP-rom fw; mask programmed rom fw; FPGA;
> even hardwired comparators and adders? The src is worth nothing for an alien
> cpu command set, the whole fw src is nothing without register documentation.
> Where to stop? FW of the DVD-writer with burn-receipes, of the HD with the
> algos of the head-amp-DSP therein? This is valuable IP of the
> DVD/HD-Manufacturer, they won't disclose. Power management of WiFI exactly
> the same.
>
> > For various reasons,
> > one of which is because there is no "powerful bugfree API".
> True. For every level API. No matter if that's driver API (to the "firmware")
> or HW-API (description of registers and chip functions).
>
> > They'll
> > be bugs and we (as in the Free software community) can fix them; I
> > don't want to be at the mercy of some random company.
> You *always* are, one way or the other. If the description of a register (e.g
> timing) is faulty, you won't fix anything, neither the driver nor the chip
> itself, unless you have the chip design data (masks etc). See actual
> processor bug, would you like to have microcode documentation, so you can
> decide whether or not, and how you may fix it with a microcode patch? You
> have to learn how the CPU works internally (down to gate-level timing) to do
> so. And this means open HW, what nearly never will happen.
>
> I feel quite like you, but i don't think anyone may *force* hw-manufacturers
> to do it our way. Instead they should offer more support and information. And
> guarantee a clean API.
>
> j
>
>
>
>
>
>
> ---------- Forwarded message ----------
> From: Sean Moss-Pultz <sean at openmoko.com>
> To: List for OpenMoko community discussion <community at lists.openmoko.org>
> Date: Sat, 09 Feb 2008 10:37:08 +0800
> Subject: Re: Patents and OpenMoko
> Clarke Wixon wrote:
> > Sean Moss-Pultz <sean at ...> writes:
> >
> >> Yes this is exactly what we want. We want to make the patents we get
> >> freely available, but also only usable for defensive purposes, forever
> >
> > Sean,
> >
> > I am a registered U.S. patent attorney and a member of the California Bar,
> > and I reside in the San Francisco Bay Area.  And I'm also a part-time OpenMoko
> > developer and enthusiastic supporter (you'll see my name all over the Bugzilla
> > bug tracker, for example, but I haven't completed any significant projects of my
> > own yet).  I have a GTA01 I'm proud to own and work on.
> >
> > I would be happy to discuss some real-world intellectual property strategies
> > at your convenience.  I have a good understanding of the U.S. patent system,
> > how you might be able leverage that (and other approaches) to advance OpenMoko's
> > specific objectives (not to intimidate others!), and how to best use open-source
> > licenses.
> >
> > Anyway, I'll get in touch with you via email and maybe we can set up a meeting
> > to discuss more concrete goals and strategies.
>
> Sounds great. I would love your help!
>
> Sean
>
>
>
>
> ---------- Forwarded message ----------
> From: "Christopher Earl" <earlc8451 at clarkstate.edu>
> To: <community at lists.openmoko.org>
> Date: Sat, 09 Feb 2008 00:30:20 -0500
> Subject: Kill The Clock
> Someone asked about killing the Huge clock that takes up the whole display quicksand on #openmoko gave me this, it makes the clock real small and docks it on the date bar
> This works from ssh
> dbus-launch gconftool-2 --type bool --set /desktop/poky/interface/small_clock true
>
>
>
>
> ---------- Forwarded message ----------
> From: dda <dda at sungnyemun.org>
> To: "List for OpenMoko community discussion" <community at lists.openmoko.org>
> Date: Sat, 9 Feb 2008 15:17:52 +0800
> Subject: Re: Input Method Development
> I dunno about Byeoru [벼루, I suppose, the flat stone used to make ink
> from dried China ink and water, used in calligraphy, I suppose], but
> the others are common, I think I mentioned them before.
>
> 2-beol is the most common hangul layout over qwerty. 3-beol is another
> one, which I have never seen in use in 20+ years spent studying
> Korean. Hangul-Romaja is a generic name for inputing Korean in
> transliteration -- say hangug for Korea. There's a couple of them, but
> again, I have never seen them in use in Korea.
>
> --
> Didier
>
> On Feb 9, 2008 2:15 AM, Jeremiah Flerchinger
> <jeremiah.flerchinger at gmail.com> wrote:
> >
> >
> >
> >
> >
> > this uim has an embedded scheme interpreter... I don't like that too much
> > for an embedded device...
> >  hmm, I have no idea: is it big, slow?
> >  It's apparently used on Linux Zaurus.
> >
> >
> >
> >
> >  We could adapt the openmoko soft keyboard to interface with uim, and if the
> > API is well designed, the IM module could be changed...
> >  I'm not sure adapting to a soft keyboard would be required.  It may seize
> > key presses & emit appropriate utf-8 key values.  Try installing it on your
> > desktop & trying it with a few soft keyboards.
> >
> >
> >
> > could someone update me on the differences between these kr input methods
> > described in the doc?
> >
> >
> > Byeoru
> > Hangul (2-beol)
> > Hangul (3-beol)
> > Hangul (Romaja) I have no clue. Were you intending this for the mailing
> > list? I'm assuming so, but only saw this addressed to myself.
> >
> >
> >  Yeah, I know the patents problem with T9. But what about this one?
> >  What one? uim is open-source, so there aren't patent issues (if that's your
> > question).
>
> _______________________________________________
> OpenMoko community mailing list
> community at lists.openmoko.org
> http://lists.openmoko.org/mailman/listinfo/community
>
>


More information about the community mailing list