Hi Torfinn
> > with the SD card inserted, I see no bootmenu - it just boots
> /dev/mmcblk0p2
> > every time.
> > What's wrong?
>
> You forgot to tell Qi not to boot from the SD partitions. See:
> http://wiki.openmoko.org/wiki/Qi#Files
>
> According to the readme[1] on the q
Hi Werner,
Werner Almesberger wrote:
> There are many component choices for future phones. Things to consider
> when choosing chips include:
> - are they available (to us) ?
>
What's the yard stick for measuring against here? I.e. are we talking
about one-off from digikey/farnell, samples
Laszlo KREKACS wrote:
> There is also the openpandora project:
> http://www.open-pandora.org/index.php?option=com_content&view=category&layout=blog&id=2&Itemid=2&lang=en
>
> Is it unsuitable for a phone because of power inefficiency?
> Can be the "ARM Cortex-A8 600Mhz" used in a future phone?
>
Warren Baird wrote:
> I meant that it should *constrain* the behaviour of rotation - more or
> less like omnewrotate behaves now, but skipping over the two
> 'incorrect' orientations.
>
> so if the app says 'landscape', it's still flip between xrandr -o 1
> and xrandr -o 3 as you rotate the pho
Rui Miguel Silva Seabra wrote:
> On Tue, Nov 10, 2009 at 12:08:06PM +0000, Dave Ball wrote:
>> However, what's the use-case for an application requesting either of the
>> inverted states? I can't see when those would be useful - in terms of
>> hints the app would
Warren Baird wrote:
> perhaps the landscape / portrait flag should just contrain the
> rotation? So if you flip the phone 180 degrees, you get the
> 'expected' behaviour, but if you just flip it 90 degrees nothing changes?
Given that these properties are for the orientation an application
req
Rui Miguel Silva Seabra wrote:
> On Tue, Nov 10, 2009 at 12:00:31AM +0000, Dave Ball wrote:
>> option1: New atoms in the _NET_WM_STATE property.
>> - _NET_WM_STATE_LANDSCAPE
>> - _NET_WM_STATE_PORTRAIT
>>
>> If neither is present for a given window, WM can choos
Carsten Haitzler (The Rasterman) wrote:
wm needs to track both and determine which one takes precedence based
on policy and th en implement that rotation, if needed. policy is what
a wm implements - that's the nature of the beast. that policy may be
hard-coded in the wm or configuration for it.
Carsten Haitzler (The Rasterman) wrote:
> On Sun, 08 Nov 2009 04:37:07 +0000 Dave Ball said:
>
>> Is there a quick-start guide for writing an e module, maybe some simple
>> code / example?
>>
>
> http://www.rasterman.com/files/logo-0.0.1.tar.gz
&g
Carsten Haitzler (The Rasterman) wrote:
> wm needs to track both and determine which one takes precedence based
> on policy and th en implement that rotation, if needed. policy is what
> a wm implements - that's the nature of the beast. that policy may be
> hard-coded in the wm or configuration
Carsten Haitzler (The Rasterman) wrote:
> On Sun, 08 Nov 2009 02:03:47 +0000 Dave Ball said:
>
>
>> Sounds like we should be using window properties for passing hints to
>> the WM, and dbus for getting orientation information from the
>> accelerometer
Carsten Haitzler (The Rasterman) wrote:
> On Sat, 7 Nov 2009 19:46:28 + Rui Miguel Silva Seabra
> said:
>
>> Being X properties or DBUS, it's the same for me. DBUS seems more natural as
>> there's probably less pooling, but then I know only a bit more of DBUS than
>> of X11 (which AFAIR wa
Dr. H. Nikolaus Schaller wrote:
> What I wonder is why nobody did fix u-boot if it had problems with
> bigger kernels.
>
I'm just a bystander here, but from what I understood this wasn't the
reason Qi was started.
u-boot is an entire environment that needs drivers for a lot of the
hardware
Andrew Stephen wrote:
> 2009/7/28 Warren Baird :
>
>> looks great - I took the liberty of adding the version #'s into the output
>> created by the template, so you can see the version #'s on the draft
>> community page.
>>
>> My preference is '8a'
>>
>
> I vote for 8a also.
>
>
8a was th
Patryk Benderz wrote:
> [cut]
>
>> associated with each table. If that doesn't work, in my mind a simple
>> 1px gray light border would work better than the block colours, which
>> can be a little over-powering.
>>
> 1 px added for you where relevant. Tell me how do you like it now.
>
Jon 'maddog' Hall wrote:
>> I assume you would like to modify V1, but could you explain how more
>> precisely?
> I like the over-all look of V1, but I also like the "working hardware"
> box. By putting the "working hardware" box in a column by itself,
> making a three-column layout, you reduce th
Hi Maddog,
>> it certainly sounds like an amazing opportunity, almost too good to be true
>> - what's the catch! :-)
>>
> I hope that you will find there is no "catch". If you do think there is
> a "catch", please tell me.
>
Thanks again for bringing this to us, and the detailed respon
Jon 'maddog' Hall wrote:
> So organize your needs. Reach out to your own universities and software
> usability development groups. Get them to join the project.
>
> Don't give up. If you look closely, you can see the light at the end of
> the tunnel. It may be faint, but I have seen similar tun
Rui Miguel Silva Seabra wrote:
> On Thu, Jul 16, 2009 at 01:16:09PM +0100, Michael Sheldon wrote:
>
>> Alex Teiche wrote:
>>
>>> Hello everyone,
>>>
>>> I recently recieved my A6 FreeRunner, and have been looking for some coding
>>> to do:) I plan on writing a chat application(similar to P
Hi Maddog,
[added cc to gta02-core list]
Thanks for looking into this - it certainly sounds like an amazing
opportunity, almost too good to be true - what's the catch! :-)
Do you know how Dr Zuffo sees the universities involvement with, and
relationship to the rest of the community - i.e. do
Risto H. Kurppa wrote:
> Thanks Sean for this announcement!
>
> It's appreciated to get a status update from OM of things we've heard
> rumors of. I'm very happy that OM got this far with the phones: we
> have some tens of thousands (better guess anyone?) of Linux phones
> around the world, various
Rui Miguel Silva Seabra wrote:
> On Wed, Jun 03, 2009 at 12:30:21AM +0400, Alexander Chemeris wrote:
>
>> On Tue, Jun 2, 2009 at 8:44 PM, Rui Miguel Silva Seabra
>> wrote:
>>
>>> For now, I'm hoping my Freerunner improves enough to last long, as I don't
>>> expect another Free Software ph
Martin Bernreuther wrote:
>> One thought is that future phones should include two uSD cards - one
>> 'internal' for OS/kernel etc. and one that is 'removable' for data
>> storage/exchange - although this is out of scope for GTA02-core.
s/should/could.
Obviously there isn't any commitment to futu
Max wrote:
> Are there plans to change uSD placeholder?
No - changing uSD holder isn't part of the GTA02-core plans.
In GTA02-core the intention is that the uSD card contains the full OS
image including kernel. The NAND will only contain QI, and the
expectation is that QI won't need to be re-
GNUtoo wrote:
> *will the sound quality be ok(is there a plan to correct the problematic
> capacitor that is between the sound card and the audio connector)? and
> will it fit into the same case than the GTA02...because if I understood
> well the sound problem can't or is too difficult to fix well(
Toni Mueller wrote:
>> They chose a 100% GPL layout tool, KiCAD
>> (http://en.wikipedia.org/wiki/Kicad), which uses only text-based
>> files
>
> This sounds good, but you seem to require a certain minimum version of
> Kicad, right? Checking out from OM and running Lenny's Kicad produced
> le
David Reyes Samblas Martinez wrote:
> 2009/5/18 Rui Miguel Silva Seabra :
>
>> On Mon, May 18, 2009 at 07:20:13PM +0200, arne anka wrote:
>>
http://wiki.openmoko.org/wiki/Gta02-core
>>> sounds interesting.
>>> could someone add background information why parts change?
>>>
Werner Almesberger wrote:
> Wolfgang Spraul wrote:
>
>> Today Openmoko released additional pieces of documentation about
>> Freerunner hardware: board outline, footprints and netlist.
>>
>
> This is great. Thanks a lot to you and everyone in Openmoko who has
> helped to make this happen !
28 matches
Mail list logo