xpcom and javascript
hi, i'm trying to make an activity out of a javascript application. i load the page into a hulahop webview-widget and i can access the dom with xpcom to save the state to the journal. for restoring the state i need to call a javascript function and i wasn't able to figure out how to do this. if someone knows how to do this or if someone has another solution to this problem it would be great. thanks chrigi ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: WPA - testing
Works for me on a Sitecom WL-174 WPA-PSK network. One of yesterdays joyrides. - Pascal. It's fixed yeah, that's why I'm asking to test it with a recent build. Ticket #5044. It went in joyride two weeks ago. It's reported working in both joyride and 657. Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: xpcom and javascript
i just like to call javascript functions in general. i checked in an example: http://dev.laptop.org/git?p=projects/comic-maker;a=blob_plain;f=comicmakeractivity.py;hb=HEAD Marco Pesenti Gritti schrieb: On Dec 13, 2007 9:39 AM, Christian Reichlin [EMAIL PROTECTED] wrote: hi, i'm trying to make an activity out of a javascript application. i load the page into a hulahop webview-widget and i can access the dom with xpcom to save the state to the journal. for restoring the state i need to call a javascript function and i wasn't able to figure out how to do this. Which javascript function? Btw do you have the code somewhere? It sounds interesting. Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: xpcom and javascript
On Dec 13, 2007 11:13 AM, Christian Reichlin [EMAIL PROTECTED] wrote:
i just like to call javascript functions in general.
i checked in an example:
http://dev.laptop.org/git?p=projects/comic-maker;a=blob_plain;f=comicmakeractivity.py;hb=HEAD
Give a try to web_view.evaluate_script('hello()') with the latest
hulahop git. It seem to work but I didn't really test it extensively.
Marco
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
New joyride build 1415
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build1415/ -Read-35.xo +Read-36.xo -Web-78.xo +Web-79.xo -atlas.i386 0:3.6.0-11.fc6 +atlas.i386 0:3.6.0-11.fc7.1 -evince-olpc.i386 0:0.3-1 -gnome-vfs2.i386 0:2.18.1-6.olpc2 +gnome-vfs2.i386 0:2.18.1-7.olpc2 -kernel.i586 0:2.6.22-20071204.2.olpc.9679b65c8c5ed6e +kernel.i586 0:2.6.22-20071213.5.olpc.fa094abd8cdf4d6 -poppler.i386 0:0.5.4-7.fc7 +poppler.i386 0:0.6.2-4.olpc2 +sugar-evince.i386 0:2.20.0-1 -telepathy-gabble.i386 0:0.7.1-0.7.olpc2 +telepathy-gabble.i386 0:0.7.1-0.8.olpc2 -telepathy-salut.i386 0:0.2.0-1.olpc2 +telepathy-salut.i386 0:0.2.0-2.olpc2 --- sugar-evince.i386 2.20.0-1 --- * New evince v2.20, support embedding in python applications --- Read-36 --- * Support evince v2.20 * Some search improvements --- Web-79 --- * Missing file for: Open an uri of type text/uri-list with browse #5080 -- This email was automatically generated Aggregated logs at http://dev.laptop.org/~bert/joyride-pkgs.html ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Unable to initialize camera (via mmap interface)
On Wed, 2007-12-12 at 16:03 -0800, Peter Krenesky wrote:
Hi all,
I'm trying to initialize the camera device and running into some
errors. I'm attempting to use the mmap interface initialized by
VIDIOCGMBUF ioctl. the ioctl is returning -1 and errno is 22.
Is VIDIOCGMBUF/mmap even supported by the driver/device? If so, any
ideas on what can be going wrong?
What's normally used right now to get video out of the device is
GStreamer. You can see what GStreamer is doing from the stuff in
v4l2src_calls.c. Specifically, look at gst_v4l2src_capture_init(). You
probably want to use the QBUF/DQBUF functionality.
Dan
Here is the c++ code that is causing the problem:
video_mbuf mmap_buf_info;
if (-1 == ioctl(vidfd, VIDIOCGMBUF, mmap_buf_info))
{
printf (ERROR: %i \n, errno);
close();
return(HXR_ENC_NO_VIDEO_CAPTURE);
}
thanks,
-peter
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: Unable to initialize camera (via mmap interface)
I'm trying to initialize the camera device and running into some errors. I'm attempting to use the mmap interface initialized by VIDIOCGMBUF ioctl. the ioctl is returning -1 and errno is 22. The problem, almost certainly, is that VIDIOCGMBUF is a V4L1 command, while the camera driver implements the V4L2 API. Almost everything from V4L1 can be mapped over, but VIDIOCGMBUF makes assumptions about the placement of DMA buffers which cannot be guaranteed with V4L2. In particular, it wants them all to be contiguous in memory. Due to the way the cafe_ccic driver works, filling in support for VIDIOCGMBUF is actually feasible, though not entirely trivial. Far better, if at all possible, would be to use the V4L2 API, which (like high-definition TV and IPv6) is definitely the way of the future. Someday. jon Jonathan Corbet / LWN.net / [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New update.1 build 656
On Dec 13, 2007 2:19 AM, Bernardo Innocenti [EMAIL PROTECTED] wrote: On 12/13/07 00:58, Build Announcer Script wrote: +compat-libstdc++-33.i386 0:3.2.3-61 Why do we even need this? I don't know, but it's explicitly listed in pilgrim as a package to install. joyride has had it, but due to the way that ship.2 was built, it did not. If no one on devel can remember why it was present, I can remove it from pilgrim. J5 added it on Mon Mar 26 18:39:45 2007 -0400 with the commit message, added compat-libstdc++-33. http://dev.laptop.org/git?p=users/cscott/pilgrim;a=commitdiff;h=6264353082f6542cbd4168ec5b7abea9a486d506 cc'ing J5; maybe he remembers why this was done? --scott -- ( http://cscott.net/ ) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: WPA - testing
Some people are experiencing problems with the latest joyride, looking like a firmware/kernel regression. See #5485. Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New update.1 build 656
Its for Opera I think or perhaps for the old flash. A lot of closed source applications need it because they compile once for all Linux platforms they support meaning lowest common denominator. It might be that we are past that point but I am not entirely sure. On Thu, 2007-12-13 at 09:57 -0500, C. Scott Ananian wrote: On Dec 13, 2007 2:19 AM, Bernardo Innocenti [EMAIL PROTECTED] wrote: On 12/13/07 00:58, Build Announcer Script wrote: +compat-libstdc++-33.i386 0:3.2.3-61 Why do we even need this? I don't know, but it's explicitly listed in pilgrim as a package to install. joyride has had it, but due to the way that ship.2 was built, it did not. If no one on devel can remember why it was present, I can remove it from pilgrim. J5 added it on Mon Mar 26 18:39:45 2007 -0400 with the commit message, added compat-libstdc++-33. http://dev.laptop.org/git?p=users/cscott/pilgrim;a=commitdiff;h=6264353082f6542cbd4168ec5b7abea9a486d506 cc'ing J5; maybe he remembers why this was done? --scott -- John (J5) Palmieri [EMAIL PROTECTED] ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 1417
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build1417/ -TamTamSynthLab-45.xo +TamTamSynthLab-46.xo --- TamTamSynthLab-46 --- * Swapped trackpad icons (Olipet) * Corrected output volume (Olipet) * Fixed a bug that prevented sound samples from loading (Olipet) -- This email was automatically generated Aggregated logs at http://dev.laptop.org/~bert/joyride-pkgs.html ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Help wanted: video demo!
Hi Guys, here's our cute XO playing a video in fullscreen mode thanks to mplayer :) http://dev.laptop.org/~rverdejo/video_samples/MPlayerFullSize01_mpeg41000_mp2128_622x520.avi cheers! Reynaldo Verdejo and Eduardo Silva. On Dec 12, 2007 4:17 AM, Sameer Verma [EMAIL PROTECTED] wrote: C. Scott Ananian wrote: We need a demo which shows off the full-screen video capabilities of the XO. Unfortunately, Record compresses its input rather heavily, so it's not a great demo for video playback. We bundle the Ogg Theora codecs, and Browse can play media files full-screen, so the first step is for someone to invest some time in transcoding an appropriate demo movie (I suggest http://www.elephantsdream.org/ -- some ogg transcoding linked from http://wiki.xiph.org/index.php/Elephants_Dream ) to an appropriate bit rate / size for the XO. Make it look good! It looks like there are a couple of Ogg Theora versions of the Elephant's Dream at http://files.akl.lt/video/Elephants%20Dream/. Encoded in Stereo at 512x288 (52MB) and 1024x576 (161MB). What rate/size would be appropriate for the XO? Sameer -- Dr. Sameer Verma, Ph.D. Associate Professor of Information Systems San Francisco State University San Francisco CA 94132 USA http://verma.sfsu.edu/ http://opensource.sfsu.edu/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: WPA - testing
Michail, We have two other critical bug fixes that require us to do a build today and get it out asap. I had put the new firmware on that list to get into the new build, but we really have to understand if this bug is real. If you and Ricardo can look at this today (build is scheduled for 5pm), that would be great! Otherwise, I think the risk is too high to include 20.p47. Other thoughts? Kim On Dec 13, 2007 11:41 AM, Marco Pesenti Gritti [EMAIL PROTECTED] wrote: Some people are experiencing problems with the latest joyride, looking like a firmware/kernel regression. See #5485. Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Help wanted: video demo!
That's a proprietary format. Couldn't you have used Theora like the OP suggested? On 12/13/07, Eduardo Silva [EMAIL PROTECTED] wrote: Hi Guys, here's our cute XO playing a video in fullscreen mode thanks to mplayer :) http://dev.laptop.org/~rverdejo/video_samples/MPlayerFullSize01_mpeg41000_mp2128_622x520.avi cheers! Reynaldo Verdejo and Eduardo Silva. On Dec 12, 2007 4:17 AM, Sameer Verma [EMAIL PROTECTED] wrote: C. Scott Ananian wrote: We need a demo which shows off the full-screen video capabilities of the XO. Unfortunately, Record compresses its input rather heavily, so it's not a great demo for video playback. We bundle the Ogg Theora codecs, and Browse can play media files full-screen, so the first step is for someone to invest some time in transcoding an appropriate demo movie (I suggest http://www.elephantsdream.org/ -- some ogg transcoding linked from http://wiki.xiph.org/index.php/Elephants_Dream ) to an appropriate bit rate / size for the XO. Make it look good! It looks like there are a couple of Ogg Theora versions of the Elephant's Dream at http://files.akl.lt/video/Elephants%20Dream/. Encoded in Stereo at 512x288 (52MB) and 1024x576 (161MB). What rate/size would be appropriate for the XO? Sameer -- Dr. Sameer Verma, Ph.D. Associate Professor of Information Systems San Francisco State University San Francisco CA 94132 USA http://verma.sfsu.edu/ http://opensource.sfsu.edu/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: WPA - testing
Kim, 1. I don't think that this alleged bug is related to the firmware 2. Even if it is, the benefits of 20.p47 far outweigh the risk of (further) breaking WPA. M. Kim Quirk [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 12/13/2007 01:42 PM To Marco Pesenti Gritti [EMAIL PROTECTED] cc Dan Williams [EMAIL PROTECTED], Ricardo Carrano [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], Jim Gettys [EMAIL PROTECTED] Subject Re: WPA - testing Michail, We have two other critical bug fixes that require us to do a build today and get it out asap. I had put the new firmware on that list to get into the new build, but we really have to understand if this bug is real. If you and Ricardo can look at this today (build is scheduled for 5pm), that would be great! Otherwise, I think the risk is too high to include 20.p47. Other thoughts? Kim On Dec 13, 2007 11:41 AM, Marco Pesenti Gritti [EMAIL PROTECTED] wrote: Some people are experiencing problems with the latest joyride, looking like a firmware/kernel regression. See #5485. Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: WPA - testing
Ok - WPA works in 657 and in joyride 1407 in the whole stack (UI to firmware). - WPA support is broken in joyride 1416. - We knew it before and we have now even more reasons to believe this is not related to the firmware (since both 1407 and 1416 run 20.p47 and 657 runs 20.p42) and since WPA worked via wpa_supplicant. - Whatever changed between 1407 and 1416 seem to have really crashed WPA support, I mean, now we cannot set it to work via wpa_supplicant anymore. - 20p47 as far as my tests go is ok. It addresses wds and mitigates #4470 (p42 did it actually). It also removes unnecessary probe responses. It is not #5194 resistant yet (Marvell is working on that front and we are testing). -- Ricardo Carrano -- Original Message --- From: Kim Quirk [EMAIL PROTECTED] To: Marco Pesenti Gritti [EMAIL PROTECTED] Cc: Ricardo Carrano [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Sent: Thu, 13 Dec 2007 13:39:36 -0500 Subject: Re: WPA - testing Michail, We have two other critical bug fixes that require us to do a build today and get it out asap. I had put the new firmware on that list to get into the new build, but we really have to understand if this bug is real. If you and Ricardo can look at this today (build is scheduled for 5pm), that would be great! Otherwise, I think the risk is too high to include 20.p47. Other thoughts? Kim On Dec 13, 2007 11:41 AM, Marco Pesenti Gritti [EMAIL PROTECTED] wrote: Some people are experiencing problems with the latest joyride, looking like a firmware/kernel regression. See #5485. Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel --- End of Original Message --- ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: WPA - testing
Ricardo Carrano [EMAIL PROTECTED] wrote on 12/13/2007 02:54:11 PM: - Whatever changed between 1407 and 1416 seem to have really crashed WPA support, I mean, now we cannot set it to work via wpa_supplicant anymore. Maybe something as simple as actually rebuilding wpa_supplicant? M.___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: WPA - testing
Kim asked me to post this here. Here is the idea for today's build. Based on 650 + (1) whatever was fixed to make WPA work in UI (2) p47 libertas fw. Premises: - 657: Is not in good shape (confimed by Alex Latham) - 650: WPA is broken, 657 WPA works. - Our tests reveal that 20p47 is the fw to ship. Mihalis just confirmed this. Marco, It seems that you are the person that can do (1), right? -- Ricardo Carrano -- Original Message --- From: Ricardo Carrano [EMAIL PROTECTED] To: Kim Quirk [EMAIL PROTECTED], Marco Pesenti Gritti [EMAIL PROTECTED] Cc: [EMAIL PROTECTED], [EMAIL PROTECTED] Sent: Thu, 13 Dec 2007 16:54:11 -0300 Subject: Re: WPA - testing Ok - WPA works in 657 and in joyride 1407 in the whole stack (UI to firmware). - WPA support is broken in joyride 1416. - We knew it before and we have now even more reasons to believe this is not related to the firmware (since both 1407 and 1416 run 20.p47 and 657 runs 20.p42) and since WPA worked via wpa_supplicant. - Whatever changed between 1407 and 1416 seem to have really crashed WPA support, I mean, now we cannot set it to work via wpa_supplicant anymore. - 20p47 as far as my tests go is ok. It addresses wds and mitigates #4470 (p42 did it actually). It also removes unnecessary probe responses. It is not #5194 resistant yet (Marvell is working on that front and we are testing). -- Ricardo Carrano -- Original Message --- From: Kim Quirk [EMAIL PROTECTED] To: Marco Pesenti Gritti [EMAIL PROTECTED] Cc: Ricardo Carrano [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] Sent: Thu, 13 Dec 2007 13:39:36 -0500 Subject: Re: WPA - testing Michail, We have two other critical bug fixes that require us to do a build today and get it out asap. I had put the new firmware on that list to get into the new build, but we really have to understand if this bug is real. If you and Ricardo can look at this today (build is scheduled for 5pm), that would be great! Otherwise, I think the risk is too high to include 20.p47. Other thoughts? Kim On Dec 13, 2007 11:41 AM, Marco Pesenti Gritti [EMAIL PROTECTED] wrote: Some people are experiencing problems with the latest joyride, looking like a firmware/kernel regression. See #5485. Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel --- End of Original Message --- ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel --- End of Original Message --- ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: WPA - testing
On Dec 13, 2007 9:50 PM, Ricardo Carrano [EMAIL PROTECTED] wrote: Kim asked me to post this here. Here is the idea for today's build. Based on 650 + (1) whatever was fixed to make WPA work in UI (2) p47 libertas fw. Premises: - 657: Is not in good shape (confimed by Alex Latham) - 650: WPA is broken, 657 WPA works. - Our tests reveal that 20p47 is the fw to ship. Mihalis just confirmed this. Marco, It seems that you are the person that can do (1), right? Yeah, working on it. Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 1418
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build1418/ -Pippy-12.xo +Pippy-14.xo --- Pippy-14 --- * Pippy can now create activity bundles of user code, using the Keep As Bundle icon on the toolbar! (From C. Scott Ananian.) -- This email was automatically generated Aggregated logs at http://dev.laptop.org/~bert/joyride-pkgs.html ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: WPA - testing
On Thu, 2007-12-13 at 15:14 -0500, Michail Bletsas wrote: Ricardo Carrano [EMAIL PROTECTED] wrote on 12/13/2007 02:54:11 PM: - Whatever changed between 1407 and 1416 seem to have really crashed WPA support, I mean, now we cannot set it to work via wpa_supplicant anymore. Maybe something as simple as actually rebuilding wpa_supplicant? I'd look first at what changed between builds... If the supplicant hasn't been updated for quite a while (it shouldn't have been) then it's much less likely to be a problem. I'm not sure what a rebuild would solve here... Dan ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: WPA - testing
On Dec 13, 2007 10:24 PM, Dan Williams [EMAIL PROTECTED] wrote: On Thu, 2007-12-13 at 15:14 -0500, Michail Bletsas wrote: Ricardo Carrano [EMAIL PROTECTED] wrote on 12/13/2007 02:54:11 PM: - Whatever changed between 1407 and 1416 seem to have really crashed WPA support, I mean, now we cannot set it to work via wpa_supplicant anymore. Maybe something as simple as actually rebuilding wpa_supplicant? I'd look first at what changed between builds... If the supplicant hasn't been updated for quite a while (it shouldn't have been) then it's much less likely to be a problem. I'm not sure what a rebuild would solve here... http://dev.laptop.org/~bert/joyride-pkgs.html The only relevant change between 1407 and 1418 *seem* to be kernel. Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: WPA - testing
md5sum for the supplicant haven't changed. -- Original Message --- From: Dan Williams [EMAIL PROTECTED] To: Michail Bletsas [EMAIL PROTECTED] Cc: Ricardo Carrano [EMAIL PROTECTED], [EMAIL PROTECTED] Sent: Thu, 13 Dec 2007 16:24:14 -0500 Subject: Re: WPA - testing On Thu, 2007-12-13 at 15:14 -0500, Michail Bletsas wrote: Ricardo Carrano [EMAIL PROTECTED] wrote on 12/13/2007 02:54:11 PM: - Whatever changed between 1407 and 1416 seem to have really crashed WPA support, I mean, now we cannot set it to work via wpa_supplicant anymore. Maybe something as simple as actually rebuilding wpa_supplicant? I'd look first at what changed between builds... If the supplicant hasn't been updated for quite a while (it shouldn't have been) then it's much less likely to be a problem. I'm not sure what a rebuild would solve here... Dan --- End of Original Message --- ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: connection to jabber.laptop.org
On Dec 13, 2007, at 1:05 PM, Giannis Galanis wrote:
I also installed the rpm in custom machine(not a school server) in
1CC.
I must note that the ejabberdctl-extra.diff patch in the wiki page
is for another version than 1.1.4.
I used the config file ejabberd.cgf which I got from
jabber.laptop.org
John, I didnt use the jtest account, but omicron which danny
created for me last week. I got the file from /home/wad
The accounts are not registered in the ejabberd.cfg file. They are
kept in database (which can
be dumped and reloaded using ejabberdctl). Thus, omicron doesn't
have an account on your new machine.
I couldnt register the admin account(is this necessary? because it
is not stated in the wiki)
This is absolutely necessary, and was the sticking point for me last
week on a schoolserver.
I tried:
ejabberdctl register localhost admin admin (according to wiki)
ejabberdctl ejabberd register admin localhost admin (according to
the previous email)
or
ejabberdctl register admin localhost admin
Every time i received:
RPC failed on the node [EMAIL PROTECTED] : nodedown ro similar
Take a look at the command line parameters to ejabberdctl. I
wouldn't expect those commands to work.
Can anyone from collabora please specify the single correct way to
configure this, because we will never get it right.
Yes, please.
Also i couldnt connect to http://yourserver:5280/admin/. Perhaps
this is expected since the admin account was not succefully created.
Correct. You were trying http://18.85.46.175:5280/admin/, right ?
I could telnet 18.85.46.175 5222 from an XO, or telnet localhost
5222 and successfully connected.
Note 18.85.46.175 is the servers IP.
I tried to connect to the custom jabber server through an XO by
sugar-control-panel -s jabber 18.85.46.175
sugar reboot
The gabble logs, which i attach, show an initial succefull
connection, which failed later on.
Also in the server side, the following message poped up:
INFO REPORT:
[(0.185.0:ejabberd_listener:90):(#port0.388) Accepted connection
({0,0,0,0,0,65535,46935,5098,56209}) -
({0,0,0,0,65535,46935,11951,5223})]
or similar.
The XO was finally connected to salut. However, no other XO has
managed to connect to jabber.laptop.org successfully the past week.
Is there a reason for this?
That is interesting. The server is up and running, and thinks that
140 of the
7500+ registered users are currently using it. You might try
restarting it ?
wad
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
olpc devel qlikview
The folks at qliktech analyzed the git tree for us: http://demo.qliktech.com/qlikview/ajax/olpc/ enjoy. -walter -- Walter Bender One Laptop per Child http://laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New joyride build 1419
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build1419/ -kernel.i586 0:2.6.22-20071213.5.olpc.fa094abd8cdf4d6 +kernel.i586 0:2.6.22-20071213.6.olpc.38ce150bb456662 -libertas-usb8388-firmware.noarch 2:5.110.20.p47-1.olpc2 +libertas-usb8388-firmware.noarch 2:5.110.20.p47-2.fc7 +olpc-library-common.noarch 0:1-11 -olpc-library-common.noarch 0:1-9 -olpc-library-core.noarch 0:1-10 +olpc-library-core.noarch 0:1-11 +olpc-library-webserver.noarch 0:0.2-1 +python-jinja.noarch 0:1.2-1 -sugar-artwork.i386 0:0.40-0.1.git288e365b29 +sugar-artwork.i386 0:0.40-1 +sugar-datastore.noarch 0:0.5-0.8.gite23a6f66eb -sugar-datastore.noarch 0:0.7.0-1 +sugar.i386 0:0.75.0-0.9.git5e942edddc -sugar.i386 0:0.75.3-1 --- olpc-library-common.noarch 1-11 --- * new packages for content library that include webserver --- olpc-library-core.noarch 1-11 --- * new packages for content library that include webserver --- olpc-library-webserver.noarch 0.2-1 --- * new packages for content library that include webserver --- python-jinja.noarch 1.2-1 --- * new packages for content library that include webserver --- sugar.i386 0.75.0-0.9.git5e942edddc --- - #5106 Attaching a file to gmail msg caused the journal to crash - #4995 genpot option in setup.py modifies PO files -- This email was automatically generated Aggregated logs at http://dev.laptop.org/~bert/joyride-pkgs.html ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New joyride build 1419
On Dec 14, 2007 1:45 AM, Build Announcer Script [EMAIL PROTECTED] wrote: http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build1419/ +sugar-datastore.noarch 0:0.5-0.8.gite23a6f66eb -sugar-datastore.noarch 0:0.7.0-1 +sugar.i386 0:0.75.0-0.9.git5e942edddc -sugar.i386 0:0.75.3-1 Dennis, looks like something went wrong with the ship.2 tagging here. It's fetching older rpms from my public_rpms... Marco ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: connection to jabber.laptop.org
On Dec 13, 2007 5:08 PM, John Watlington [EMAIL PROTECTED] wrote:
On Dec 13, 2007, at 1:05 PM, Giannis Galanis wrote:
I also installed the rpm in custom machine(not a school server) in
1CC.
I must note that the ejabberdctl-extra.diff patch in the wiki page
is for another version than 1.1.4.
I used the config file ejabberd.cgf which I got from
jabber.laptop.org
John, I didnt use the jtest account, but omicron which danny
created for me last week. I got the file from /home/wad
The accounts are not registered in the ejabberd.cfg file. They are
kept in database (which can
be dumped and reloaded using ejabberdctl). Thus, omicron doesn't
have an account on your new machine.
I couldnt register the admin account(is this necessary? because it
is not stated in the wiki)
This is absolutely necessary, and was the sticking point for me last
week on a schoolserver.
I tried:
ejabberdctl register localhost admin admin (according to wiki)
ejabberdctl ejabberd register admin localhost admin (according to
the previous email)
or
ejabberdctl register admin localhost admin
Every time i received:
RPC failed on the node [EMAIL PROTECTED] : nodedown ro similar
Take a look at the command line parameters to ejabberdctl. I
wouldn't expect those commands to work.
The commandline parameters of ejabberdctl are not easy to find. Why do you
think the above commands would not work?
You said you used ejabberdctl ejabberd register admin localhost admin and
managed to register.
I also tried
ejabberdctl delete-older-users
ejabberdctl status
ejabberdctl --node localhost status
I received:
RPC failed on the node {1st [EMAIL PROTECTED] : nodedown
Can anyone from collabora please specify the single correct way to
configure this, because we will never get it right.
Yes, please.
Also i couldnt connect to http://yourserver:5280/admin/. Perhaps
this is expected since the admin account was not succefully created.
Correct. You were trying http://18.85.46.175:5280/admin/, right ?
I could telnet 18.85.46.175 5222 from an XO, or telnet localhost
5222 and successfully connected.
Note 18.85.46.175 is the servers IP.
I tried to connect to the custom jabber server through an XO by
sugar-control-panel -s jabber 18.85.46.175
sugar reboot
The gabble logs, which i attach, show an initial succefull
connection, which failed later on.
Also in the server side, the following message poped up:
INFO REPORT:
[(0.185.0:ejabberd_listener:90):(#port0.388) Accepted connection
({0,0,0,0,0,65535,46935,5098,56209}) -
({0,0,0,0,65535,46935,11951,5223})]
or similar.
The XO was finally connected to salut. However, no other XO has
managed to connect to jabber.laptop.org successfully the past week.
Is there a reason for this?
That is interesting. The server is up and running, and thinks that
140 of the
7500+ registered users are currently using it. You might try
restarting it ?
wad
There are 140 people connected to jabber.laptop.org?
With what command can you see this?
Noone at the office has connected recently.
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
New joyride build 1421
http://xs-dev.laptop.org/~cscott/olpc/streams/joyride/build1421/ -Record-45.xo +Record-46.xo -olpc-utils.i386 0:0.53-1.olpc2 +olpc-utils.i386 0:0.56-1.olpc2 -sugar.i386 0:0.75.0-0.9.git5e942edddc +sugar.i386 0:0.75.3-1 --- Record-46 --- * #5448 fix * #4983 addressed -- This email was automatically generated Aggregated logs at http://dev.laptop.org/~bert/joyride-pkgs.html ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
New ship.2 build 651
http://xs-dev.laptop.org/~cscott/olpc/streams/ship.2/build651/ -libertas-usb8388-firmware.noarch 2:5.110.20.p42-1.olpc2 +libertas-usb8388-firmware.noarch 2:5.110.20.p47-2.fc7 +olpc-utils.i386 0:0.48.1-1.olpc2 -olpc-utils.i386 0:0.48-1.olpc2 -sugar-datastore.noarch 0:0.2.2-0.40.20071114git.ea0764a9e9 +sugar-datastore.noarch 0:0.2.3-1.olpc2 -sugar.i386 0:0.70.3-1 +sugar.i386 0:0.70.4-1 -- This email was automatically generated Aggregated logs at http://dev.laptop.org/~bert/ship.2-pkgs.html ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: olpc devel qlikview
Can anyone tell me how a project owner is determined by git ? On Dec 13, 2007, at 6:54 PM, Walter Bender wrote: The folks at qliktech analyzed the git tree for us: http://demo.qliktech.com/qlikview/ajax/olpc/ enjoy. -walter -- Walter Bender One Laptop per Child http://laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: QActivity
Bernhard Rosenkraenzer wrote: sorry for the delay, net access here is pretty far from reliable (it's pretty common for the entire country's net access to just drop and stay down for a couple of days - nobody but me seems to be bothered by it). Out of curiosity, what country would that be? So in case I need to travel there I'll come prepared with something to read for 2 days :-) We do not support the B2 boxes any more, due to lack of developer time for testing and bugfixing. So the latest builds do not actually even boot on B2s! I know -- but all I have is a B2 (and one of the old ones at that, 128 MB). Making the current joyride images work again would be another interesting open project. It probably takes some kernel work in the Geode GX drivers. Yes, but that isn't done for KDE4 yet, and developing for KDE3 is a dead end -- the kdeedu applications in KDE4 SVN are already much better than their KDE3 counterparts (I have almost all of them running by now btw). You mean running on the XO? As activities? -- \___/ |___| Bernardo Innocenti - http://www.codewiz.org/ \___\ One Laptop Per Child - http://www.laptop.org/ ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
multiple MTD partitions
Hello Mitch, we've sent an UBIFS announcement few days ago to this mailing list: http://lists.laptop.org/pipermail/devel/2007-December/008348.html but unfortunately have not got feedback, and I suspect one of the reasons is that it is too difficult to boot UBIFS on XO. I'd kindly ask you to help me with booting XO with UBIFS as rootfs. UBI/UBIFS is too large and difficult to implement their support in XO boot-loader. So I plan to use the following scheme: 1. Have 2 MTD partitions - mtd0 and mtd1. mtd0 is small (say, 10MiB), and has JFFS2 FS. It contains /boot, /boot-alt, and everything else which the boot-loader would like to have. mtd1 is large, and it spans up to the end of the flash chip. 2. When booting, the bootloader reads kernel, initrd and the other stuff from the JFFS2 FS on MTD 0. It has to be trivial as the boot-loader already can read JFFS2 FS. The boot-loader does not try to read mtd1, because it contains UBI/UBIFS which it does not support. 3. Once the kernel and initrd are loaded, mtd1 can be attached to UBI and rootfs (UBIFS) can be bounted. Also, I need to be able to easily flash images which contain JFFS2 and UBIFS to the internal NAND. But I guess this has nothing to do with the bootloader, right? Thanks. -- Best Regards, Artem Bityutskiy (Артём Битюцкий) ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
[PATCH] Make the OLPC build not depend on mkinitrd
---
SPECS/olpc-2.6.spec |8 +++-
buildd.sh |2 +-
2 files changed, 8 insertions(+), 2 deletions(-)
diff --git a/SPECS/olpc-2.6.spec b/SPECS/olpc-2.6.spec
index c823a54..2ead835 100644
--- a/SPECS/olpc-2.6.spec
+++ b/SPECS/olpc-2.6.spec
@@ -15,6 +15,9 @@ Summary: The Linux kernel (the core of the Linux operating
system)
%define buildkdump 0
%define buildheaders 1
+# Disable debuginfo package because it makes the build fail
+%define _enable_debug_packages 0
+
# Versions of various parts
# After branching, please hardcode these values as the
@@ -213,8 +216,11 @@ Summary: The Linux kernel (the core of the Linux operating
system)
#
# Packages that need to be installed before the kernel is, because the %post
# scripts use them.
+# On the OLPC, we use a fancy initrd that doesn't rely on mkinitrd
+# We drop mkinitrd because it also drags in lvm2 and other nasty dependencies
#
-%define kernel_prereq fileutils, module-init-tools, initscripts = 8.11.1-1,
mkinitrd = 4.2.21-1
+%define kernel_prereq fileutils, module-init-tools, initscripts = 8.11.1-1 \
+ %{?!olpc:, mkinitrd = 4.2.21-1}
Name: kernel
Group: System Environment/Kernel
diff --git a/buildd.sh b/buildd.sh
index 24ba127..6e8de51 100755
--- a/buildd.sh
+++ b/buildd.sh
@@ -7,7 +7,7 @@ GITWEB=http://dev.laptop.org/git?p=olpc-2.6;
if [ x$BRANCH = x ]; then
BRANCH=master
fi
-BUILDDIR=/home/dilinger/public_html/builds-${BRANCH}
+BUILDDIR=$HOME/public_html/builds-${BRANCH}
BASE=$BUILDDIR/`date '+%s'`
SUBLEVEL=$(wget -O- ${GITWEB};a=blob_plain;hb=${BRANCH};f=Makefile
2/dev/null | sed -ne
's/^.*SUBLEVEL[[:space:]]*=[[:space:]]*\([0-9]\+\).*$/\1/p')
--
1.5.3.3
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
