Werner,
To reiterate - I am using:
wlan-trial-20090206.uImage
openmoko-fso-image-glibc-ipk--20090202-om-gta02.rootfs.jffs2
while trying to use u-boot (NOR) with:
setenv bootargs_base \${bootargs_base} log_buf_len=2M
setenv bootcmd setenv bootargs \${bootargs_base} \${mtdparts}\; nan
On Thu, 2009-02-12 at 15:17 -0800, Truedat101 wrote:
> Not sure what the status is on these openmoko scripts like env and
> download.sh, but these previous posts are related:
> http://lists.openmoko.org/nabble.html#nabble-td2185294
> http://lists.openmoko.org/nabble.html#nabble-td1633573|a1633573
>
Since I now have a small army of WRT54G(L) APs, I put Tomato 1.22 on
one of them, in an attempt to reproduce Mickey's famous bug #1250:
https://docs.openmoko.org/trac/ticket/1250
The test consisted of setting the AP to open, b/g mixed, the preamble
according to the table below, cycling (unbind/bin
I concur. Found the same using you instructions. Investigating workaround.
And as the env script provided with the current snapshot is out of date
(download_dir does not exist at the default url), this seems to be broken
out of the box. Affects also the proper working of MokoMakefile 'make qe
Not sure what the status is on these openmoko scripts like env and
download.sh, but these previous posts are related:
http://lists.openmoko.org/nabble.html#nabble-td2185294
http://lists.openmoko.org/nabble.html#nabble-td1633573|a1633573
The download_dir appears to not exist and/or no longer be co
Same problem when making qemu. I get the "Kernel is ... not found".
Investigating why.
Sincere Trout wrote:
>
> Hi,
>
> I am having problem while building Openmoko on QEmu. I go an error saying
> "Kernel is... not found" when I run openmoko/flash.sh. So I changed the
> env file on following
Hey Guys,
roh just setup gitosis to have more fine grained access control to
git.openmoko.org and ease creating new repositories and you will need to carry
out the following change in order to be able to fetch and push.
In .git/config change from:
[remote "origin"]
url = git+ssh://g...
Werner,
Werner Almesberger wrote:
> Philip Rhoades wrote:
>> The memory for the larger kernel does not stick between boots so I have
>> to do:
>
> Hmm, there's something weird about how your device boots. Are you
> loading u-boot from NAND or from NOR ? When you bring up the boot
> menu, it sa
-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/
Philip Rhoades wrote:
> The memory for the larger kernel does not stick between boots so I have
> to do:
Hmm, there's something weird about how your device boots. Are you
loading u-boot from NAND or from NOR ? When you bring up the boot
menu, it says at the top whether it's NAND or NOR.
For all
10 matches
Mail list logo