-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hello fellow developers.
|
| I have be turning my attention to the accelerometers in the Freerunner
| recently, and I would like to make a number of improvements.
| I'll give a bit of an overview below for t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| AG>
| AG> make ARCH=arm menuconfig
|
| thank you.
|
| is there a way to make zImage out of uImage again?
Not 100% certain but stripping the 64-byte U-Boot header that we add
will certainly devolve it somewh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Thu, 2009-03-05 at 14:24 +, Andy Green wrote:
|> Somebody in the thread at some point said:
|>
|> | The version of qi at http://people.openmoko.org/andy/ does have issues.
|> | I didn&#x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| The version of qi at http://people.openmoko.org/andy/ does have issues.
| I didn't get the BSoD. With the 2.6.28-stable kernel I was having
| problems with battery charging and sensing.
How did you determi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| [Still working on]
| #991: PMU driver doesn't populate initial input device status
Is this still desired behaviour?
| #1319: sysfs RTC class device missing wakealarm capability
Do we care since we can us
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Can anyone shed any light on this problem? I cannot flash the qi from
| http://downloads.openmoko.org/distro/unstable/NeoFreerunner/ as shown
| below onto my GTA02v5. I am able to flash the qi from
| http:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| It's complaining that the kernel has not been configured. However, I've
| copied the gta02_moredrivers_defconfig
| file to GTA02 and to linux-2.6 directory. Do I need to do anything else?
| Is there someway
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Tue, 3 Mar 2009 07:09:06 -0300
| Werner Almesberger (WA) wrote:
|
| WA> Petr Vanek wrote:
| WA> > dear kernel boys, is there a minimal _keep_fr_just_alive_ kernel
| WA> > config somewhere? then we only n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| TK> It should be pretty easy. You only need to add patches to the
| TK> linux-kexecboot recipe. It may be
| TK> a problem that the phones only have two buttons, but that could be
| TK> solved. The size of k
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I am new to the *OpenMoko* community and appreciate your patience.
| I am trying to compile a simple "Hello World" *kernel* module.
| I have downloaded the tool chain and am trying to compile the module as
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Adding the list back into the conversation
|
| On Mon, 2009-03-02 at 18:26 +0100, Thomas B wrote:
|> Thanks for your pointer! You mean this one?
|>
|>
http://downloads.openmoko.org/distro/unstable/NeoFreerun
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Am Sonntag, den 01.03.2009, 18:09 +0100 schrieb "Marco Trevisan
| (Treviño)":
|> Michael 'Mickey' Lauer wrote:
|>> Oh no. Please don't introduce SDL. We have something leaner and much
|>> better -- it's call
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| WA> This size is still a bit on the large side, tough. Andy and I have
| WA> been discussing this thing last week and we think that one could
| WA> bring the size down considerably by using SDL instead of X.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| This size is still a bit on the large side, tough. Andy and I have
| been discussing this thing last week and we think that one could
In fact I brought it up with several people including Werner.
| bring
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Thu, 2009-02-26 at 20:58 +0800, Andy Green wrote:
| Somebody in the thread at some point said:
| | Hi Angus,
| |
| | I have some questions about the images in Unstable>Neofreerunner
| |
| | 1) I se
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi Angus,
|
| I have some questions about the images in Unstable>Neofreerunner
|
| 1) I see 3 different kernels in the Unstable>neofreerunner-Andy
| tracking,OE,Stable.Which is the one we need to use for tes
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Wednesday 25 February 2009 21:07:52 Leonti Bielski wrote:
|> Hello!
|> Strange thing just happend to me - after upgrading gsm firmware I
|> decided to upgrade Qi as well.
|> I downloaded it from [1].
|> A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Werner,
|
| Something else I have been meaning to mention (it may not be an issue
| because it only occurs with your WLAN test kernel) but most of the time
| when I disconnect the USB cable from the FR (whet
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| "USB device controller allows bulk transfer with DMA, interrupt and
|control transfer."
|
| However, the document does not mention interrupt transfers anywhere
| else and IN_CSR2_REG, bit ISO, makes m
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|
http://downloads.openmoko.org/distro/experimental/NeoFreerunner/uImage-2.6.28-oe1+gitr34240a1c06ae36180dee695aa25bbae869b2aa26-r3-om-gta02.bin
This is literally 2.6.28? What's the lineage of it?
- -Andy
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| However, in that case, is it likely that it's more to do with the slow
| video bus (combined with single-buffered, non-accelerated graphics)
| than with the timings? Any estimates of how long the synchroni
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi -
If there was an effort to synthesize a VSYNC interrupt on Glamo (the
real thing doesn't exist), is there actually anyone who would use it?
Trying to figure out whether to close this as WONTFIX or have a go at it.
https://docs.openmoko.org/trac/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Strike! Thanks Andy, it works. One minor glitch is that after a wakeup
the
| programmed threshold (not the wakeup_threshold, the usual threshold)
seems to
| be reset but the sysfs still shows the same value
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| c_c writes:
|> In guitartuner, I'm using voice-recoding.state to grab samples from the
|> mic. But I'm facing a problem with that. If I get a call while the
program
|> is running, I get a kernel oops like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Wed, Feb 11, 2009 at 11:26:14AM +0530, Andy Green wrote:
|> -BEGIN PGP SIGNED MESSAGE-
|> Hash: SHA1
|>
|> Somebody in the thread at some point said:
|> | It looks as though it&#x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| It looks as though it's a known problem
|
| http://docs.openmoko.org/trac/ticket/2230
Yes it is known, I will try that git repack thing Holger mentions there
now I have a reliable internet connection for a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Michael 'Mickey' Lauer wrote:
> Am Friday 06 February 2009 19:44:19 schrieb raghav n:
>> Am just talking with no show code! I got this idea but not sure if its
>> already there. I use the power button to suspend the freerunner and to wake
>> it up too.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Werner Almesberger wrote:
> You may want to check if zcat /proc/config.gz | grep WAKELOCK yields
Yes I built a moredrivers kernel with outdated config by accident that
still had WAKELOCK. And it performed as advertised, resume correctly
worked, bu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green wrote:
|> GTA02 NOR U-Boot will then be incompatible with what we changed to.
|
| Yup, except for the first partition. By the way, since we may
| subdivide the kernel partition, we'll
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green wrote:
|> This opens a can of worms for Qi in terms of supporting GTA02 in the
|> field already with random dynparts to give access to the magic ext2
|> partition in NAND.
|
| One more
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Cool. Combining this with the initramfs/kexec stuff that's been
| discussed on the kernel list (cc'd here): the kexec kernel could very
| easily do the magic to read that address as you've described here,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Currently we have two patchsets - one generic OpenWrt-patchset for
| 2.6.28-kernels (located here:
|
https://svn.openwrt.org/openwrt/trunk/target/linux/generic-2.6/patches-2.6.28/),
| some little s3c46xx-re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| PS: What kernel git are most of the developers following for the
| FreeRunner these days? (just so I can jump up to speed)
You want
http://git.openmoko.org/?p=kernel.git;a=summary
andy-tracking branch.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi Radek / Andy,
|
| I tried with rootdelay=1 and did not succeed :confused:
|
| The following are the outputs on the LCM:
|
| With 2GB SD card: rootdelay=1
|
| lis302dl lis302dl.1: device BOOT reload failed
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Its not jffs2 partition. Its ext3 only.
| I tried ext3 also. It didn't work.
If your partition is actually ext2 somehow with no journal, it can also
fail that way.
If you have loglevel=8 and console=tty0,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| r...@om-gta02:~# kexec -l --command-line="rootfstype=jffs2
| root=/dev/mmcblk0p1 c
It's really jffs2 on partition 1 of the SD Card?
- -Andy
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.9 (GNU/Linux)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi Werner,
|
| I was able to load and run a Kernel using kexec by doing
| the following:
|
| a) Booted using Om 2008.12
| b) Placed a zImage in / directory.
| c) kexec -l zImage
| d) kexec -e
|
| Kernel pani
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> Have you run a cycle of your bouncing-ap-channel tests with maxperf?
| With the test that only produces the frequency change, the AR6k
| doesn't seem to crash anymore. The test is still limited by the
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| HSP. Also, I think I need a low pass filter. Can someone point me in the
| right direction?
Biquad filters are cheap and simple to do as integer and they're
flexible. There's a generic float implementatio
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hello All,
|
| I think this should be possible to route logs
| to the PC (USB device) instead of the default
| phone console.
|
| That is, What should I have to modify in the
| following to see my logs in PC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> There's no point altruistically researching Atheros
|> firmware bugs if it won't pay off for us?
|
| Why do you think it does not pay off for us if we look for solutions
| for problems our customers experi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green writes:
|> Well it can be avoided OK by not doing it, I am just wondering what it
|> leads to if the firmware is broken for some things and we don't have a
|> way to update it.
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green wrote:
|> If wpa_supplicant's automatic up and down action when it loses
|> association does that and hard resets everything on the module and
|> stack, it might avoid us hav
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green wrote:
|> So... it's a firmware problem we can't do anything about?
|
| We'll see. I haven't heard back from Atheros yet.
|
| Since the module duly reports when it has
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Frequency leakage is a complication inherent to the design of
| 802.11abg, so we're not seeing anything new here. The number of
| misses seems high, though. And of course none of this gives the
| firmware a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Is there a way for QI bootloader to show
| options if there are multiple distros in my SD?
| I dont know how to do it? In this context, does
| u-boot overweigh Qi or am i missing something
| about Qi for Mu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| A while ago, someone asked in a thread which I believe was on this
| list for a way to control whether WLAN gets powered down (and thus
| loses state) during suspend.
|
| Following the example of Larry Wall
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green wrote:
|> If I got the wrong idea, check that /boot/uImage-GTA02 exists on that
|> ext3 partition.
|
| By the way, it may help people making the jump from u-boot to Qi if
| they could just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi Andy,
|
|>> Did you download the Qi image again fresh, since -U had been overwriting
|>> it?
| Sorry Andy. I could not get your question. I did :
When you used -U option before, it writes data into the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi Andy,
|
| Sorry that I overlooked the dfu-util command for flashing
| QI Boot loader . It should be -D and I was given -U.
|
| But dfu-util fails saying:
| Starting download: [
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi Andy,
|
| Thank you for the imediate reply.
|
| I flashed the Qi image using the following command:
| [By booting GTA02 device in NOR flash mode]
|
| sudo dfu-util -a u-boot -R -U qi-s3c2442-master_a2d11c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi Andy,
|
| Sorry for not making it clear.
|
| Actually what happens is:
|
| 1) When I try booting
| (after flashing Qi into NAND from NOR flash mode and inserting SD card
| with ext3 partition containing A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi All,
|
| I tried modifying the bootloader from u-boot to Qi
| for booting Android from SD card. I booted the phone
| in NOR mode (aux first, power next) and then flashed the
| Qi bootloader using dfu-util
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy, this is the diff before the rotation and after the failed
| rotation (WS). How can I make sense of these values?
| (I guess I might have to - I haven't read docs yet).
Well, doesn't look like the res
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| I could rotate here but after one more attempt I got white screen :-/
| The behavior is not (apparently) deterministic because the first time
| I tried (now shown) I got the white screen immediately.
|
| Th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Are there any hardware engineers who can verify whether or not the
| touch-screen on the Neo or FR could register or generate motion-based
| events? If not, is this something that could be done easily in
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Monday 12 January 2009 20:54:17 Andy Green wrote:
|> Somebody in the thread at some point said:
|>
|> |> Perhaps we should resume this on linux-wireless, since I guess that's
|> |&g
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> Perhaps we should resume this on linux-wireless, since I guess that's
|> where all the rfkill folks hang out.
|
| Yes please do this, if you want.
Oh dear. I thought we almost had Werner writing the rfki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Monday 12 January 2009 17:00:13 Andy Green wrote:
|> No, it's a less than happy-making situation there are no updates and no
|> redistributable Linux firmware update tool.
|
| Ok, but the fi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Monday 12 January 2009 10:09:56 Andy Green wrote:
|> | - in the discussion on linux-wireless, Michael Buesch also mentioned
|> | that rfkill is expected to act "immediately".
|>
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green wrote:
|> Yeah I take it to mean when you return from the rfkill action, the
|> stopping of RF TX is done already. That sounds doable?
|
| We could introduce a synchronization point (cur
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green wrote:
|> It seems like it is turning off ieee80211 powersaving mode (the AP
|> beacon dropbox system) in order to have that kind of impact.
|
| You mean the synchronized wakeups ? Yes, it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green wrote:
|> maxperf is one of those names that makes you wonder why it isn't the
|> default.
|
| Alas, maximum performance also means maximum power burn:
|
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Monday 12 January 2009 00:48:20 Andy Green wrote:
|> Somebody in the thread at some point said:
|> | Hi All,
|> |
|> | Does anybody else here get 'fade outs' or other screen crashe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green wrote:
|> Can you provide a patch that does the changes you tried on both configs
|> and kill _MD support? Thanks.
|
| Just sent it, thanks.
|
| By the way, we also enable CONFIG_MMC_SD
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Regarding general reception issues, "GNUtoo" reported on IRC
| experiencing unstable associations with default settings, but that
| "wmiconfig -i eth0 --power maxperf" solved the problem.
maxperf is one of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green wrote:
|> Agree about that, we should move to modularized WLAN but last time I
|> tried this with Atheros stack I was completely unable to get it to work.
|> ~ Hopefully it's bette
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi All,
|
| Does anybody else here get 'fade outs' or other screen crashes when
trying to
| rotate the screen on latest FSO?
|
| xrandr -o 2 (rotate 180 degrees, stays portrait) works ok though.
Yes it's a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green writes:
|> I can see the logic, but why in U-Boot? Are people really sitting in
|> U-Boot and need more commands for stuff like charging?
|
| When the battery is very empty it would be n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| phil...@hug.cx writes:
|> diff --git a/board/neo1973/gta02/gta02.c b/board/neo1973/gta02/gta02.c
|> index a59a513..4255caa 100644
|> --- a/board/neo1973/gta02/gta02.c
|> +++ b/board/neo1973/gta02/gta02.c
|>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Nelson Castillo wrote:
|> I thought that we needed to have a small mach-gta02.c that works in
mainline.
|
| I don't think this is a condition for getting the design reviewed by
| upstream. People will mainly
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Thursday 08 January 2009 23:32:34 Nelson Castillo wrote:
|
|> I feel you're trying to tell us there is a single path to solving the
|> problem and that we
|> are failing to follow it...
|
| Sorry that I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Thursday 08 January 2009 20:38:42 you wrote:
|
|> | have and maintain code that is doing that.
|>
|> The implementation already exists.
|
| Cool what prevents the kernel team from presenting the patches
u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Thursday 08 January 2009 16:58:32 Andy Green wrote:
|> Somebody in the thread at some point said:
|> |1.) Get the code upstream into the linux kernel
|>
|> We feel showing it can remove
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| 1.) Get the code upstream into the linux kernel
We feel showing it can remove the need for tslib gives us a story that
gives a better chance upstream.
| Our Company goal is to use upstream stuff, by
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi,
|
| --- On Wed, Jan 7, 2009 at 7:06 PM, Andy Green wrote:
| | jtag_speed 0
| |
| | Try increasing this, despite "speed" it actually means "delay".
| |
| | Also, only certain magic l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Wednesday 07 January 2009 14:27:57 Andy Green wrote:
|> | It's not the firmware. It started after I switched to 2.6.28 and the
|> newer
|> | frameworkd.
|>
|> Fair enough, maybe Werne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| jtag_speed 0
Try increasing this, despite "speed" it actually means "delay".
Also, only certain magic libftdi versions work, IIRC 0.8 is good.
- -Andy
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hmm.. not sure if I agree here. IMO resume should reinstate the
situation as
| it was at suspend. NM or any userspace process could then decide what
to do if
| it notices the AP has disappeared.
It's not n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Wednesday 07 January 2009 13:44:36 Andy Green wrote:
|> Somebody in the thread at some point said:
|> |> Thanks for the report about it, what does enabled or disabled mean for
|> |> Wifi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| => 2.6.28
| * Framework already supports both kernels (.24 & .28).
| * Next FSO milestone will come with support for both kernels. If .28
proves to
| be stable enough in the coming weeks .24 support may be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|> Thanks for the report about it, what does enabled or disabled mean for
|> Wifi? Say if it is in "disabled" situation, what does that look like?
|
| eth0 is up but lost its IP, wireless is not associated.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| In the end I only had to change bitbake's conf/local.conf and include
these
| lines to move over to 2.6.28 + comaptible frameworkd:
|
| PREFERRED_PROVIDER_virtual/kernel = "linux-openmoko-devel"
| PREFERRED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Maybe later, if that's done, people will start to wonder why tslib is
| still necessary when we have a clean input device, but it's not today's
| problem directly for us.
|
|> the problem is - a newer devic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| all in all - the point here isn't to remove tslib - just turn off
| tslib's filtering! keep it. just disable what you don't need anymore!
Yes that's the default situation we are at right now.
But, there i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Friday 26 December 2008 22:36:42 Andy Green wrote:
|
|> No the kernel touchscreen filter stuff is independent of the driver, it
|> is implemented separately and resuably.
|
| Ah okay. From
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Friday 26 December 2008 21:38:14 Andy Green wrote:
|
|> | for evdev and the calibration data?
|>
|> It's a good point, is there a way to associate the input event device
|> that sends
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
|>>> With the latest kernel we can use the Touchscreen with no further
|>>> user-space filtering. I'd like to test this.
|>> What is the benefit?
|> Briefly stated: We think it's better if the driver sends on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hello,
|
| I have just flashed the three devices I'm working on, with the
| latest version (Om2008.8), and it seems there's a bug related to the
| Bluetooth Device. Although it is enabled:
|
| r...@om-gt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hello!
| This question is mostly for Andy, but since it might be useful for
| other users I decided to post it on ML too.
|
| So, what exactly is different in system paths in rootfs between old
| kernel and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| This is a multipart question about the Openmoko Freerunner. I
| basically want to know about the sound states the device can support,
| and currently supports.
Most of these things are possible, have a rea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| thanks for your mail.
| This is what I got by use the command:
| [EMAIL PROTECTED]:~# cat /proc/version
| Linux version 2.6.24
This is still old stable branch stuff. You mentioned -->
|> | Kernel testin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Kernel testing-om-gta02-20081202.uImage.bin
| testing-om-gta02-20081210.uImage.bin
| boot time, several small things. BUT, the critical bugs still there.
| #1482 [oe]AUX bottom doesn't shine
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi,
|
| 2008/12/9 Graeme Gregory <[EMAIL PROTECTED]>:
|> On Mon, 2008-12-08 at 21:10 +, Thomas White wrote:
|>> A practical DRM module will look very different indeed, but I thought
|>> I'd publish this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
Two threads are going on internal list I will reply to combined here...
I am not at all an Xorg guy and for sure there will be better comment
out here especially considering the stuff going on around Glamo 2D
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Hi All,
|
| I had some questions .Probably a stupid question but I really want to
know how
| neo should work ,rather behave in such scenarios.
|
| Scenario 1:
| 1)when the neo is connected to charger/USB and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Could you describe this in more detail,
|
| Where do i type these commands ?
|
| Andy Green wrote:
|> Somebody in the thread at some point said:
|> | Latest uImage-android seems to be broken - uboot
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Andy Green wrote:
|> -BEGIN PGP SIGNED MESSAGE-
|> Hash: SHA1
|>
|> Somebody in the thread at some point said:
|> | Latest uImage-android seems to be broken - uboot gives Bad data C
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| Latest uImage-android seems to be broken - uboot gives Bad data CRC
| message with it.
| Can anybody post some older uImage-android ?
No this is caused by U-Boot's default environment only pulling in 2MB
fr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Somebody in the thread at some point said:
| On Thu, 04 Dec 2008 17:29:36 -
| "Openmoko Public Trac" <[EMAIL PROTECTED]> (OPT) wrote:
|
|> #1841: white screen of death (WSOD) after resume
|>
-
---+--
1 - 100 of 259 matches
Mail list logo
