Re: anyone want XOrduino or XO Stick bare boards
paul wrote: > doing some cleanup today, i found that i have 10 XO Stick and 14 > XOrduino bare boards that i'm happy to mail to anyone that can make > use of them -- either all at once, or as few as one to a "customer". i should have been more clear, since someone has already asked -- i'm not charging anything for the boards. these circuit boards are all surplus that was saved from the goodwill industries and the dumpster while we were closing down the OLPC offices in somerville several years ago. i'll accumulate requests (if any) for a week or so, then send them out. paul > > i've used a couple of the XO Stick boards for my own projects, and i'm > setting aside a couple more for future use. i also built up an > XOrduino, to prove it could be done (it wasn't easy -- hand-soldering > SMT parts is harder than it looks), but i'm not sure i ever even > booted it. i'm happy to give that board to someone too. > > i'm not on any of the deployment lists, or the unleashkids -- feel > free to forward this message if you think someone not on devel would > be interested. > > for a reminder of what i'm talking about see: > http://cananian.livejournal.com/66129.html > http://cananian.livejournal.com/66654.html > http://cananian.livejournal.com/66895.html > > i have notes i made while assembling the XOrduino which i can share. > not sure i have anything similar for the XO Stick -- i recall it was > a piece of cake by comparison. > > paul > =- > paul fox, p...@laptop.org > > _______ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
anyone want XOrduino or XO Stick bare boards
doing some cleanup today, i found that i have 10 XO Stick and 14 XOrduino bare boards that i'm happy to mail to anyone that can make use of them -- either all at once, or as few as one to a "customer". i've used a couple of the XO Stick boards for my own projects, and i'm setting aside a couple more for future use. i also built up an XOrduino, to prove it could be done (it wasn't easy -- hand-soldering SMT parts is harder than it looks), but i'm not sure i ever even booted it. i'm happy to give that board to someone too. i'm not on any of the deployment lists, or the unleashkids -- feel free to forward this message if you think someone not on devel would be interested. for a reminder of what i'm talking about see: http://cananian.livejournal.com/66129.html http://cananian.livejournal.com/66654.html http://cananian.livejournal.com/66895.html i have notes i made while assembling the XOrduino which i can share. not sure i have anything similar for the XO Stick -- i recall it was a piece of cake by comparison. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: low battery shutdown
martin wrote: > On Mon, Feb 22, 2016 at 9:12 AM, wrote: > > > When my XO 1.5 shows about 33% charge, the system shuts > > down with no warning. This is normal behaviour? > > > Not normal behaviour. It is consistent with a battery that has reached the > end of its usable/reliable life _or_ a battery that has unbalanced cells. that sounds right. it might (or might not be) interesting to look at the power logs kept in /home/olpc/power_logs (i think that's the name). there might be an indication there as to why the system is shutting down early. the system will shut down based on the result of the function "low_battery" in /sbin/powerd (powerd is a script). that function checks whether the capacity is reported as less than 1%, or the voltage as less than 5.7V. if you can't swap or rebalance your battery, you might be able to play with the contents of that function to get a clean shutdown earlier. paul > > Note that this happens on almost every battery-powered device, not only > XOs, when batteries get old or their cells unbalanced. > > IIRC wiki has instructions on how to try to rebalance batteries. > > > > > m > -- > martin.langh...@gmail.com > - ask interesting questions > - don't get distracted with shiny stuff - working code first > ~ http://docs.moodle.org/en/User:Martin_Langhoff > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: game controller
peter wrote: > Greetings to all for the New Year, > > Paul Fox, pgf at laptop.org, Sat Dec 5 11:02:48 EST 2015, > > the "game controller" is simply 4 separate electrical contacts ... > > ... use 'xev' to check ... > > A "Hardware" section now in http://wiki.laptop.org/go/Game_controller . > Corrections, criticisms and suggestions welcome. the only mistake i see in your new section is that there are 4 buttons, not 5. > > Can anyone tell where the nomenclature "KP_Up" and etc. originated? > A mainframe console in the 1960s? i suspect the names came about when the PC/AT keyboard was introduced by IBM. i think that was the first PC keyboard to have a separate numeric keypad. (but that's just an informed guess.) paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Game controller
that being said, it's possible to write code to handle combinations of those keypresses (e.g., "all mashed down at once") separately from the individual strokes. you either need to intercept the keys at a pretty low level (scan codes) and keep track of the up and down state of every key, or you can read the keys normally and use a user-level timer to decide whether more than one has been pressed in very quick succession. paul i wrote: > the "game controller" is simply 4 separate electrical contacts with a > button large enough to push them individually or together (in some > combinations). the resulting presses are reported as keyboard > keystrokes. if i remember correctly, these buttons are bound to the > "keypad" versions of the arrow keys, i.e. KP_UP, KP_RIGHT, etc. use > 'xev' to check me on this. > > paul > > peter wrote: > > Hi, > > > > I'm interested in use of the game controller or controllers in > > place of the TouchPad or mouse. This is relevant to eBook mode > > where the TouchPad is not accessible and a mouse is not convenient. > > > > This is what I have. > > [olpc@xo-53-1d-bb ~]$ cat /boot/olpc_build > > 13.2.5 for XO-1.5 (build 17) > > > > bash-4.2# evtest > > No device specified, trying to scan all of /dev/input/event* > > Available devices: > > /dev/input/event0:Lid Switch > > /dev/input/event1:Power Button > > /dev/input/event2:AT Translated Set 2 keyboard > > /dev/input/event3:EBook Switch > > /dev/input/event4:olpc-kbdshim virtual keyboard > > /dev/input/event5:SynRelPS/2 Synaptics TouchPad > > /dev/input/event6:olpc-kbdshim virtual mouse > > /dev/input/event7:USB Optical Mouse > > Select the device event number [0-7]: > > > > No mention of the Game controller. Is any joystick device present? > > > > [olpc@xo-53-1d-bb ~]$ ls -l /dev/j* > > ls: cannot access /dev/j*: No such file or directory > > > > Can any Linux software detect or communicate with this game > > controller? Ideas? > > > > > > ___ > > Devel mailing list > > Devel@lists.laptop.org > > http://lists.laptop.org/listinfo/devel > > =- > paul fox, p...@laptop.org > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Game controller
the "game controller" is simply 4 separate electrical contacts with a button large enough to push them individually or together (in some combinations). the resulting presses are reported as keyboard keystrokes. if i remember correctly, these buttons are bound to the "keypad" versions of the arrow keys, i.e. KP_UP, KP_RIGHT, etc. use 'xev' to check me on this. paul peter wrote: > Hi, > > I'm interested in use of the game controller or controllers in > place of the TouchPad or mouse. This is relevant to eBook mode > where the TouchPad is not accessible and a mouse is not convenient. > > This is what I have. > [olpc@xo-53-1d-bb ~]$ cat /boot/olpc_build > 13.2.5 for XO-1.5 (build 17) > > bash-4.2# evtest > No device specified, trying to scan all of /dev/input/event* > Available devices: > /dev/input/event0: Lid Switch > /dev/input/event1: Power Button > /dev/input/event2: AT Translated Set 2 keyboard > /dev/input/event3: EBook Switch > /dev/input/event4: olpc-kbdshim virtual keyboard > /dev/input/event5: SynRelPS/2 Synaptics TouchPad > /dev/input/event6: olpc-kbdshim virtual mouse > /dev/input/event7: USB Optical Mouse > Select the device event number [0-7]: > > No mention of the Game controller. Is any joystick device present? > > [olpc@xo-53-1d-bb ~]$ ls -l /dev/j* > ls: cannot access /dev/j*: No such file or directory > > Can any Linux software detect or communicate with this game > controller? Ideas? > > > _______ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: download.laptop.org
tony wrote: > It appears that 13.2.5 is no longer accessible as download.laptop.org is > not responding. download.l.o is being worked on (disk troubles). without checking with those actually doing the work, i'd guess another week or two of downtime. paul =----- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Compatibility of serial adapters
peter wrote: > Seems that an adapter such as http://www.ebay.ca/itm/381346598663 , > similar to the first generation adapter, might work. The concluding > sentence in > http://wiki.laptop.org/go/Serial_adapters#First_generation_serial_adapter > is "This only works on the XO-1." What prevents it from working on an > XO-1.5? Can anyone elaborate on this compatibility topic? i believe it's because the later adapters are USB adapters, and are powered from the USB side. the old XO-1 adapter gets power from the laptop -- that power isn't available from later models. (read the descriptions of "Pin 1" in the Electrical Details section of the page you linked to. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] [Sugar-devel] how to remove WiFi credential/history from Sugar?
adam wrote: > >> > > > >> > >/etc/NetworkManager/system-connections/ that's is where the config lives on the machine i'm looking at (running 13.2.0). try: cd /etc sudo grep -R . cd /home/olpc sudo grep -R . on older releases, sugar kept the network config separate, under /home/olpc/.sugar, i think. it took a while before gnome and sugar wifi configs were synced. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: how to remove WiFi credential/history from Sugar?
adam wrote: > "rm /etc/sysconfig/network-scripts/key_" does not fully delete a WiFi > credential, even after reboot of the XO-1.5 with Sugar 0.106.0, the > password is clearly still buried+working in the system somewhere. under sugar, i think it's in the control panel, under Network. paul > > Anywhere else obvious to look? Or wipe out all WiFi credentials + > history? I've also looked in the following 2 diretories which are both > empty: > >/etc/NetworkManager/system-connections/ >/bootpart/security/state/ > > It's called the N.ice S.ugar A.gency after all taking my password who knows > where...Thanks for ideas =) > > -- > Unsung Heroes of OLPC, interviewed live @ http://unleashkids.org ! > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Fwd: android on XO-4 questions
thanks ben! youxin wrote: > > > > - is it possible to get root? there's a terminal emulator > > pre-installed, and it's possible to browse the filesystem > > and do a few things, but being root would give access to > > more. (logs, for instance) > > > There is no official "root" process in Android user build. But there > are bunch of root tools you may can try on Android 4.3, I never tried > them and not sure which secure hole they use, but they may haven't > been fixed by XO-4 Android. > http://forum.xda-developers.com/showthread.php?t=2565758 > > Alternatively, > * Serial port has root access. good. i'll try that first -- sounds easiest. :-) > * Rebuild Android in engineer mode gives you root access out of box. > http://wiki.laptop.org/go/Android/Building/Variants > * XO-4 special secure hole, boot to sugar, unpack the Android ramdisk > in boot partition, change secure configuration, repack ramdisk and > replace it. > > > > > > > > - are the USB ports fully supported? i can't seen to get any > > app that exists to allow access to a USB GPS dongle to work, > > for instance. > > > Not tested, only USB mess storage is tested. I don't think USB GPS > dongle will work any way since there should be a GPS hardware abstract > layer for Android needs to be implemented. the GPS dongles are all just serial devices, and an app opens the serial port and reintroduces "mock" GPS events into the system. "You Are Here GPS" seems to be one such app: https://play.google.com/store/apps/details?id=com.agbooth.usbgps&hl=en but the Play store won't let me install it -- claims "This item is not compatible with your device". > > > > > > > - has anyone gotten bluetooth audio to work? i know there's > > a limitation in the XO-4 hardware regarding audio -- i > > think stereo headsets won't work -- but can any audio work? > > (here's a case where looking at logs and dmesg output might > > be helpful) > > > Assume you are talk about A2DP? It's not ported on XO-4, but HSP > should work fine. okay. i've rechecked the docs for my headset, and it only mentions A2DP and HFP. so i guess i'm stuck with a wired connection. (the headset allows for a wired input as well as using BT.) > > > > - i could probably get audio to work via an external (USB) > > bluetooth dongle, but a) USB devices would need to be > > recognized, and b), i think i'd need to disable the internal > > bluetooth. > > > I have no idea of this. > > > > > > > finally, a different sort of question: > > - i have exactly one app (an important one, unfortunately) in > > which the mapping of ctrl-ESC to emulate the android hardware > > "Menu" button doesn't work. does anyone know where that > > keyboard mapping is implemented? i'd happily replace the > > app-switcher function on the rotate button, and make it > > a true Menu key, instead. > > > > Keyboard mapping is here: > http://dev.laptop.org/git/users/ben/android_vendor_olpc_xo4/tree/keyboard/olpc_keyboard.kl?h=android-4.3.1-xo4 > > It located in system/usr/keylayout, you may need remount system > partition as rw to change it or change it when booted to sugar. great -- i'll take a look. thanks again, paul > > Regards, > Ben =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
android on XO-4 questions
i've been playing with android on XO-4 lately. i had tried an early release, it was buggy, and i didn't have much use for it anyway, so i'd not tried the latest. it actually works pretty well. but i have some questions. i don't know if anyone with answers or experience is reading here, but i may as well start somewhere. - is it possible to get root? there's a terminal emulator pre-installed, and it's possible to browse the filesystem and do a few things, but being root would give access to more. (logs, for instance) - are the USB ports fully supported? i can't seen to get any app that exists to allow access to a USB GPS dongle to work, for instance. - has anyone gotten bluetooth audio to work? i know there's a limitation in the XO-4 hardware regarding audio -- i think stereo headsets won't work -- but can any audio work? (here's a case where looking at logs and dmesg output might be helpful) - i could probably get audio to work via an external (USB) bluetooth dongle, but a) USB devices would need to be recognized, and b), i think i'd need to disable the internal bluetooth. finally, a different sort of question: - i have exactly one app (an important one, unfortunately) in which the mapping of ctrl-ESC to emulate the android hardware "Menu" button doesn't work. does anyone know where that keyboard mapping is implemented? i'd happily replace the app-switcher function on the rotate button, and make it a true Menu key, instead. =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: selinux
tim wrote: > I need to determine the state of selinux on an xo4 running 32014o4.zd. I nonexistent. it's not in the kernel. > notice that /etc/selinux/config does not exist. Can someone tell me what is > the best way to determine whether selinux is disabled and if not if it is > permissive? you can "gunzip -c /proc/config.gz | grep SECURITY" to see that no security options are enabled. i'm not sure what "and if not if it is permissive" means. paul =-- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Devel Digest, Vol 106, Issue 2
please post messages with descriptive subject lines. lucia wrote: > Hi: > > I subscribe to Mike's question. > "Don't hate me people, but I am also interested in finding a copy of Windows > > XP for XO-1 to try and learn about how it works and loads on the XO. > > Thanks," windows for the XO-1 was never publicly available, and was never deployed beyond initial trials by the customer who wanted it. > > Furthermore, (sorry for the pro's here): I understand that Sugar GUI sits > on top of Linux OS, but if somebody wants to develop something in a Windows > 8.1 environment (I'm not a converted to Microsoft or any other OS), does > he/she have to go back to the command line? i don't really understand the question, but if you want to know how to do sugar development on non-OLPC platforms, you should ask on the sugar mailing list: http://lists.sugarlabs.org/listinfo/sugar-devel paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
tkk...@nurturingasia.com wrote: > Tried this first thing in the morning. Disabling kdbshim and the > MakeyMakey activity does the trick on my XO 1.75! thanks. would you be in a position to test a fix for this, if i sent you a new olpc-kbdshim binary to try? i prepared a patch some time ago for kbdshim, which causes it to (mostly) ignore external devices. but since i don't have makeymakey hardware, it never really got tested. i think the same patch may solve your problem. but first, please try this: - disable kbdshim, as you have done previously. - run "sudo evtest". this will show you a list of system input devices. - one of those devices should be your logitech device. select it by number. - it will dump a list of supported events and properties, then it will loop, reporting individual events as they arrive from that device. i'm only interested in the initial list of events and properties, so you can use ^C to kill evtest as soon as you'd like. - send me the resulting output. paul > > Thanks for the advice from all! There is so much to learn :-) > > Have a great weekend! > > > >-Original Message- > >From: Paul Fox [mailto:p...@laptop.org] > >Sent: Saturday, September 20, 2014 12:52 AM > >To: tkk...@nurturingasia.com > >Cc: devel@lists.laptop.org > >Subject: Re: Logitech USB wireless keyboard with trackpad on XO-1.75 > > > >have you tried disabling kbdshim, as suggested by james? use either: > >sudo systemctl stop olpc-kbdshim.service > >or the MakeyMakey activity to do this. kbdshim can interfere with > >the operation of some integrated multi-device hardware. > > > >paul > > > >tkk...@nurturingasia.com wrote: > > > Managed to get via yum install usbutils > > > > > > "sudo lsusb -v" command gives a long list: > > > > > > For the Logitec k400r (wireless keyboard with trackpad) I get this > > > output: > > > > > > Bus 001 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver > > > Device Descriptor: > > > bLength 18 > > > bDescriptorType 1 > > > bcdUSB 2.00 > > > bDeviceClass 0 (Defined at Interface level) > > > bDeviceSubClass 0 > > > bDeviceProtocol 0 > > > bMaxPacketSize0 8 > > > idVendor 0x046d Logitech, Inc. > > > idProduct 0xc52b Unifying Receiver > > > bcdDevice 12.01 > > > iManufacturer 1 Logitech > > > iProduct 2 USB Receiver > > > iSerial 0 > > > bNumConfigurations 1 > > > Configuration Descriptor: > > > bLength 9 > > > bDescriptorType 2 > > > wTotalLength 84 > > > bNumInterfaces 3 > > > bConfigurationValue 1 > > > iConfiguration 4 RQR12.01_B0019 > > > bmAttributes 0xa0 > > > (Bus Powered) > > > Remote Wakeup > > > MaxPower 98mA > > > Interface Descriptor: > > > bLength 9 > > > bDescriptorType 4 > > > bInterfaceNumber 0 > > > bAlternateSetting 0 > > > bNumEndpoints 1 > > > bInterfaceClass 3 Human Interface Device > > > bInterfaceSubClass 1 Boot Interface Subclass > > > bInterfaceProtocol 1 Keyboard > > > iInterface 0 > > > HID Device Descriptor: > > > bLength 9 > > > bDescriptorType 33 > > > bcdHID 1.11 > > > bCountryCode 0 Not supported > > > bNumDescriptors 1 > > > bDescriptorType 34 Report > > > wDescriptorLength 59 > > > Report Descriptors: > > > ** UNAVAILABLE ** > > > Endpoint Descriptor: > > > bLength 7 > > > bDescriptorType 5 > > > bEndpointAddress 0x81 EP 1 IN > > > bmAttributes 3 > > > Transfer Type Interrupt > > > Synch Type None > > > Usage Type Data > > > wMaxPacketSize 0x0008 1x 8 bytes > > > bInterval 8 > > > Interface Descriptor: > > > bLength 9 > > > bDescriptorType 4 > > > bInterfaceNumber 1 > > > bAlternateSetting 0 > > > bNumEndpoints 1 > > > bInterfaceClass 3 Human Interface Device > > > bInterfaceSubClass 1 Boot Interface Subclass > > > bInterfaceProtocol 2 Mouse > > > iInterface 0 > > > HID Device Descriptor: > > > bLength 9 > > > bDescriptorType 33 > > > bcdHID 1.11 > > > bCountryCode 0 Not supported > > > bNumDescriptors 1 > > > bDescriptorType 34 Report > > > wDesc
Re: Logitech USB wireless keyboard with trackpad on XO-1.75
>There are too many ways in which a device may present the USB HID > >(human interface device) features to the host computer; if you can > >provide the "sudo lsusb -v" command output then I can check that. > > > >You may need to "sudo yum install -y lsusb" to get the lsusb program > >installed. > > > >Moving on to speculation: > > > >Some devices are not intentionally supported by OLPC OS, for reasons > >of space. It is possible to add support. > > > >Some devices are not sadly not supported by Linux. This particular > >device is unlikely to be affected, since other references to it show > >support on other Linux distributions [1]. > > > >Our ticket #12616 [2] seems likely to be the cause of your problem. > >Please check to see if any of the workarounds in that ticket fix it > >for you. In particular, try stopping olpc-kbdshim process, > > > >sudo systemctl stop olpc-kbdshim.service > > > >But this also disables keyboard and touchpad idle detection, rotate > >key, touchpad and arrow keys screen rotation support, grab scrolling > >key, volume keys, and brightness keys. > > > >You might also try the MakeyMakey activity on Sugar Labs [3], which > >uses the same workaround. > > > >+CC Paul Fox, for interest as olpc-kbdshim author. > > > >References: > > > >[1] http://elinux.org/RPi_USB_Keyboards > > > >[2] http://dev.laptop.org/ticket/12616 > > > >[3] http://wiki.sugarlabs.org/go/Activities/MakeyMakey > > > >-- > >James Cameron > >http://quozl.linux.org.au/ > > > > > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Announcing OLPC OS 13.2.1
james wrote: > G'day, > > We're pleased to announce the release of OLPC OS 13.2.1 for XO-1, > XO-1.5, XO-1.75 and XO-4. > > Compared to previous releases, this release has very little change; it perhaps "very little" compared to some past releases. but when combined with "developer's per release", i think you've accomplished quite a lot!!! :-) congratulations! paul > adds hardware support for a new camera sensor, and wireless > performance fixes. > > Details of new features, known issues, and how to download, install or > upgrade can be found in the release notes: > > http://wiki.laptop.org/go/Release_notes/13.2.1 > > XO-4 users should note that the forced power down button press has > been extended from two to five seconds. > > Many thanks to all contributors, testers, upstreams, and those who > have provided feedback of any kind. > > -- > James Cameron > http://quozl.linux.org.au/ > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Announcing the development of OLPC OS 13.2.1
not speaking for james or olpc, i think this sounds like a request for a volunteer project, and not something that should be directed at james. paul tony wrote: > Hi, James > > It would also be very helpful to have a release 12.2.0 for the XO-1. > This release would incorporate > the libertas patch and correct the firmware version. Perhaps the > ds-backup.sh and ds-backup.py could > be replaced with versions that correct the reported problems. If > politically acceptable, this could also be shown on the release page as > the recommended alternative for use with the XO-1. > > Tony > > On 06/12/2014 06:00 PM, devel-requ...@lists.laptop.org wrote: > > Message: 1 > > Date: Thu, 12 Jun 2014 15:26:00 +1000 > > From: James Cameron > > To:devel@lists.laptop.org > > Subject: Announcing the development of OLPC OS 13.2.1 > > Message-ID:<20140612052600.gf13...@us.netrek.org> > > Content-Type: text/plain; charset=us-ascii > > > > Announcing our next release cycle: > > > > http://wiki.laptop.org/go/13.2.1 > > > > Goal is to add hardware support for the new SIV121C camera sensor, and > > include wireless performance fixes published since 13.2.0. > > > > Scope is restricted to Open Firmware, and kernel. > > > > -- James Cameron http://quozl.linux.org.au/ > > _______ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: New camera sensor SIV121C
> On Wed, Jun 4, 2014 at 9:38 PM, James Cameron wrote: > > We have begun qualification of a new camera sensor SIV121C for > > production of the XO-1.75 and XO-4 laptops. > ... > > > The new sensor does a little bit better at low light levels, as a > > result of a different analog to digital conversion method. i noticed on trac that you're supporting the new sensor on 1.5. for replacement purposes? paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] XO on Fedora 20 (was Re: [GSoC] Porting To Python3)
daniel wrote: > * Should we contribute the olpc-os-builder changes back to OLPC or fork it? > > I don't know if OLPC will do any active development on the linux side of > > things, if not maybe better to turn this into a sugarlabs thing. ... > Yes. I don't really have a strong feeling one way or another. I can send > patches for the generic parts if they are wanted. > > I think we also need a place where to put reference configurations. I > initially had put them in olpc-os-builder, numbered as 14.0.0 but that > feels wrong... since no official olpc releases are planned. I suppose I > could edit the examples/f18-[model].ini ones instead, but I would need > access to whatever repository we use to change those without needing review > every time. in my opinion, the value of not forking would outweigh the risk of giving commit privs to someone from (gasp!) sugarlabs. ;-) (that really is just an opinion, of course. it's not my call.) it also seems like this problem could be well solved with branches and tags. i haven't looked at the o-o-b tree, but i assume the current 13.2.0 point could be frozen (branch or tag) and other work could continue, and eventually branched or tagged itself. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Announcing another early Android build for XO-4
james wrote: > Would be nice, yes, but not immediately planned. do we have any idea why it doesn't work? > Meanwhile, if you would like to test and still retain an existing > install, learn how to backup and restore the internal storage: > > http://wiki.laptop.org/go/Backup#XO-1.5.2C_XO-1.75_and_XO-4 > http://wiki.laptop.org/go/Firmware/Storage#How_to_make_an_image_copy_of_internal_storage neither is very helpful in lowering the bar for someone that would like to test without (even temporarily) destroying the content of their laptop. paul =----- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: gnome applet can't initialize Clutter
scott wrote: > Paul, > The Gnome Control Panel is not present in the build. Am I missing > something or is it left out also? > > How do you edit the menu system in Gnome without it, etc? i think you need to think about this differently: this isn't a gnome laptop. this is a sugar laptop, with the ability to do some gnome stuff if you need to. we didn't used to include gnome at all -- gnome was added because at some point the laptops got faster and had enough storage, and because one of our deployments wanted to be able to run some applications that weren't sugar-compatible. but when things got difficult (e.g., gnome3), we had to choose between getting a release out the door or not. paul > > > > > On Sat, May 10, 2014 at 12:20 PM, Paul Fox wrote: > > > scott wrote: > > > I'm new to the XO-4. So it appears that nobody is running a GUI besides > > > Sugar on these? > > > > > > We don't have opengl support in the X drivers because of the video type > > on > > > these? > > > > > > I wonder why OLPC published a build with Gnome if it is this broken? > > > > i think it's fine if you don't try to install new gnome things. i.e., > > what we shipped is self-consistent. > > > > we were aware of the bluetooth issues -- bluetooth wasn't needed by > > any of our deployments, so it was a low priority. i think we tested with > > the bluez stack. > > > > paul > > > > > > > > > > > > > > On Sat, May 10, 2014 at 11:53 AM, Peter Robinson > >wrote: > > > > > > > I don't remember the details of the 13.2.0 build, I seem to remember > > > > that it was the last release to include fall back mode. The gnome3 > > > > fallback mode had issues in that anything that was linked against > > > > clutter fails because of the lack of opengl support in all of the X > > > > drivers. > > > > > > > > Peter > > > > > > > > On Sat, May 10, 2014 at 7:50 PM, Scott Chapman > > wrote: > > > > > That appears to be the version included with the 13.2.0 build? > > > > > > > > > > What build should I downgrade to that will run Gnome correctly? Or > > is > > > > there > > > > > an easy way to get a non-sugar GUI working on one of these? > > > > > > > > > > > > > > > On Sat, May 10, 2014 at 11:48 AM, Peter Robinson < > > pbrobin...@gmail.com> > > > > > wrote: > > > > >> > > > > >> most of the gnome3 stack won't currently run on any of the XOs > > > > >> > > > > >> Peter > > > > >> > > > > >> On Sat, May 10, 2014 at 7:42 PM, Scott Chapman > > > > wrote: > > > > >> > This affects other gnome commands such as gnome-control-panel as > > well. > > > > >> > > > > > >> > > > > > >> > On Sat, May 10, 2014 at 12:40 AM, Scott Chapman < > > sc...@mischko.com> > > > > >> > wrote: > > > > >> >> > > > > >> >> Hi! > > > > >> >> > > > > >> >> I just got an XO-4 and working to get some things working - > > bluetooth > > > > >> >> in > > > > >> >> this case. > > > > >> >> > > > > >> >> I installed the latest OLPC distro to the internal storage as > > follows > > > > >> >> from > > > > >> >> the ok prompt: > > > > >> >> fs-update u:\32013o4.zd > > > > >> >> > > > > >> >> booted to sugar - switched to Gnome > > > > >> >> > > > > >> >> Bluetooth applet won't show a screen when you right-click on > > the icon > > > > >> >> in > > > > >> >> upper right and select "Bluetooth Settings". > > > > >> >> > > > > >> >> So, I killed the existing bluetooth-applet and ran another one > > from > > > > the > > > > >> >> command line in a terminal: > > > > >> >> > > > > >> >> [olpc@xo-d2-7f-9f ~]$ bluetooth-applet > > > > >> >> > > > > >> >> # Here I selected "Bluetooth Settings" in the new icon and got > > this: > > > > >> >> > > > > >> >> (gnome-control-center:1100): GModule-CRITICAL **: > > g_module_close: > > > > >> >> assertion `module->ref_count > 0' failed > > > > >> >> > > > > >> >> (gnome-control-center:1100): Clutter-CRITICAL **: Unable to > > > > initialize > > > > >> >> Clutter: Failed to connected to any renderer due to constraints > > > > >> >> > > > > >> >> How do I get this working? > > > > >> >> > > > > >> >> Thanks, > > > > >> >> Scott > > > > >> > > > > > >> > > > > > >> > > > > > >> > ___ > > > > >> > 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 > > > > =- > > paul fox, p...@laptop.org > > =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: gnome applet can't initialize Clutter
scott wrote: > I'm new to the XO-4. So it appears that nobody is running a GUI besides > Sugar on these? > > We don't have opengl support in the X drivers because of the video type on > these? > > I wonder why OLPC published a build with Gnome if it is this broken? i think it's fine if you don't try to install new gnome things. i.e., what we shipped is self-consistent. we were aware of the bluetooth issues -- bluetooth wasn't needed by any of our deployments, so it was a low priority. i think we tested with the bluez stack. paul > > > > On Sat, May 10, 2014 at 11:53 AM, Peter Robinson wrote: > > > I don't remember the details of the 13.2.0 build, I seem to remember > > that it was the last release to include fall back mode. The gnome3 > > fallback mode had issues in that anything that was linked against > > clutter fails because of the lack of opengl support in all of the X > > drivers. > > > > Peter > > > > On Sat, May 10, 2014 at 7:50 PM, Scott Chapman wrote: > > > That appears to be the version included with the 13.2.0 build? > > > > > > What build should I downgrade to that will run Gnome correctly? Or is > > there > > > an easy way to get a non-sugar GUI working on one of these? > > > > > > > > > On Sat, May 10, 2014 at 11:48 AM, Peter Robinson > > > wrote: > > >> > > >> most of the gnome3 stack won't currently run on any of the XOs > > >> > > >> Peter > > >> > > >> On Sat, May 10, 2014 at 7:42 PM, Scott Chapman > > wrote: > > >> > This affects other gnome commands such as gnome-control-panel as well. > > >> > > > >> > > > >> > On Sat, May 10, 2014 at 12:40 AM, Scott Chapman > > >> > wrote: > > >> >> > > >> >> Hi! > > >> >> > > >> >> I just got an XO-4 and working to get some things working - bluetooth > > >> >> in > > >> >> this case. > > >> >> > > >> >> I installed the latest OLPC distro to the internal storage as follows > > >> >> from > > >> >> the ok prompt: > > >> >> fs-update u:\32013o4.zd > > >> >> > > >> >> booted to sugar - switched to Gnome > > >> >> > > >> >> Bluetooth applet won't show a screen when you right-click on the icon > > >> >> in > > >> >> upper right and select "Bluetooth Settings". > > >> >> > > >> >> So, I killed the existing bluetooth-applet and ran another one from > > the > > >> >> command line in a terminal: > > >> >> > > >> >> [olpc@xo-d2-7f-9f ~]$ bluetooth-applet > > >> >> > > >> >> # Here I selected "Bluetooth Settings" in the new icon and got this: > > >> >> > > >> >> (gnome-control-center:1100): GModule-CRITICAL **: g_module_close: > > >> >> assertion `module->ref_count > 0' failed > > >> >> > > >> >> (gnome-control-center:1100): Clutter-CRITICAL **: Unable to > > initialize > > >> >> Clutter: Failed to connected to any renderer due to constraints > > >> >> > > >> >> How do I get this working? > > >> >> > > >> >> Thanks, > > >> >> Scott > > >> > > > >> > > > >> > > > >> > ___ > > >> > 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 =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Announcing another early Android build for XO-4
is it possible (read: "has anyone tried") to install just the android half of these releases on an SD card? then dual booting would just involve inserting or removing the SD card, and trying new builds would be a lot less disruptive on the linux install. (i realize this isn't the target configuration, but it might get some additional testing coverage.) paul james wrote: > An Android 4.3.1 (Jelly Bean) build for the XO-4 laptop. > > OLPC is preparing an Android, Sugar and Gnome dual-boot system for the > XO-4. > > Our next development build is available, with the following changes: > > - increased camera usage stability, > > - respond to brightness keys on keyboard, > > - several more apps bundled, > > - support for OLPC English and Spanish keyboard layouts. > > http://wiki.laptop.org/go/Android > http://build.laptop.org/android/2014-05-05/ > > Note: the .zd file has the same name as previous releases. > =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: EC, CForth exploratory commands?
martin wrote: > part text/plain1286 > Hi folks! > > Yesterday I ran a workshop covering some topics about hw development > and mfg. Using a lot of material from Bunnie's blog, as well as from > my time in the trenches. > > As part of it I tried -- and mostly failed -- to give folks a tour of > early boot, using some old boards I have stashed. Here I got truly > lost. I could not find current useful notes on what you can do in the > early CForth env. I could also not find the commands for the EC port > in the wiki, though I do remember issuing commands on that port during > some testing... i think the only reference to those commands may be in the source: http://dev.laptop.org/git/users/rsmith/ec-cl4-mmp3/tree/monitor.c#n172 paul > > I'm more familiar with the full OFW/Forth env so I kind of rescued my > pride there. The attendees got hooked so they're trying to drag me > into a second session in the coming weeks. It would be nice to revisit > EC port and early CForth with commands that actually work :-} > > For simplicity sake, let's assume that I'm on XO-4 B1 or later. That's > what I have the most of, and what I suspect is the most interesting > anyway. > > thanks in advance... > > > m > -- > martin.langh...@gmail.com > - ask interesting questions > - don't get distracted with shiny stuff - working code first > ~ http://docs.moodle.org/en/User:Martin_Langhoff > _______ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Multi-touch [ Devel Digest, Vol 98, Issue 6]
fors...@ozonline.com.au wrote: > part text/plain1115 > Me: SHC23800033 > Q7B37 > I can't run or easily install most apps because of the unsupported > wifi module have you tried a USB ethernet adapter? (hoping you have one to try.) i haven't tried one on XO-4 android, but have used one successfully on another android device. paul =--------- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Announcing another early Android build for XO-4
james wrote: > Interesting, thanks. All my tests were with one finger, and I wasn't > aware of any multitouch apps. > > No, not tracking bugs, Ben is the main developer, and he is subscribed > here. Have used the Wiki page to some extent. pinch to zoom in google maps is the easiest test i know of. in addition, if it's available on the XO-4, there's a developer-support feature that will highlight all the touches on the screen with little rings, tracking each finger as it moves. don't recall what it's called in the developer menu, but it was pretty obvious at the time. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Announcing another early Android build for XO-4
john wrote: > > > On Mar 19, 2014, at 5:12 PM, ben wrote: > > > On 03/20/2014 07:01 AM, Esteban Bordón wrote: > >> Hi! > >> > >> Someone knows how take a screenshot in android? Is there any keys > >> combination for do it in the XO? > >> > > Android brings in a hot key combination for screenshot which is press the > > hard volume down and power > > buttons at the same time, hold them for a second. But unfortunately it > > does work on current XO-4 build. > > Need more investigation why. > > Probably something to do with our power button going through the EC, > and not being directly sensed by the MMP3 SoC. > Power button events thus come in over the EC/Host communications --- > I'm not sure these are button down/button up events. the power button does produce real down/up events, but until today, when we released new EC firmware, both down and up came right together, independent of how long the button was held. plus, the power button appears on a different input device than the rest of the keyboard, which shouldn't confuse things, but might. the new EC code produces real PRESSED and RELEASED events which the kernel now translates to to real key down/up input events. ben needed this for the android power dialog, which relies on timing the button press duration in order to pop up the menu. it's vaguely possible that this change also fixes the screenshot combo. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Announcing another early Android build for XO-4
james wrote: > On Wed, Mar 19, 2014 at 10:21:21AM -0400, Paul Fox wrote: > > the imagename (32013a4.zd) hasn't changed from the 2/26 release. > > the md5 sums are different, so i guess this is probably just a naming > > issue. > > yes, i've not changed the image file name, and at this stage i don't > plan to for the next release either. oh, okay. sorry for the noise. the 2/26 release was the first i'd installed. i just assumed the filename would change for the next one. but of course the versioning issues are very different with two OSes, one of which may be versionless, for all intents and purposes. :-) paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Announcing another early Android build for XO-4
james wrote: > > OLPC is preparing an Android, Sugar and Gnome dual-boot system for the > XO-4. > > Our next development release of a dual boot build is available, with > the following changes: > > - a boot menu, if the rocker down key is held during power up, > > - the touchpad works, > > - power management works, > > - the automatic partition resize no longer requires a first boot into > Linux, > > - switched to user build from engineer build, > > - the power button menu will work once new firmware is released, which > should be tomorrow. > > The build is based on our arm-3.5 kernel, with changes which will be > found in the arm-3.5-android branch of our olpc-kernel repository. > > http://wiki.laptop.org/go/Android > http://build.laptop.org/android/2014-03-19/ the imagename (32013a4.zd) hasn't changed from the 2/26 release. the md5 sums are different, so i guess this is probably just a naming issue. paul > > -- > James Cameron > http://quozl.linux.org.au/ > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.12 (GNU/Linux) > > iD8DBQFTKSOjbmRwv64kZsARAlx+AJ9jdK+ZgV73jla7xveISitCgK7d2QCg24pT > av4U/r7qJhK8DlKzvkMNdBo= > =XaCD > -END PGP SIGNATURE- > part 2 text/plain 129 > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] Boot Menu for XO
[ forgot to cc devel@ ] tkk...@nurturingasia.com wrote: > With XO getting scare 1:1 is not possible and hence I need to use SD card to > boot. Is there a way I could get the XO 1.75 to select booting media: 1. the > internal SSD or 2: inserted bootable SD card. > > Cheers > XO4All this page might help: http://wiki.laptop.org/go/Custom_bootloader =----- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-1.75 early boot codes
daniel wrote: > Hi, > > When booting the XO-1.75 with the check key pressed, 2-digit boot > codes fill the screen briefly before OFW boots the system. > > Can anyone remind me where these numbers are defined in the code? I > know it's in cforth git somewhere... i think you're only partly right about the cforth part. it looks like they come from "puthex" in fbnums.fth, which appears in both cforth and ofw. two callers are from cforth (from ofw.fth), and the rest are from OFW, mostly in resetvec.fth paul > > Thanks > Daniel > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] Student using XO backwards
[ cc'ing devel ] nathan c. riddle wrote: > Did anyone else pick up on the student use of XO in picture of O.K. > School in Manitoba on planet.laptop.org for Dec. 17 ? Using touchpad > behind display. > > Is this just for posing picture or do students use it this way? > > Tried it and easily adapted to reversed motions needed to move pointer > -- feels like I am using a touch tablet. > > > Wonder if pointer response could be reversed for those who were not > comfortable with tablet feel. yes -- the commandline command "olpc-rotate -e" will do it -- it causes both touchpad axes to be reflected. use "olpc-rotate -n" to revert to 'n'ormal. (the 'e' stands for ebook). i thought this facility would be useful when using the laptop in ebook mode, because in that mode the only way to get at the touchpad is by cracking the laptop open slightly, which results in that same "backwards" operation. but i found that in practice it was pretty easy to get used to the reversal, and doing the axis reflection automatically is impossible. (the problem is that the laptop only knows it's in ebook mode when fully closed. as soon as you crack it open to reach the touchpad, it's back in "normal" mode, even though it's only been opened by less than an inch to access the touchpad.) paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: using laptop charger
james wrote: > Shouldn't be destroyed. > > Even if there is an overvoltage condition (beyond 24V), damage should > be constrained to a fuse on motherboard. it's better than that: 24V is where we'll stop charging, and perhaps stop operating -- but the laptop won't be damaged. the laptop will be fine up to 40V, which is when the fuse will blow: http://wiki.laptop.org/go/XO_DC_Input#Overvoltage paul > > Attached microscope photograph taken facing the back of the DC input > connector. Big white device with marking 3R is the fuse, silk screen > label PF2, replacement should be rated 3A at 125V. > > Second set of pads is next, PF1, in parallel, possibly useful if your > fuse is a different shape. > > For continued safety, please replace fuse with required rating, not a > nail or copper wire. > > On Thu, Dec 12, 2013 at 11:48:21PM +, NoiseEHC wrote: > > Thanks for all the answers, I will let you know whether my XO 1.75 > > will be destroyed by the Toshiba adapter... :) > > > > > > On 11/12/2013 20:29, John Watlington wrote: > > >James is correct about 19V probably not working with an XO-1, but with an > > >XO-1.75/4 > > >you should be fine up to 24V. > > > > > >When running with an input voltage higher than 13V, the battery charger > > >on the > > >motherboard runs noticeably hotter. Still within spec at 19V and 45C > > >ambient, > > >but you might notice the difference in case temperature near the DC input > > >plug > > >if charging an empty battery. > > > > > >Cheers, > > >wad > > > > > >On Dec 11, 2013, at 3:09 PM, James Cameron wrote: > > > > > >>G'day Andrew, > > >> > > >>There is a voltage above which the XO-1 will not charge, which had > > >>been often encountered by people using solar panels. Along would come > > >>a cold sunny day, with a greater than normal voltage, and the charging > > >>would stop. > > >> > > >>I don't recall the actual voltage (Richard may remember), but I think > > >>it was somewhere near 18V, and it varied slightly between laptops. > > >> > > >>So it might work, or might not. > > >> > > >>Instead of using a resistor, you might use two or three large diodes > > >>in series, each of which will provide a "forward voltage" 0.6V drop. > > >>Pick the diodes based on the maximum current 1.85A (usually double > > >>that), and the power that will be released as heat; P = V x I, where V > > >>is 0.6, and I is not to exceed 1.85A, so 1.11W minimum "power > > >>dissipation". Place them in a way that does not hold the heat in. > > >> > > >>https://learn.sparkfun.com/tutorials/diodes > > >> > > >>p.s. if you find one diode does what you need, then add another in > > >>case of variation in the supply or laptop. You might even add a > > >>full-wave bridge rectifier instead of two diodes, that way the input > > >>polarity won't matter. > > >> > > >>On Wed, Dec 11, 2013 at 01:52:54PM +, NoiseEHC wrote: > > >>>Hi! > > >>> > > >>>I am thinking about using my laptop's charger instead of the OLPC > > >>>charger in the future as I move a lot and it's getting really > > >>>tiresome to bring both chargers with me. The plan is to create a > > >>>converter plug and use only the laptop's but it has different > > >>>voltage levels. > > >>> > > >>>laptop: TOSHIBA > > >>>part: PA3715U-1ACA > > >>>model: PA-1750-24 > > >>>output: 19V - 3.95A > > >>> > > >>>XO-1.75: DARFON > > >>>model: BBOJ-C > > >>>output: 13.5V - 1.85A > > >>> > > >>>So can I plug my XO to the TOSHIBA adapter? The page says that > > >>>11-18V needed, while the laptop's is 19V. Shall I use a resistor to > > >>>drop the voltage or is it unnecessary? Power usage is not an issue > > >>>to me. (BTW I will use the plug from the XO-1's charger, I guess > > >>>that it did not change in the meantime.) > > >>> > > >>>Thanks, > > >>>Andrew > > >>>___ > > >>>Devel mailing list > > >>>Devel@lists.laptop.org > > >>>http://lists.laptop.org/listinfo/devel > > >>-- > > >>James Cameron > > >>http://quozl.linux.org.au/ > > >>___ > > >>Devel mailing list > > >>Devel@lists.laptop.org > > >>http://lists.laptop.org/listinfo/devel > > > > -- > James Cameron > http://quozl.linux.org.au/ > part 3 text/plain 129 > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO Problems (4 Problems)
walter wrote: > On Sun, Nov 24, 2013 at 1:53 PM, C. Scott Ananian wrote: > > Anyone have any suggestions for my six year old friend? > > IIRC startup volume is persistent, but I can't remember how it is > > adjusted. > > Yes. He can adjust the volume using the volume control on the Frame > and it should persist. really? i thought startup volume (the "on music" -- love it!) was controlled by, and persisted by, OFW, and that it was a separate setting than for the running OS. i.e., it used to be that you had to adjust the volume while the chimes were still playing, and then you'd be all set. paul > > > The rest might be helped by upgrading to the latest XO4 build? > > I recommend he try [1] if he has an XO 4. Feedback appreciated. > > > --scott > > > > -- Forwarded message -- > > From: "Douglas Rogers" > > Date: Nov 24, 2013 12:00 PM > > Subject: XO Problems (4 Problems) > > To: > > Cc: > > > > hi scott it's Douglas. Can you help me make my xo work? > > 1) When I turn on the computer,the ''on music'' is too loud.(so loud I have > > to cover the speakers) > > 2) In scratch when I switch projects all the sprites from the old project > > stay there. > > 3) My XO freezes up a lot > > 4) If I use the touch screen I can't start using the mouse again > > > > > > > > ___ > > Devel mailing list > > Devel@lists.laptop.org > > http://lists.laptop.org/listinfo/devel > > > > -walter > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > > [1] http://wiki.sugarlabs.org/go/0.100/Testing > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: The mouse touch pad doesn't work on XO4
basanta wrote: > Hi list, > Just realized that the mouse touchpad doesn't work for XO4. Has it been > disabled on purpose ? is there a way to enable it ? is this on a single XO-4? the touchpad should work fine. paul =----- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
basanta wrote: > Amazingly changing the manufacturing data didn't do the job but changing > /etc/sysconfig/keyboard did. Wow! Now I have Nepali input system. Thank you > all. i believe /etc/sysconfig/keyboard is created on first boot, using information gleaned from manufacturing data. see /usr/sbin/olpc-configure for details. this would explain why changing the manufacturing tags didn't help -- they've already been consulted, on your test laptop. paul > > Now I need to find a place to change default locale to ne_NP, so that the > default interface is in Nepali. There is an option to do this in > manufacturing data but it would be better if it can be done using file. > -basanta > > > On Tue, Nov 12, 2013 at 6:22 PM, Walter Bender > wrote: > > > Makes things much easier. Now you just have to change the > > manufacruring data as was suggested earlier, but you don't need to > > modify the xkb symbol table. > > > > Good luck. > > > > -walter > > > > On Tue, Nov 12, 2013 at 4:24 AM, James Cameron wrote: > > > Okay, that is consistent with the data we have for the SKU311 > > > mentioned by Samuel on 8th November. > > > > > > The divide and multiply key is the language switch key. > > > > > > On Tue, Nov 12, 2013 at 01:36:35PM +0545, Basanta Shrestha wrote: > > >> The laptops(XO-4) have arrived but it turns out the keyboard is the > > other one > > >> the rubber one (Improved Membrane Keyboard ?). > > >> -Basanta > > >> > > >> > > >> On Tue, Nov 12, 2013 at 10:36 AM, Basanta Shrestha < > > >> basanta.shres...@olenepal.org> wrote: > > >> > > >> D > > >> > > >> > > >> On Mon, Nov 11, 2013 at 11:23 PM, Daniel Drake > > wrote: > > >> > > >> On Sun, Nov 10, 2013 at 5:18 PM, James Cameron < > > qu...@laptop.org> > > >> wrote: > > >> > If you need to scale up this change to many laptops, contact > > >> > reu...@laptop.org or myself. I must know the SKU number. > > >> > > >> In the particular case of changing language/keyboard defaults > > as we > > >> are discussing, instead of changing manufacturing data I would > > >> recommend doing it via olpc-os-builder, configuration for > > [base], see > > >> > > http://dev.laptop.org/git/projects/olpc-os-builder/tree/modules/base/ > > >> README#n46 > > >> > > >> > > >> Doing it via olpc-os-builder would be easier especially when we be > > having > > >> more than 200 laptops to work on. This way we won't have to deal > > with each > > >> and every laptop. So the lines I would have to add would be > > following : > > >> > > >> [base] > > >> default_language=us > > >> > > >> default_kbd_model=us > > >> default_kbd_layout=us > > >> default_kbd_variant=np > > >> > > >> > > >> But where do we set the key combination to switch between default > > and > > >> nepali. I would like to assign alt+space or alt+shift as > > combination. > > >> > > >> Note: We need to set default layout to english. Nepali input is only > > >> required for few activities in Epaath and for typing document in > > Nepali. > > >> > > >> -basanta > > >> > > >> > > >> > > >> > > >> > > >> > > >> -- > > >> Basanta Shrestha > > >> Network Engineer > > >> Open Learning Exchange (OLE) Nepal > > >> Tel: +977.1.551, 5520075 Ext. 303 > > >> Cell: +977.9818 605110 > > >> http://www.olenepal.org > > > > > > -- > > > James Cameron > > > http://quozl.linux.org.au/ > > > > > > > > -- > > Walter Bender > > Sugar Labs > > http://www.sugarlabs.org > > > > > > -- > Basanta Shrestha > Network Engineer > Open Learning Exchange (OLE) Nepal > Tel: +977.1.551, 5520075 Ext. 303 > Cell: +977.9818 605110 > http://www.olenepal.org > part 2 text/plain 153 > ___ > Sugar-devel mailing list > sugar-de...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] seeking help to enable nepali keyboard input for XO-4
walter wrote: > On Fri, Nov 8, 2013 at 8:48 PM, Basanta Shrestha > wrote: > > They are hard/clicky ones. > > So I think what we should do is a combination of the suggestions made > previously: if you set the manufacturing data (KL) [1] to tell the > laptops that they have Nepali keyboards, you will be part of the way > there. But we need to make a new variant (KV) for the "hard/clicky" > (HS) keyboard. As I mentioned earlier, we need to decide what the key > combination for switching languages will be, since there is no > physical :Language key. at what level is the language key handled, on laptops with the membrane keyboards? (i.e., X? sugar?) that might influence what sort of combination is available or useful for doing the switch. paul > > -walter > > [1] http://wiki.laptop.org/go/Manufacturing_data > > > > > > On Fri, Nov 8, 2013 at 10:24 PM, Daniel Drake wrote: > >> > >> On Thu, Nov 7, 2013 at 11:23 PM, Basanta Shrestha > >> wrote: > >> > But for XO-4 we will just be getting ones with English layout. I was > >> > wondering how we can enable nepali keyboard input on it. > >> > >> Are these keyboards hard/clicky/high-school style, or soft/membrane? > >> > >> Daniel > > > > > > > > > > -- > > Basanta Shrestha > > Network Engineer > > Open Learning Exchange (OLE) Nepal > > Tel: +977.1.551, 5520075 Ext. 303 > > Cell: +977.9818 605110 > > http://www.olenepal.org > > > > ___ > > Sugar-devel mailing list > > sugar-de...@lists.sugarlabs.org > > http://lists.sugarlabs.org/listinfo/sugar-devel > > > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > ___ > Sugar-devel mailing list > sugar-de...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: pretty boot stall on 1.5
kevin wrote: > > > > One of the first things powerd interacts with is the network card, I'd > > run the OFW's tests for wifi. On one of the problem XOs, once in sugar > > can you connect to an AP? Can you send me the logs from /var/log off > > list to have a quick look at? > > ... > Jerry, you're a troubleshooting genius. Once I got into sugar from the > check-mark boot, I could see the AP's, but couldn't connect. > > Alas, having that insight, this now became a probelm which I had seen > before and knew how to solve. :-) > > Yep, as I'm sure everyone on the list will now giggle at me ... the hwclock > was set to 01/01/1963,. once i did the date -- set, then hwclock > --systohc, all works wonderfully on pretty boot. ah yes. the bad date confuses powerd. time in unix is normally counted in seconds since the start of 1970, so your date causes time to be reported as a negative number. powerd discards events that may have arrived before some reasonable time in the past -- this is usually the time of last suspend -- but at boot the value compared against is 0. so all events prior to 1970 appear too old, and they all get discarded. (and so the DCON isn't unfrozen.) the fix for this happens to be the very last commit made to powerd, and was released in powerd-110. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: ARM XO model
yioryos wrote: > Is the XO version/model info somewhere in /sys for the ARM XOs as > it is for the x86 XOs (in /sys/class/dmi/id/)? look under /proc/device-tree paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-tablet development?
frantisek wrote: > Hello, > > sorry if this was already discussed but where development discussion > about new XO-tablet is taking place? Where is the documentation/wiki? there are not yet any public development or documentation channels, that i know of. > > I understand it is android based (i.e. very different from xo laptops) > but I am still missing discussion about the hardware itself and also the > software (android UI modification, preloaded applications). OLPC was not involved in the development of the tablet hardware. > > Is some XO laptop software shared between laptop and tablet (sugar, > activities,...)? i don't believe so, currently. that could change. > Is the UI and preloaded apps on the tablet open sourced? no, not generally. parts of android are open source, of course, and some of the included apps may also be. but much is closed source, including, i believe, the UI. > Is this developed by olpc people or outsourced to completely different > people/company? hardware was done by an external vendor. UI software and integration was by an OLPC-funded team, which until recently was completely separate from the laptop development team. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Request for mDNS name resolution from Internet-in-a-Box project
braddock wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Dear OLPC Devel folks, > Is it possible to enable mDNS name resolution in future builds of OLPC OS? > > Fedora and most Linux distros (not to mention Macs) support mDNS out > of the box, yet for some reason it is turned off in OLPC OS. I > believe all that is required is the addition of the nss-mdns package > to the OLPC OS build. if it's that simple, can your deployments simply do that installation with yum? or is there something else missing, either from the laptop, or from my understanding? paul > > Enabling mDNS allows us to add an Internet-in-a-Box network appliance > to an XO deployment network with zero configuration. The user just > plugs our device into their network and browser queries for > http://know.local simply resolve. > > This works on Mac and most flavors of Linux, and for Windows we > provide an NMB name at http://know. > > But ironically the XO seems to lack any mechanism for de-centralized > local resource discovery. > > Unfortunately, since OLPC OS does not resolve mDNS names we are > finding deployments to XO schools are much, much harder. > > We are, for example, right now in the middle of a deployment to a > large school with XOs in Pakistan. Instead of just plugging in the > Internet-in-a-Box device, the people on-site need to reconfigure DHCPd > on their CentOS XS School Server to supply a static IP to our > appliance's MAC address, then use the IP address from the XO's > browser. Not ideal, and I'm not sure they will succeed. > > A successful deployment of Internet-in-a-Box to a Windows-based school > in Sierra Leone, on the other hand, was trivial. > > Thanks, > Braddock Gaskill > Founder, Internet-in-a-Box Project > http://internet-in-a-box.org > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.11 (GNU/Linux) > Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ > > iQEcBAEBAgAGBQJR+YPTAAoJEHWLR/DQzlZubWAH/AsAPXBJgIiUzT44jqZeObJF > a3ebCOypZnDTYHO+RVd3T3fGhx3uopFY3zQjiywZ+9sKYEQlMOg/pVoYtXxfAdXD > wmxWKy26iyl2po+KXJlPyT7brEJ1MKkHmlyTZiXSj82E5pf9BbITFsQjEwqeeGwe > 9JO8YjOmaUVbZVRuNSWfwsPJz2RlZZPNZR9d/VGkyTkvmNRiaqvNpFBa8SyFFC7D > F7E6mPsAvzTDogXQz3RCsyHjmXV/BIpl5nqtFViVEp4hbjWc2kXwdEqLqX27dWJC > /SWovkjOifwWyvd0aiLEM0202RN/FzsdhAl50e1ptV3EzEw1bZXHD+83ty0N0hQ= > =xnyF > -END PGP SIGNATURE----- > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Seeking advice to buy ARM system.
basanta wrote: > Hi, > We are considering buying an ARM system in order to build Operating System > Images for XO(1.75 and 4) laptops. Currently we are doing this under > virtualization environment using "Fedora-17-armhfp-vexpress" which is very > slow. > > I am seeking some expert advice on which ARM system/board to buy from the > list. So far I have been suggested Wandboard quad and Odriod-U2. i can tell you that OLPC will be just as interested in any data you collect. all of our ARM builds to date have been done on a donated bare evaluation mother board from Marvell, which conveniently has expandable RAM (3G, i believe) and SATA ports. i would be inclined to exclude the Odroid board based on lack of SATA, and both boards you mention are limited to 2G of RAM. but we've not done much experimentation, so they might not be completely inappropriate. the recently announced Utilite (utilite-computer.com) looks interesting, but isn't available yet, so who knows? paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Different boot sound on XO1.75
juan wrote: > Just downgraded do Q4D20 and the original sound has been restored :) > > I had no idea that certain OS versions had to be matched to certain > Firmware versions... > I always tried to keep up with the latest on my test machines. we try very hard to maintain both forward and backward compatibility, but of course that's not always possible. i think the release notes usually cover any major issues. in this case, we needed to reclaim space in flash for the firmware, so the startup jingle file was moved to the root filesystem. the effect is aesthetic only, but still surprising. paul > > - Juan > > On 06/20/2013 11:41 AM, Daniel Drake wrote: > > On Thu, Jun 20, 2013 at 11:36 AM, Juan Cubillo > > wrote: > >> That might be an option, but not in my case. Both XOs have Build 13.0.1 > >> and > >> Firmware Q4D28. > >> > >> I'll wait for James to wake up :) > > In the mean time maybe you can explain why changing firmware version > > and/or OS version is not an option. It might help us give good advice. > > > > Thanks > > Daniel > > _______ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Upstreaming MMP clock devicetree support
mp/clk-apbc.c
> index 89a146a..d53bc79 100644
> --- a/drivers/clk/mmp/clk-apbc.c
> +++ b/drivers/clk/mmp/clk-apbc.c
> @@ -15,6 +15,8 @@
> #include
> #include
> #include
> +#include
> +#include
>
> #include "clk.h"
>
> @@ -129,8 +131,70 @@ struct clk *mmp_clk_register_apbc(const char *name,
> const char *parent_name,
> apbc->hw.init = &init;
>
> clk = clk_register(NULL, &apbc->hw);
> -if (IS_ERR(clk))
> +if (WARN_ON(IS_ERR(clk)))
> kfree(apbc);
>
> return clk;
> }
> +
> +static void __init mmp_apbc_dt_init(struct device_node *node)
> +{
> +struct device_node *parent = of_get_parent(node);
> +const __be32 *regs;
> +struct clk *clk;
> +int rc;
> +int len;
> +int num_clocks;
> +int clock_num;
> +void __iomem *baseaddr;
> +const char *clock_name;
> +const char *parent_name;
> +struct clk **clks;
> +struct clk_onecell_data *clk_data;
> +
> +regs = of_get_property(node, "reg", &len);
> +if (WARN_ON(!regs || (len % sizeof(__be32) != 0)))
> +return;
> +num_clocks = len / sizeof(__be32);
> +
> +baseaddr = of_iomap(parent, 0);
> +of_node_put(parent);
> +if (WARN_ON(!baseaddr))
> +return;
> +
> +clk_data = kzalloc(sizeof(*clk_data), GFP_KERNEL);
> +if (WARN_ON(!clk_data))
> +goto err_clk_data;
> +
> +clks = kzalloc(num_clocks * sizeof(*clks), GFP_KERNEL);
> +if (WARN_ON(!clks))
> +goto err_clks;
> +
> +clock_name = of_get_property(node, "clock-output-names", NULL);
> + parent_name = of_clk_get_parent_name(node, 0);
> +
> +for (clock_num = 0; clock_num < num_clocks; clock_num++) {
> +void __iomem *clock_addr;
> +clock_addr = baseaddr + be32_to_cpup(regs + clock_num);
> +
> +clk = mmp_clk_register_apbc(clock_name, parent_name,
> +clock_addr, 10, 0);
> +if (IS_ERR(clk))
> +return;
> +clock_name += strlen(clock_name) + 1;
> +clks[clock_num] = clk;
> +}
> +
> +clk_data->clk_num = num_clocks;
> +clk_data->clks = clks;
> +rc = of_clk_add_provider(node, of_clk_src_onecell_get, clk_data);
> +WARN_ON(rc);
> +return;
> +
> +err_clks:
> +kfree(clk_data);
> +err_clk_data:
> +iounmap(baseaddr);
> +
> +}
> +CLK_OF_DECLARE(mmp2_apbc, "marvell,mmp-apb-clock", mmp_apbc_dt_init);
> diff --git a/drivers/clk/mmp/clk-apmu.c b/drivers/clk/mmp/clk-apmu.c
> index 4f4d8c5..dfcecc9 100644
> --- a/drivers/clk/mmp/clk-apmu.c
> +++ b/drivers/clk/mmp/clk-apmu.c
> @@ -15,6 +15,8 @@
> #include
> #include
> #include
> +#include
> +#include
>
> #include "clk.h"
>
> @@ -22,7 +24,6 @@
> struct clk_apmu {
> struct clk_hw hw;
> void __iomem*base;
> -u32 rst_mask;
> u32 enable_mask;
> };
>
> @@ -85,3 +86,37 @@ struct clk *mmp_clk_register_apmu(const char *name, const
> char *parent_name,
>
> return clk;
> }
> +
> +static void __init mmp_apmu_dt_init(struct device_node *node)
> +{
> +struct device_node *parent = of_get_parent(node);
> +const char *clk_name = node->name;
> +void __iomem *baseaddr;
> +struct clk *clk;
> +u32 reg;
> +u32 enable_mask;
> +int rc;
> +
> +rc = of_property_read_u32(node, "reg", ®);
> +if (WARN_ON(rc))
> +return;
> +
> +rc = of_property_read_u32(node, "enable-mask", &enable_mask);
> +if (WARN_ON(rc))
> +return;
> +
> +baseaddr = of_iomap(parent, 0);
> +of_node_put(parent);
> +if (WARN_ON(!baseaddr))
> +return;
> +
> +of_property_read_string(node, "clock-output-names", &clk_name);
> +clk = mmp_clk_register_apmu(clk_name, of_clk_get_parent_name(node, 0),
> +baseaddr + reg, enable_mask);
> +if (WARN_ON(IS_ERR(clk)))
> +return;
> +
> +rc = of_clk_add_provider(node, of_clk_src_simple_get, clk);
> +WARN_ON(rc);
> +}
> +CLK_OF_DECLARE(mmp2_apmu, "marvell,mmp-apmu-clock", mmp_apmu_dt_init);
> diff --git a/drivers/clk/mmp/clk-mmp2.c b/drivers/clk/mmp/clk-mmp2.c
> index 6f654c3..6abb083 100644
> --- a/drivers/clk/mmp/clk-mmp2.c
> +++ b/drivers/clk/mmp/clk-mmp2.c
> @@ -15,6 +15,7 @@
> #include
> #include
> #include
> +#include
>
> #include
>
> @@ -73,7 +74,7 @@ static const char *sdh_parent[] = {"pll1_4", "pll2",
> "usb_pll", "pll1"};
> static const char *disp_parent[] = {"pll1", "pll1_16", "pll2", "vctcxo"};
> static const char *ccic_parent[] = {"pll1_2", "pll1_16", "vctcxo"};
>
> -void __init mmp2_clk_init(void)
> +static void __init mmp2_clk_init_static(void)
> {
> struct clk *clk;
> struct clk *vctcxo;
> @@ -445,3 +446,19 @@ void __init mmp2_clk_init(void)
> apmu_base + APMU_CCIC1, 0x300);
> clk_register_clkdev(clk, "sphyclk", "mmp-ccic.1");
> }
> +
> +void __init mmp2_clk_init(void)
> +{
> +struct device_node *node;
> +
> +/* The presence of the ABP clock node in the device tree indicates
> + * that we should use the DT for clock setup. */
> +node = of_find_compatible_node(NULL, NULL, "marvell,mmp-apb-clock");
> +if (node) {
> +of_node_put(node);
> +of_clk_init(NULL);
> +} else {
> +/* Fallback to static setup */
> +mmp2_clk_init_static();
> +}
> +}
> --
> 1.8.1.4
>
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
=-
paul fox, p...@laptop.org
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: Compiling thee kernel
ajay wrote: > On Tue, Jun 11, 2013 at 6:25 PM, Paul Fox wrote: > > > ajay wrote: > > > Hi James. > > > Thanks a ton for the reply > > > > > > Here are the steps I followed on my x86-based Dell laptop:: > > > > > > a) > > > "cd ~" > > > > > > > > > b) > > > "git clone git://dev.laptop.org/olpc-kernel" > > > > > > > > > c) > > > "cd olpc-kernel" > > > > > > > you left out: > > cp arch/x86/configs/xo_1.5_defconfig .config > > make oldconfig > > > > Ohh ok.. oops. you're probably still on master. there's another missing step: git checkout x86-3.3 paul > > Currently, I do not see any such file as arch/x86/configs/xo_1.5_defconfig > :-\ > Doing "ls -l arch/x86/configs gives me" :: > > [ajay@localhost olpc-kernel]$ ls -l arch/x86/configs/ > total 16 > -rw-rw-r--. 1 ajay ajay 7511 Jun 9 05:37 i386_defconfig > -rw-rw-r--. 1 ajay ajay 7528 Jun 9 05:37 x86_64_defconfig > > > Paul, > > a) > Are there some additional steps to generate the config file for XO-1.5? > > b) > Secondly, is the "marvell" module generatable only on the XO-1.5? As far as > I know, the OmniVersion sensor works since the earliest series of laptops? > > > > > paul > > > > > > > > d) > > > "make" > > > > > > > > > e) > > > Wait many minutes (if not hours). > > > Everything runs to completion. > > > > > > > > > f) > > > Haphazardly edit "drivers/media/video/ov7670.c". > > > > > > > > > g) > > > Now, run "make" again. > > > > > > Because of the haphazard editing of the file in step f), the build > > should > > > break. > > > However, it doesn't, and it runs to completion as before. > > > > > > > > > h) > > > At any time, there is no object file (.o) or kernel-object (.ko) file > > > whatsoever in the directory "drivers/media/video/marvell-ccic". > > > > > > > > > i) > > > Because of observation of step h), and the fact that "ov7670.h" is used > > in > > > the file "drivers/media/video/marvell-ccic/mcam-core.c", > > > I doubt if the "marvell" module is being compiled at all. > > > > > > > > > j) > > > Moreover, the "I2C VS SMBus" has stemmed into my imagination, looking at > > > the file "drivers/media/video/Kconfig" :) > > > > > > > > > Note that following the steps f) and g) after haphazardly editing a > > > different file like "drivers/media/video/tvaudio.c" DOES break the > > build. > > > That means that I am at least following the right ways to break the > > build :P > > > > > > > > > James, > > > please let me know if you require any more info. > > > > > > Thanks again for the help !! > > > > > > > > > On Tue, Jun 11, 2013 at 4:05 PM, James Cameron > > wrote: > > > > > > > G'day Ajay, > > > > > > > > I've never heard of such a restriction. Can you tell us the name of > > > > the branch you compiled, and what method you used? Perhaps share the > > > > output? > > > > > > > > -- > > > > James Cameron > > > > http://quozl.linux.org.au/ > > > > > > > > > > > > > > > > -- > > > Regards, > > > > > > Ajay Garg > > > Dextrose Developer > > > Activity Central: http://activitycentral.com > > > part 2 text/plain 129 > > > ___ > > > Devel mailing list > > > Devel@lists.laptop.org > > > http://lists.laptop.org/listinfo/devel > > > > =- > > paul fox, p...@laptop.org > > ___ > > Devel mailing list > > Devel@lists.laptop.org > > http://lists.laptop.org/listinfo/devel > > > > > > -- > Regards, > > Ajay Garg > Dextrose Developer > Activity Central: http://activitycentral.com =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Compiling thee kernel
ajay wrote: > Hi James. > Thanks a ton for the reply > > Here are the steps I followed on my x86-based Dell laptop:: > > a) > "cd ~" > > > b) > "git clone git://dev.laptop.org/olpc-kernel" > > > c) > "cd olpc-kernel" > you left out: cp arch/x86/configs/xo_1.5_defconfig .config make oldconfig paul > > d) > "make" > > > e) > Wait many minutes (if not hours). > Everything runs to completion. > > > f) > Haphazardly edit "drivers/media/video/ov7670.c". > > > g) > Now, run "make" again. > > Because of the haphazard editing of the file in step f), the build should > break. > However, it doesn't, and it runs to completion as before. > > > h) > At any time, there is no object file (.o) or kernel-object (.ko) file > whatsoever in the directory "drivers/media/video/marvell-ccic". > > > i) > Because of observation of step h), and the fact that "ov7670.h" is used in > the file "drivers/media/video/marvell-ccic/mcam-core.c", > I doubt if the "marvell" module is being compiled at all. > > > j) > Moreover, the "I2C VS SMBus" has stemmed into my imagination, looking at > the file "drivers/media/video/Kconfig" :) > > > Note that following the steps f) and g) after haphazardly editing a > different file like "drivers/media/video/tvaudio.c" DOES break the build. > That means that I am at least following the right ways to break the build :P > > > James, > please let me know if you require any more info. > > Thanks again for the help !! > > > On Tue, Jun 11, 2013 at 4:05 PM, James Cameron wrote: > > > G'day Ajay, > > > > I've never heard of such a restriction. Can you tell us the name of > > the branch you compiled, and what method you used? Perhaps share the > > output? > > > > -- > > James Cameron > > http://quozl.linux.org.au/ > > > > > > -- > Regards, > > Ajay Garg > Dextrose Developer > Activity Central: http://activitycentral.com > part 2 text/plain 129 > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: squashfs module for ARM kernels
now that we've got several patches on the list for this, perhaps someone could open a ticket requesting the feature, with the right patches attached. i'm sure it will make the someone's job easier. target the ticket for 13.2.0. (and don't wait too long. that train's about to leave the station! :-) paul yioryos wrote: > > This is a good idea. We already have CONFIG_SQUASHFS=m > > on the XO-1 > > and XO-1.5 kernels. It won't be loaded unless needed > > by user-space, > > so it is low risk to add. > > > > Attached is a patch for XO-4. I wasn't able to figure > > out a patch for > > XO-1.75, because "make oldconfig" asked me far too many > > questions. > > > > If squashfs module building is activated, you may want to consider xz > support too. Is becoming rapidly prevalent and does not increase module size > much. > Attached are patches for xo-1.75 (3.0-wip kernel, > 3bef06d573cebfdb4ff0d9832f3fc1aea93d22fa) and xo-4 (3.5 kernel, > 265e8dda6a55825aca3bb39f6c531522e1d357fc) defoconfigs. They build sane > kernels but I could only test XO-1.75 (no XO-4) > part 3 text/plain 129 > _______ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Transient-Issues with game-keys on XO-1.75
ajay wrote: > On Tue, Apr 16, 2013 at 2:24 AM, Walter Bender > wrote: > > > Sure it is not the hardware (misaligned buttons)? > > > > Don't think so :-\ > > The results are not consistent, irrespective of whether I press the key(s) > gently, or with force. > The only consistent thing is the correct working of the "square" key. > > Anyhow, the best test for this issue is only if more than one person does a > quick test for this :) have you tried the keyboard diagnostic from OFW? ok test /keyboard paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: wifi power on/off
yioryos wrote:
> I'm trying to cycle the power of the wifi card on the XO-1{.5] but after
> half an hour of fruitless searching of the list/wiki/web I thought to ask,
> since I remember being discussed here.
> Could please someone points to the terminal commands to turn off and on
> power on the usb8388 and sd8686 modules/cards?
can't be done, on recent releases. well, at least for 1.5 and later
laptops. it may still be operational for XO-1 [1]. our rfkill-based
mechanism was messy, and it was rejected when we attempted to put it
upstream.
the mechanism hasn't yet been replaced -- someday the card should
power down with "ifconfig eth0 down".
paul
[1] on XO-1 the commands to try are "rfkill block wifi" and "rfkill
unblock wifi".
> Thanks
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
=-
paul fox, p...@laptop.org
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: RAM in XO-1.75-models
ajay wrote: > Hi all. > > As per http://wiki.laptop.org/go/XO-1.75, the RAM in XO-1.75 is > >"DRAM memory: 512 MB or 1GB DDR3 dynamic > RAM<http://en.wikipedia.org/wiki/DDR3_SDRAM>; > " > > Is there any specific criteria as to which models have 512 MB, and which > have 1 GB? > I, for example, have 512 MB of RAM, on a CL1 model. the SKU number of a laptop tells you how it was built: http://wiki.laptop.org/go/Manufacturing_data#XO-1.75 =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: minimizing footprint
martin wrote: > Hi Paul, > > On Sun, Mar 24, 2013 at 6:34 PM, Paul Fox wrote: > > but when systemd falls out of favor in a year or two we'll just have > > to change things again -- either to something new, or back to cron > > Not sure whether you're stating that straight or facetiously. > > Systemd has some shortcomings, but it seems to be an outstanding step > ahead in Linux system infra. And it is evolving quickly for the better > -- I can't see any fundamental problem with it, and its limitations > and blemishes will be overcome. we'll see. =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: minimizing footprint
i think the point john (gilmore) was making is that it's a bad precedent that simply because a) systemd offers a second-rate API for scheduling events, and b) we only have a couple of uses for an event scheduler, that we should therefore switch from a well-established API to a lousy API. instead, if systemd can be made to support the cron API properly, it would be worth making it do so. barring that, or if it's too much work (likely), then if it saves us boatloads of disk to make the switch, and our use-cases don't lose functionality or correctness as a result, then i guess we should switch. but when systemd falls out of favor in a year or two we'll just have to change things again -- either to something new, or back to cron (which will most certainly still be available). paul gonzalo wrote: > On Sun, Mar 24, 2013 at 11:29 AM, Tony Anderson wrote: > > > On 03/24/2013 09:38 AM, devel-requ...@lists.laptop.org wrote: > > > >> It's true, we need learn new tricks, but does not have sense have a > >> service > >> not needed on every xo, if we can do it in a better way. > >> > > > > Does this logic apply generally? > > > > 12.1.0 has a control panel entry 'Modem configuration'. How many XOs > > require this capability? > > > > > Generally. > In the case we are discussing, we don't need remove a feature, > only implement it in a different way. > > Gonzalo > part 2 text/plain 129 > _______ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Kernel RPMs now auto-install to boot partition
wow. somehow i didn't think this would ever happen. thank you!! paul daniel wrote: > Hi, > > Found some time to implement something that has been desired for a > while: now when you install a kernel RPM on the XO, it will > additionally auto-install to the boot partition, so now you can just > install a new kernel RPM with rpm/yum and reboot and expect it to be > used, no additional steps needed. > > The root of this strange behaviour (installing kernels twice) is due > to the design of the update system, there might be room to improve on > this in future as well, but at least this detail will now be less > annoying to developers. > > Daniel > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] gray dots forever: when 12.1.0 & 13.1.0 never fully boot (XO-1 especially? 11.3.1 too)
john wrote: > (1) If powerd fails when the clock is set to before the Unix epoch, > powerd is buggy, and this bug should be ticketed and fixed. i agree. though i confess yesterday was the first time i'd ever seen a negative number from "date +%s". it kind of threw me. ticket filed: https://dev.laptop.org/ticket/12621 > > That bug is independent of the situation that causes the clock to get > set that way (which may well be another bug in another component, which > would deserve another ticket). it's likely that bad validation of RTC register values is to blame, though that remains to be seen. paul > > (2) Perhaps the reason there is trouble with reflashing some laptops > whose clocks are bad is that the signature on the new release has a > limited validity time period, and the security system is rejecting the > new release because the bad clock looks like it's outside the validity > period? > > John > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Is it possible to hack the "rotate" key?
ajay wrote: > Thanks Gary and Paul. > I tested "Moon" on build 28 on XO-4; and the rotation caused the canvas to > be redrawn appropriately. > okay. was that unexpected? > > Paul, > > I have two queries :: > > a) > In "Moon"'s code (as already told by Gary), the "size-changed" signal is > used to call the callback that redraws the canvas. > So, in this case, is the "size-changed" signal a result of the > rotate-key-event (KEY_SWITCHVIDEOMODE), or "size-changed" signal is > generated via some another mechanism? i don't know. > > b) > Is the behaviour of olpc-kbdshim the same for a XO-1.75 and a XO-4 (as far > as "that code is written to either run a command > attached to the event (currently /usr/bin/olpc-rotate), or pass the event > through, but not both" is concerned)? yes. and for XO-1 and XO-1.5 as well. paul > > > > > On Mon, Feb 18, 2013 at 7:18 PM, Paul Fox wrote: > > > ajay wrote: > > > Hi all. > > > > > > Is it possible to hack the "rotate" key in XO? > > > > > > I wish to have the following working :: > > > > > > * Press the "rotate" key. This will rotate the window. > > > * Just after that, have a callback function being called in "sugar" > > > (this of course being possible only if the "rotate" key could be > > hacked). > > > > > > > as gary points out, the rotate key event (KEY_SWITCHVIDEOMODE) is > > caught by olpc-kbdshim. that code is written to either run a command > > attached to the event (currently /usr/bin/olpc-rotate), or pass the > > event through, but not both. > > > > if there were consensus that running the command _and_ passing the > > event was safe and reasonable, maybe we could do that, though it > > doesn't feel right to me. > > > > but i also think gary's on the right track by suggesting you look at > > other window events to learn of the rotation changes -- after all, > > rotation doesn't require a button press. it can be caused by manual > > xrandr invocation, or simply by someone typing "olpc-rotate left". > > > > paul > > > > > > > > > > > I will be thankful for any pointers. > > > > > > > > > > > > Regards, > > > > > > Ajay Garg > > > Dextrose Developer > > > Activity Central: http://activitycentral.com > > > part 2 text/plain 129 > > > ___ > > > Devel mailing list > > > Devel@lists.laptop.org > > > http://lists.laptop.org/listinfo/devel > > > > =- > > paul fox, p...@laptop.org > > ___ > > Devel mailing list > > Devel@lists.laptop.org > > http://lists.laptop.org/listinfo/devel > > > > > > -- > Regards, > > Ajay Garg > Dextrose Developer > Activity Central: http://activitycentral.com =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Is it possible to hack the "rotate" key?
ajay wrote: > Hi all. > > Is it possible to hack the "rotate" key in XO? > > I wish to have the following working :: > > * Press the "rotate" key. This will rotate the window. > * Just after that, have a callback function being called in "sugar" > (this of course being possible only if the "rotate" key could be hacked). > as gary points out, the rotate key event (KEY_SWITCHVIDEOMODE) is caught by olpc-kbdshim. that code is written to either run a command attached to the event (currently /usr/bin/olpc-rotate), or pass the event through, but not both. if there were consensus that running the command _and_ passing the event was safe and reasonable, maybe we could do that, though it doesn't feel right to me. but i also think gary's on the right track by suggesting you look at other window events to learn of the rotation changes -- after all, rotation doesn't require a button press. it can be caused by manual xrandr invocation, or simply by someone typing "olpc-rotate left". paul > > > I will be thankful for any pointers. > > > > Regards, > > Ajay Garg > Dextrose Developer > Activity Central: http://activitycentral.com > part 2 text/plain 129 > _______ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: What I have to do for the same?
pas...@diogoantunes.org wrote: > > No, I put a wrong inittab (may be), and now the XO doesn't run (it > freezes on the chargement animation after 18 points). What can I do? please continue to use the mailing list. that way other people besides me can see your questions and can help you. push and hold the "checkmark" game key while turning on the power. this may give more information as to what is happening: http://wiki.laptop.org/go/Startup_Diagnosis#Check-Key_Boot if you cannot boot, you may be able to boot from a a USB stick, and rescue your system. for instance, you might be able to boot "puppy linux": http://wiki.laptop.org/go/PuppyLinux#XOpup.3B_Puppy_Linux_5.1_for_the_XO-1_and_the_XO-1.5 or, you could simply reinstall the OLPC software. paul > > Well, after this, I will test, but at this point I can't do nothing. > > Thanks. > Libere, > Pascal Diogo Antunes. =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-4 not resuming after suspend
gary wrote: > On 3 Feb 2013, at 22:04, Paul Fox wrote: > > > jerry wrote: > >> On Sat, 2013-02-02 at 09:25 +1100, fors...@ozonline.com.au wrote: > >>>>>>> I have an XO-4 B1, OFW Q7B14, EC Firmware 0.3.10, os28. > >>>>>>> > >>>>>>> It won't resume after suspend, but sometimes it does. I couldn't > >>>>>>> reproduce the bug, but it happens most of the time. > >>> ... > >>>>>>> Anyone else seeing this? > >>>>>>> > >>> > >> > >> I'm seeing this with my B1, hard lock just after suspending, can't > >> awaken the XO via any input method. Sorry no logs for this one. > >> > >> > >>> For me, OS28 XO-4 doesnt seem to be going into suspend, mostly. It did > >>> suspend once and when it resumed it did not load the cursor, just a > >>> square of noise like a QR code, a bug we had in the early XO-4 builds. > >>> It seems suspend has regressed from OS27. > >>> > >>> Tony > >>> > >> > >> I'm seeing this with the C2 unit I have, enabling powerd's tracing shows > >> suspend is being skipped with "cpu busy" once a rtcalarm wakeup event > >> occurs during until_dim-soft. I have the logs if needed. > > > > thanks -- yes, we've observed that something is consuming cpu > > on os28, preventing suspend. > > Testing os28 on a XO-4 B1, and XO-4 C2: Interestingly if automatic > power management is disabled in Sugar, My Settings, the backlight > does start to correctly auto switch off when idle. With automatic > power management on it is even preventing the backlight from > powering off. it's an algorithmic thing: if suspend is desired, and can't happen, no ensuing actions (dimming, blanking) will happen either. but if suspend isn't desired, it's effectively scheduled far, far, in the future. so dimming and blanking will happen first, and they're not inhibited by most suspend inhibitors (like CPU busy, in this case). paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: What I have to do for the same?
martin wrote: > If you are using Sugar, you can also disable power management from the > control panel. i believe pascal is trying to do something different. i believe he wants power management, but nothing else -- no X, no sugar. so he wants a different run-level to include power management. paul > > cheers, > > > > m > > On Sun, Feb 3, 2013 at 6:52 PM, wrote: > > Hi, > > I have a simple question: > > when I use my XO-1, if I do nothing, after 15 sec, it changes to a > > middle-suspend : only the screen isn't off. > > So what I have to enable or disable to have the same on another init mod > > (init 2 for example)? > > Because I would to have the minimum of services (with my initdefault on > > starting up), without modificate my init (5). So for the moment, I have > > modificated the inittab, but now, I would to have the middle-suspend on > > inactivited use. > > How and what I have to do? > > > > Thanks in advance. > > > > Best Regards, > > Pascal Diogo Antunes. > > > > ps: sorry if i wrote on the wrong list, but i didn't have response on the > > test@list. > > > > ___ > > Devel mailing list > > Devel@lists.laptop.org > > http://lists.laptop.org/listinfo/devel > > > > -- > martin.langh...@gmail.com > mar...@laptop.org -- Software Architect - OLPC > - ask interesting questions > - don't get distracted with shiny stuff - working code first > - http://wiki.laptop.org/go/User:Martinlanghoff > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: What I have to do for the same?
pas...@diogoantunes.org wrote: > Quoting Paul Fox : > > > pas...@diogoantunes.org wrote: > > > Hi, > > > I have a simple question: > > > when I use my XO-1, if I do nothing, after 15 sec, it changes to a > > > middle-suspend : only the screen isn't off. > > > So what I have to enable or disable to have the same on another init > > > mod (init 2 for example)? > > > Because I would to have the minimum of services (with my initdefault > > > on starting up), without modificate my init (5). So for the moment, I > > > have modificated the inittab, but now, I would to have the > > > middle-suspend on inactivited use. > > > How and what I have to do? > > > > this is the correct list for your question. > > > > the "middle suspend" you speak of, triggered by inactivity, is > > provided by /usr/sbin/powerd. powerd doesn't care about init > > levels, so if you arrange to have powerd run in runlevel 2, then > > you will get the same behavior you currently get in runlevel 5. > > > > the configuration for powerd is found in /etc/powerd/powerd.conf. > > there is more documentation in the comments in /usr/sbin/powerd itself. > > (for better or worse, powerd is a shell script.) any modifications > > you make to the powerd configuration will take effect both in init 5 > > and in init 2. > > > > paul > > > > > > > > Thanks in advance. > > > > > > Best Regards, > > > Pascal Diogo Antunes. > > > > > > ps: sorry if i wrote on the wrong list, but i didn't have response on > > > the test@list. > > > > > > ___ > > > Devel mailing list > > > Devel@lists.laptop.org > > > http://lists.laptop.org/listinfo/devel > > > > =- > > paul fox, p...@laptop.org > > > > Okay thanks. > The problem is on the init 2 mod, even with powerd runed, I have no > reactions (with screen blank or freeze) on a idle functionment. > I change the values on configuration, but it works only on init 5. > No big deal, I did simple test, I will do all what I want on init 5. > So you said all I needed. there are two other programs that i forgot about. sorry. you also need to be sure that olpc-switchd and olpc-kbdshim are running in init 2. these are support programs that help powerd. (you didn't say what software version you are running on your XO-1. on recent systems, olpc-kbdshim is a standalone daemon, but on earlier systems its invoked via hal.) paul > Thanks. > > Libere, > Pascal Diogo Antunes. =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: What I have to do for the same?
pas...@diogoantunes.org wrote: > Hi, > I have a simple question: > when I use my XO-1, if I do nothing, after 15 sec, it changes to a > middle-suspend : only the screen isn't off. > So what I have to enable or disable to have the same on another init > mod (init 2 for example)? > Because I would to have the minimum of services (with my initdefault > on starting up), without modificate my init (5). So for the moment, I > have modificated the inittab, but now, I would to have the > middle-suspend on inactivited use. > How and what I have to do? this is the correct list for your question. the "middle suspend" you speak of, triggered by inactivity, is provided by /usr/sbin/powerd. powerd doesn't care about init levels, so if you arrange to have powerd run in runlevel 2, then you will get the same behavior you currently get in runlevel 5. the configuration for powerd is found in /etc/powerd/powerd.conf. there is more documentation in the comments in /usr/sbin/powerd itself. (for better or worse, powerd is a shell script.) any modifications you make to the powerd configuration will take effect both in init 5 and in init 2. paul > > Thanks in advance. > > Best Regards, > Pascal Diogo Antunes. > > ps: sorry if i wrote on the wrong list, but i didn't have response on > the test@list. > > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-4 not resuming after suspend
jerry wrote: > On Sat, 2013-02-02 at 09:25 +1100, fors...@ozonline.com.au wrote: > > > >> > I have an XO-4 B1, OFW Q7B14, EC Firmware 0.3.10, os28. > > > >> > > > > >> > It won't resume after suspend, but sometimes it does. I couldn't > > > >> > reproduce the bug, but it happens most of the time. > > ... > > > >> > Anyone else seeing this? > > > >> > > > > > I'm seeing this with my B1, hard lock just after suspending, can't > awaken the XO via any input method. Sorry no logs for this one. > > > > For me, OS28 XO-4 doesnt seem to be going into suspend, mostly. It did > > suspend once and when it resumed it did not load the cursor, just a square > > of noise like a QR code, a bug we had in the early XO-4 builds. It seems > > suspend has regressed from OS27. > > > > Tony > > > > I'm seeing this with the C2 unit I have, enabling powerd's tracing shows > suspend is being skipped with "cpu busy" once a rtcalarm wakeup event > occurs during until_dim-soft. I have the logs if needed. thanks -- yes, we've observed that something is consuming cpu on os28, preventing suspend. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-4 lack of keyboard/mouse input - still happening?
daniel wrote: > Hi, > > In recent months we have seen some issues with the XO-4 keyboard and > mouse, where the system would boot (or resume from suspend?) and not > respond to keyboard/mouse input (and/or respond to keyboard input in a > very lagged manner). > > This problem may have been accompanied with kernel messages like: > psmouse serio1: Failed to deactivate mouse on olpc_touchpad/serio0 > psmouse serio1: Failed to enable mouse on olpc_touchpad/serio0 > psmouse serio1: sentelic: Unable get OPC state. > atkbd serio0: keyboard reset failed on olpc_keyboard/serio0 > > and corresponds to tickets: > #12101 cl4: touchpad missing after reboot > #12370 No mouse interaction possible after bootup > > Has anyone seen these problems or the possibly-related kernel messages > on recent builds such as 13.1.0 build 27 with the latest firmware? > > I previously saw it fairly regularly on my two XO-4s but I can't > recall seeing it recently. Additionally, we would sometimes get those > kernel messages during shutdown, and those messages have now gone > away, so I'm wondering if we have fixed these issues while working on > related things. i wish i could point to an EC or kernel fix that i'm aware of that would have made it go away, but i can't. i agree that i don't recall seeing it lately. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Hacking onto the "appearing" and "hiding" of OSK
ajay wrote:
> On Mon, Jan 28, 2013 at 11:01 PM, Paul Fox wrote:
>
> > ajay wrote:
> > > Hi all.
> > >
> > > A simple solution was found :)
> > >
> > > I hacked the "KP_Prior" and "KP_Next" keys, and now they are used for
> > > making-window-smaller and restoring-original-window-size respectively :)
> >
> > so sugar takes over those keys? aren't those keys used by activities?
> > they're certainly useful in a terminal -- page up and page down.
> >
>
> Hmm.. Well a simple "grepping" showed that the "Read" activity is the only
> activity that explicitly makes use of the "KP_Home" and "KP_End" keys; but
> none seemed to make use of "KP_Prior" and "KP_Next".
certainly not my call, but stealing keys which have always been
intended for activities to use seems like it shouldn't be done
lightly.
(and why do you need two keys? isn't the operation a toggle?)
paul
>
>
>
> > paul
> >
> > >
> > > All thanks to
> > >* /usr/share/X11/xkb/keycodes/evdev
> > >* sugar/src/jarabe/view/keyhandler.py
> > >
> > >
> > >
> > > Just one thing I noticed when I tried to have the above keys take
> > effect
> > > ONLY in ebook-mode (via the "evtest --query" test), that when I ran this
> > > again and again via the "suprocess" module, the XO-4 behaved very
> > > erratically. However, when I made the keys take effect irrespective of
> > the
> > > test of ebook-mode, things worked cool. However, I will keep on looking
> > > into the reason.
> > >
> > >
> > > Thanks a ton to all :)
> > >
> > >
> > > On Thu, Jan 24, 2013 at 10:45 PM, Paul Fox wrote:
> > >
> > > > gonzalo wrote:
> > > > > Write does not know what is the ebook switch state, that logic is
> > in the
> > > > > osk.
> > > > >
> > > > > Looking in the wiki and sugar code, I could not find information
> > about
> > > > how
> > > > > read the switch,
> > > > > but in ticket http://dev.laptop.org/ticket/12326 found this:
> > > > >
> > > > > If you do:
> > > > >
> > > > > evtest --query /dev/input/event4 EV_SW SW_TABLET_MODE; echo $?
> > > > >
> > > > >
> > > > > If the xo is in ebook mode returns 10, if not, returns 0.
> > > > >
> > > > > There are any official doc about the switches I am missing? There
> > are a
> > > > way
> > > > > to catch a event when the switch is activated, using dbus or
> > something
> > > > > similar?
> > > >
> > > > if you open the device and read it, you'll get a stream of "struct
> > > > input_event" structures (/usr/include/linux/input.h) representing
> > > > opening and closing of the SW_TABLET_MODE switch. here's a C code
> > > > snippet from olpc-switchd (part of powerd):
> > > >
> > > > void ebook_event()
> > > > {
> > > > struct input_event ev[1];
> > > >
> > > > if (read(ebk_fd, ev, sizeof(ev)) != sizeof(ev))
> > > > die("bad read from ebook switch");
> > > >
> > > > dbg(3, "ebk: ev sec %d usec %d type %d code %d value %d",
> > > > ev->time.tv_sec, ev->time.tv_usec,
> > > > ev->type, ev->code, ev->value);
> > > >
> > > > if (ev->type == EV_SW && ev->code == SW_TABLET_MODE) {
> > > > if (ev->value)
> > > > send_event("ebookclose", round_secs(ev), ebk_device);
> > > > else
> > > > send_event("ebookopen", round_secs(ev), ebk_device);
> > > > }
> > > > }
> > > >
> > > >
> > > > perhaps there's an evdev to dbus gateway of some sort, but i don't
> > know
> > > > about it, if so.
> > > >
> > > > the "evtest" commandline example, above, uses an ioctl
Re: [Sugar-devel] Hacking onto the "appearing" and "hiding" of OSK
ajay wrote:
> Hi all.
>
> A simple solution was found :)
>
> I hacked the "KP_Prior" and "KP_Next" keys, and now they are used for
> making-window-smaller and restoring-original-window-size respectively :)
so sugar takes over those keys? aren't those keys used by activities?
they're certainly useful in a terminal -- page up and page down.
paul
>
> All thanks to
>* /usr/share/X11/xkb/keycodes/evdev
>* sugar/src/jarabe/view/keyhandler.py
>
>
>
> Just one thing I noticed when I tried to have the above keys take effect
> ONLY in ebook-mode (via the "evtest --query" test), that when I ran this
> again and again via the "suprocess" module, the XO-4 behaved very
> erratically. However, when I made the keys take effect irrespective of the
> test of ebook-mode, things worked cool. However, I will keep on looking
> into the reason.
>
>
> Thanks a ton to all :)
>
>
> On Thu, Jan 24, 2013 at 10:45 PM, Paul Fox wrote:
>
> > gonzalo wrote:
> > > Write does not know what is the ebook switch state, that logic is in the
> > > osk.
> > >
> > > Looking in the wiki and sugar code, I could not find information about
> > how
> > > read the switch,
> > > but in ticket http://dev.laptop.org/ticket/12326 found this:
> > >
> > > If you do:
> > >
> > > evtest --query /dev/input/event4 EV_SW SW_TABLET_MODE; echo $?
> > >
> > >
> > > If the xo is in ebook mode returns 10, if not, returns 0.
> > >
> > > There are any official doc about the switches I am missing? There are a
> > way
> > > to catch a event when the switch is activated, using dbus or something
> > > similar?
> >
> > if you open the device and read it, you'll get a stream of "struct
> > input_event" structures (/usr/include/linux/input.h) representing
> > opening and closing of the SW_TABLET_MODE switch. here's a C code
> > snippet from olpc-switchd (part of powerd):
> >
> > void ebook_event()
> > {
> > struct input_event ev[1];
> >
> > if (read(ebk_fd, ev, sizeof(ev)) != sizeof(ev))
> > die("bad read from ebook switch");
> >
> > dbg(3, "ebk: ev sec %d usec %d type %d code %d value %d",
> > ev->time.tv_sec, ev->time.tv_usec,
> > ev->type, ev->code, ev->value);
> >
> > if (ev->type == EV_SW && ev->code == SW_TABLET_MODE) {
> > if (ev->value)
> > send_event("ebookclose", round_secs(ev), ebk_device);
> > else
> > send_event("ebookopen", round_secs(ev), ebk_device);
> > }
> > }
> >
> >
> > perhaps there's an evdev to dbus gateway of some sort, but i don't know
> > about it, if so.
> >
> > the "evtest" commandline example, above, uses an ioctl on the input
> > device to determine current state. here's snippet from the evtest source:
> > (full source: git://anongit.freedesktop.org/evtest)
> >
> > static int query_device(const char *device, const struct query_mode
> > *query_mode>
> > {
> > int fd;
> > int r;
> > unsigned long state[NBITS(query_mode->max)];
> >
> > fd = open(device, O_RDONLY);
> > if (fd < 0) {
> > perror("open");
> > return EXIT_FAILURE;
> > }
> > memset(state, 0, sizeof(state));
> > r = ioctl(fd, query_mode->rq, state);
> > close(fd);
> >
> > if (r == -1) {
> > perror("ioctl");
> > return EXIT_FAILURE;
> > }
> >
> > if (test_bit(keycode, state))
> > return 10; /* different from EXIT_FAILURE */
> > else
> > return 0;
> > }
> >
> >
> >
> > paul
> >
> >
> > >
> > > Gonzalo
> > >
> > >
> > > On Thu, Jan 24, 2013 at 12:16 PM, Martin Langhoff <
> > martin.langh...@gmail.com
> > > > wrote:
> > >
> > > > On Thu, Jan 24, 2013 at 10:13 AM, Paul Fox wrote:
Re: [Sugar-devel] Hacking onto the "appearing" and "hiding" of OSK
gonzalo wrote:
> Write does not know what is the ebook switch state, that logic is in the
> osk.
>
> Looking in the wiki and sugar code, I could not find information about how
> read the switch,
> but in ticket http://dev.laptop.org/ticket/12326 found this:
>
> If you do:
>
> evtest --query /dev/input/event4 EV_SW SW_TABLET_MODE; echo $?
>
>
> If the xo is in ebook mode returns 10, if not, returns 0.
>
> There are any official doc about the switches I am missing? There are a way
> to catch a event when the switch is activated, using dbus or something
> similar?
if you open the device and read it, you'll get a stream of "struct
input_event" structures (/usr/include/linux/input.h) representing
opening and closing of the SW_TABLET_MODE switch. here's a C code
snippet from olpc-switchd (part of powerd):
void ebook_event()
{
struct input_event ev[1];
if (read(ebk_fd, ev, sizeof(ev)) != sizeof(ev))
die("bad read from ebook switch");
dbg(3, "ebk: ev sec %d usec %d type %d code %d value %d",
ev->time.tv_sec, ev->time.tv_usec,
ev->type, ev->code, ev->value);
if (ev->type == EV_SW && ev->code == SW_TABLET_MODE) {
if (ev->value)
send_event("ebookclose", round_secs(ev), ebk_device);
else
send_event("ebookopen", round_secs(ev), ebk_device);
}
}
perhaps there's an evdev to dbus gateway of some sort, but i don't know
about it, if so.
the "evtest" commandline example, above, uses an ioctl on the input
device to determine current state. here's snippet from the evtest source:
(full source: git://anongit.freedesktop.org/evtest)
static int query_device(const char *device, const struct query_mode
*query_mode>
{
int fd;
int r;
unsigned long state[NBITS(query_mode->max)];
fd = open(device, O_RDONLY);
if (fd < 0) {
perror("open");
return EXIT_FAILURE;
}
memset(state, 0, sizeof(state));
r = ioctl(fd, query_mode->rq, state);
close(fd);
if (r == -1) {
perror("ioctl");
return EXIT_FAILURE;
}
if (test_bit(keycode, state))
return 10; /* different from EXIT_FAILURE */
else
return 0;
}
paul
>
> Gonzalo
>
>
> On Thu, Jan 24, 2013 at 12:16 PM, Martin Langhoff > wrote:
>
> > On Thu, Jan 24, 2013 at 10:13 AM, Paul Fox wrote:
> > > i believe sugar already has code to detect the two modes, since
> > > that's how it knows whether to present the OSK or not.
> >
> > Yep. Ajay, I think Write shows you the way :-)
> >
> >
> >
> >
> > m
> > --
> > martin.langh...@gmail.com
> > mar...@laptop.org -- Software Architect - OLPC
> > - ask interesting questions
> > - don't get distracted with shiny stuff - working code first
> > - http://wiki.laptop.org/go/User:Martinlanghoff
> >
=-
paul fox, p...@laptop.org
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: 13.1.0 release candidate 4 (build 24) released
jerry wrote: > On Thu, 2013-01-24 at 10:19 -0500, Paul Fox wrote: > > jerry wrote: > > > On Fri, 2013-01-11 at 21:31 +, Daniel Drake wrote: > > > > Hi, > > > > > > > > We're pleased to announce the next release candidate of our new 13.1.0 > > > > software release. > > > > > > > Please review the "Known problems" section of the release notes. Some > > > > documented issues are carried over from previous releases, but others > > > > are new and are things that we will aim to fix in the few weeks before > > > > release. > > > > > > > > IMPORTANT: New XO-4 firmware Q7B11 breaks automatic upgrade for > > > > touchscreen firmware versions before 0.0.0.10 on C1 models. After > > > > reflashing to Q7B11 from an earlier version, you must (just this once) > > > > manually upgrade with > > > > > > > > ok update-nn-flash > > > > > > > > Otherwise the touchscreen will not work. > > > > > > > > > > I have questions with this, should everybody be doing this procedure to > > > all updates from a release prior to 23 to a release 24 or later that > > > would install Q7B11 or later? > > > > from 23 or prior to 24 or later, then yes, you should do the manual > > update. > > > > the only exception is if you have a B1 with a clear lightguide, and > > you care a lot about precise linearity of touchscreen response. in > > that case, you should stick with firmware 0.0.0.4. > > > > and remember, if you make a mistake, you can always go back to 0.0.0.4 > > by downloading it and doing a manual reflash. > > > > > > > > ie: image 13.1.0-21 is installed then you flash/olpc-update to 13.1.0-26 > > > should you be doing this? Does this apply to all B1,C1,C2 models and > > > what versions should be installed with Q7B11 for these models? > > > > > > from a machine with Q7B11: > > > > > > kernel: zforce: found zForce firmware 0.0.0.4 > > > kernel: zforce: running in multitouch mode > > > > > > What should syslog be recording for the zforce driver for the B1,C1,C2? > > > > > > Just trying to clear up what needs to be done going forward. > > > > B1 machines with clear lightguides should probably be left alone, as > > noted above. > > > > This might sound like a dumb question but do all B1s have clear > lightguides? If not, how can one tell them apart? not dumb at all. the lightguide we're talking about is the plastic piece sandwiched between the screen and the white plastic bezel that surrounds the screen. if you look at the thin edge that's visible, it will either be dark, basically black, or transparent -- you'll be able to see bright reflections from surfaces within it. most B1 machines have the clear variety, but some number were modified to have the dark lightguide (which is actually a very dark red) before being sent out to users. paul > > all other machines should (currently) have 0.0.0.10. and, once they > > have 0.0.0.10, C1 and C2 machines will automatically upgrade in the > > future. i think B1 machines will continue needing manual upgrades. > > > > Think this information might need to be part of the release notes. > > Jerry =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 13.1.0 release candidate 4 (build 24) released
jerry wrote: > On Fri, 2013-01-11 at 21:31 +, Daniel Drake wrote: > > Hi, > > > > We're pleased to announce the next release candidate of our new 13.1.0 > > software release. > > > Please review the "Known problems" section of the release notes. Some > > documented issues are carried over from previous releases, but others > > are new and are things that we will aim to fix in the few weeks before > > release. > > > > IMPORTANT: New XO-4 firmware Q7B11 breaks automatic upgrade for > > touchscreen firmware versions before 0.0.0.10 on C1 models. After > > reflashing to Q7B11 from an earlier version, you must (just this once) > > manually upgrade with > > > > ok update-nn-flash > > > > Otherwise the touchscreen will not work. > > > > I have questions with this, should everybody be doing this procedure to > all updates from a release prior to 23 to a release 24 or later that > would install Q7B11 or later? from 23 or prior to 24 or later, then yes, you should do the manual update. the only exception is if you have a B1 with a clear lightguide, and you care a lot about precise linearity of touchscreen response. in that case, you should stick with firmware 0.0.0.4. and remember, if you make a mistake, you can always go back to 0.0.0.4 by downloading it and doing a manual reflash. > > ie: image 13.1.0-21 is installed then you flash/olpc-update to 13.1.0-26 > should you be doing this? Does this apply to all B1,C1,C2 models and > what versions should be installed with Q7B11 for these models? > > from a machine with Q7B11: > > kernel: zforce: found zForce firmware 0.0.0.4 > kernel: zforce: running in multitouch mode > > What should syslog be recording for the zforce driver for the B1,C1,C2? > > Just trying to clear up what needs to be done going forward. B1 machines with clear lightguides should probably be left alone, as noted above. all other machines should (currently) have 0.0.0.10. and, once they have 0.0.0.10, C1 and C2 machines will automatically upgrade in the future. i think B1 machines will continue needing manual upgrades. paul > > Jerry > > > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Hacking onto the "appearing" and "hiding" of OSK
jerry wrote: > On 24 January 2013 08:11, Ajay Garg wrote: > > > > > > > On Thu, Jan 24, 2013 at 7:37 PM, Ajay Garg wrote: > > > >> > >> > >> On Thu, Jan 24, 2013 at 7:36 PM, Gonzalo Odiard wrote: > >> > >>> > >>> > >>>> So, it seems that just hacking onto the game-key won't help :( > >>>> > >>> > >>> No. Will not work, because the osk will appear if you touch over a input > >>> widget. > >>> The game keys are not the expected way to show the osk. > >>> > >> > >> Hmm.. which brings us back to square one :( > >> > > > > > > Let's try another way :P > > > > Is there a way, so that we may know whether we are in ebook-mode, or > > normal-mode? > > > > > Yes, there is a ebook switch event: i believe sugar already has code to detect the two modes, since that's how it knows whether to present the OSK or not. paul > > Jan 24 01:14:28 xo-1e-89-0d kernel: OLPC XO-1.75 lid and ebook switches > Jan 24 01:14:28 xo-1e-89-0d kernel: input: OLPC lid switch as > /devices/virtual/input/input3 > Jan 24 01:14:28 xo-1e-89-0d kernel: input: OLPC ebook switch as > /devices/virtual/input/input4 > > Jan 24 01:14:49 xo-1e-89-0d olpc-kbdshim-udev[484]: olpc-kbdshim-udev: > starting olpc-kbdshim-udev version 29 > Jan 24 01:14:49 xo-1e-89-0d olpc-kbdshim-udev[484]: olpc-kbdshim-udev: fd > 4: found touchscreen (zForce touchscreen) /dev/input/event8 (18:00:00) > Jan 24 01:14:49 xo-1e-89-0d olpc-kbdshim-udev[484]: olpc-kbdshim-udev: fd > 6: found keyboard (AT Translated Set 2 keyboard) /dev/input/event5 > (11:01:01) > Jan 24 01:14:49 xo-1e-89-0d olpc-kbdshim-udev[484]: olpc-kbdshim-udev: fd > 7: found touchpad (FSPPS/2 Sentelic FingerSensingPad) /dev/input/event9 > (11:02:0f) > > Jan 24 01:14:49 xo-1e-89-0d olpc-kbdshim-udev[484]: olpc-kbdshim-udev: fd > 8: found ebook switch > > Jerry > part 2 text/plain 153 > ___ > Sugar-devel mailing list > sugar-de...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] [IAEP] XO-4 Questions After Viewing CES video
bert wrote: > > On 11.01.2013, at 05:22, Paul Fox wrote: > > > bert wrote: > >> > >> On 10.01.2013, at 21:19, John Watlington wrote: > >> > >>>> More recent versions of the XO-4 touchscreen firmware should allow > >>>> a many-finger keyboard. I hope someone with an XO-4 is working > >>>> on a demo! > >> > >> Oh, I must have missed the announcement. How is the raw touch data > >> exposed? > > > > sorry! a few releases of the touchscreen firmware ago, the max number > > of touches quietly went from 2 to 4. full positioning is still only > > accurate with just 2, but the touchscreen will attempt to keep track > > of 4 if they're separable in at least one axis. so there's nothing > > special for a program to do (i.e., no raw data to fetch). > > > > i haven't experimented with the feature much, but gonzalo has the > > beginnings of a nice little piano playing activity floating around > > somewhere. > > Ah, it does work indeed, see screenshot at > > http://activities.sugarlabs.org/en-US/sugar/addon/4611 for well-placed touches only. :-) (i'm actually a little surprised that that screenshot worked.) paul > > Thanks! > > - Bert - > =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [support-gang] [IAEP] XO-4 Questions After Viewing CES video
bert wrote: > > On 10.01.2013, at 21:19, John Watlington wrote: > > >> More recent versions of the XO-4 touchscreen firmware should allow > >> a many-finger keyboard. I hope someone with an XO-4 is working > >> on a demo! > > Oh, I must have missed the announcement. How is the raw touch data > exposed? sorry! a few releases of the touchscreen firmware ago, the max number of touches quietly went from 2 to 4. full positioning is still only accurate with just 2, but the touchscreen will attempt to keep track of 4 if they're separable in at least one axis. so there's nothing special for a program to do (i.e., no raw data to fetch). i haven't experimented with the feature much, but gonzalo has the beginnings of a nice little piano playing activity floating around somewhere. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 13.1.0 release candidate 2 (build 21) released
jerry wrote: > On Wed, 2013-01-02 at 14:56 -0500, Paul Fox wrote: > > jerry wrote: > > > On Sun, 2012-12-30 at 12:42 +, Daniel Drake wrote: > > > > Hi, > > > > > > > > We're pleased to announce the next release candidate of our new 13.1.0 > > > > software release. > > > < snip > > > > > This build now enables XO-4 idle suspend by default. This is still a > > > > work in progress, there are still various instabilities which may make > > > > this build feel more unstable than previous ones. You can disable > > > > automatic power management in sugar's Settings panel to restore > > > > previous behaviour. > > > > > > > > > > Once my XO-4s (B1 & C2) enters idle suspend they can not be awakened > > > with any external method I've tried. No response to touch-screen, > > > touch-pad, keyboard, or power-button to trigger a event in powerd. I've > > > > [semi-]reliable suspend/resume on C1/C2 requires new as-yet-unreleased > > EC code. i've not yet had a B1 work well. > > > > Is that cl4-7_0_3_06.img? Would it be helpful to test this code? no. it'll be the next one. stay tuned. paul > > > > also, as you've found, rtcalarm-based resume should be okay, but i > > don't think anything else will wake the system reliably. > > > > Yea that looks to be working well. > > > > set the dim/blank to be 60/120 to speed up testing whether rtcalarm > > > works. What I found interesting is once suspended then using the > > > keyboard to awaken if you wait for rtcalarm to wake the XO the event > > > will be shown as 'keypress' while tracing powerd. > > > > yes, a kernel issue was causing most wakeups to be ascribed to > > "keypress". should be fixed in the next build. > > > > Good to know, thanks. > > Jerry > =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 13.1.0 release candidate 2 (build 21) released
gonzalo wrote: > > [semi-]reliable suspend/resume on C1/C2 requires new as-yet-unreleased > > EC code. i've not yet had a B1 work well. > > > Is the wifi interface broken known too or need a ticket filled about that? it's always better to file a ticket than not. which wifi failure are you referring to? it's hard to keep track. ;-) paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 13.1.0 release candidate 2 (build 21) released
jerry wrote: > On Sun, 2012-12-30 at 12:42 +, Daniel Drake wrote: > > Hi, > > > > We're pleased to announce the next release candidate of our new 13.1.0 > > software release. > < snip > > > This build now enables XO-4 idle suspend by default. This is still a > > work in progress, there are still various instabilities which may make > > this build feel more unstable than previous ones. You can disable > > automatic power management in sugar's Settings panel to restore > > previous behaviour. > > > > Once my XO-4s (B1 & C2) enters idle suspend they can not be awakened > with any external method I've tried. No response to touch-screen, > touch-pad, keyboard, or power-button to trigger a event in powerd. I've [semi-]reliable suspend/resume on C1/C2 requires new as-yet-unreleased EC code. i've not yet had a B1 work well. also, as you've found, rtcalarm-based resume should be okay, but i don't think anything else will wake the system reliably. > set the dim/blank to be 60/120 to speed up testing whether rtcalarm > works. What I found interesting is once suspended then using the > keyboard to awaken if you wait for rtcalarm to wake the XO the event > will be shown as 'keypress' while tracing powerd. yes, a kernel issue was causing most wakeups to be ascribed to "keypress". should be fixed in the next build. paul > > Jerry > > > > > > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [TRANSIENT] Peer XOs NOT shown in Neighborhood view when Power Management is enabled
samuel wrote: > On Tue, Jan 1, 2013 at 7:34 PM, Jerry Vonau wrote: > > > On Wed, 2012-12-19 at 09:48 -0500, Martin Langhoff wrote: > > > On Wed, Dec 19, 2012 at 5:14 AM, Jerry Vonau wrote: > > > > Think I found the problem, in powerd we're setting WOL based on this > > > > string: > > > > > > > > if grep -qi ": :14B2" /proc/net/tcp > > > > > > > > but that string is not present in /proc/net/tcp so WOL is not set > > > > according to ethtool, but that string can be found in /proc/net/tcp6 > > > > > > > > avahi is bound to tcp6 when viewed with 'netstat -nat' > > > > > > > > This is reproducible in 12.1.0 and 13.1.0 > > > > > > Arghhh. Ouch. > > > > > > Does it behave better with: > > > > > > if grep -qi ": :14B2" /proc/net/tcp* > > > > This does not work because IPv6 addresses are longer (and therefore have > more octets). > > The variant I came up with (if we want to support both v4 and v6 listeners) > is > > if grep -qiE ": +:14B2" /proc/net/tcp? > > Simply removing the ": " check on its own might be sufficient for our > purposes but could falsely return true in a few cases. > > If IPv4 backward compatibility on the listener check is not a concern, then > you should just match on the longer string of zeros:14B6 in /proc/net/tcp6 > and not check both files for speed. why would ipv4 backward compatibility not be a concern? paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] Locations for bitfrost src-rpm packages
ajay wrote: > Hi all. > > Where can I find the corresponding source-rpm packages, for :: > > * > http://rpmdropbox.laptop.org/f18/bitfrost-1.0.18-1.fc18.armv7hl.rpm > AND > * > http://rpmdropbox.laptop.org/f18/bitfrost-sugar-1.0.18-1.fc18.armv7hl.rpm > could it be here? https://dev.laptop.org/git/projects/bitfrost/ paul > > > > Thanks in advance !! :) > > > > Regards, > > Ajay Garg > Dextrose Developer > Activity Central: http://activitycentral.com > part 2 text/plain 153 > ___ > Sugar-devel mailing list > sugar-de...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: XO-4 WOL and powerd
jerry wrote: > Hi All, > > I can't seem to retrieve what the 8787 wifi card is set to for WOL. All > that is returned is link detected with ethtool. Can't tell from here but WOL isn't implemented in the 8787 driver yet. > is wol even getting set? From here it looks like sleeping is being > prevented from a quick look at powerd, can someone confirm that sleeping > is in fact disabled. powerd currently won't let the system suspend, since suspend doesn't yet work reliably enough. search for "prevent_sleep", if you want to reenable it. (but be prepared for lots of hangs and crashes.) paul > > Jerry > > =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 13.1.0 development build 19 released
manuel wrote: > On Sun, Dec 16, 2012 at 1:40 PM, Daniel Drake wrote: > > XO-4 now has HDMI support in Linux (#12350). Other kernel fixes: > > Is there some "user guide" about this? > > I mean, what I need to know to make this work? I have a 32'' LED TV > and a 23'' LCD Monitor that I would like to try with the XO-4 HDMI > output. Both, the TV and the monitor have this kind of connector[1]. > > So, should I just need a cable with a mini-HDMI on one side (to be > connected in the XO) and a "common" HDMI connector on the other side > (to be connected into the TV or Monitor)? i believe the connector is "micro-HDMI", i.e., type D: http://en.wikipedia.org/wiki/HDMI#Connectors your assumptions are correct -- hdmi should be auto-detecting under linux. in OFW, you can type "720p" or "1080p" to enable hdmi output. remember that as discussed yesterday on the devel@ list, there are some caveats regarding HDMI on B1 units. paul > > Thanks! > > [1] > http://en.wikipedia.org/wiki/File:HDMI_connector-male_2_sharp_PNr%C2%B00059.jpg > > -- > Kaufmann Manuel > -- http://mkaufmann.com.ar > _______ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 13.1.0 development build 19 released
anna wrote: > On Sun, Dec 16, 2012 at 10:40 AM, Daniel Drake wrote: > > > > > XO-4 now has HDMI support in Linux (#12350). > > > > Once of the perks of having an AV contractor in the house is that it wasn't > hard to dig up the proper HDMI adaptor. Still mostly the same issue as > build 18 as noted in #12350, but under build 19 there's no HDMI output at > all after entering boot instead of the TV hanging on the OFW screen while > the XO boots. > > I tried both 720p and 1080p. i can't tell if you're not getting signal at all, or just in OFW. if the former, and you're using a B1 unit (and i assume you are), then there's a good chance that the cable isn't making contact properly. the jack is mounted just a little too far back from the edge of the motherboard, and so too far from the outside of the laptop. it's only off by a millimeter or so -- if you don't mind trimming just a bit of the rubber encapsulation from around the metal part of the micro-hdmi plug, it should help. (fixed on C1 units) if the latter, and you have signal in OFW but not linux, be sure your upgrade to q7b09 was successful. linux hdmi won't work without it. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] XO-hang on 1.75-touch
ajay wrote: > > Please find attached the logs. > probably better to record the data associated with bug reports in a trac ticket. paul > > > > > > Gonzalo > > > > ___ > > Devel mailing list > > Devel@lists.laptop.org > > http://lists.laptop.org/listinfo/devel > > > > > > > Regards, > > Ajay Garg > Dextrose Developer > Activity Central: http://activitycentral.com > part 5 text/plain 153 > ___ > Sugar-devel mailing list > sugar-de...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: 13.1.0 development build 12 released
fors...@ozonline.com.au wrote: > Thanks > > Can you please fix my edit to the wiki > I am totally confused, all I know is that all my olpc-updates have > been with 2 power sources and I don't remember ever seeing it do a > OFW upgrade to be clear, olpc-updates occur while the machine is running. no firmware update will occur then. firmware updates happen when the machine is booting, and that's when two power sources are required. paul =----- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Neonode low-level access
gonzalo wrote: > Should be a a way to get this info, if not I don't know how this demo can > work: > > http://www.youtube.com/watch?v=b-C42PGoDqY > > I am more than interested to get the piano working i'll push harder on the vendor for this. paul > > Gonzalo > > On Thu, Nov 8, 2012 at 12:47 PM, Gary Martin > wrote: > > > Hi Bert, > > > > On 8 Nov 2012, at 14:38, Bert Freudenberg wrote: > > > > > How can I get at low-level data from the XO-4's touch screen in Linux? > > I'm thinking of the actual light levels of all the sensors around the > > edges. > > > > Unfortunately not at the moment, as far as I'm aware of (happy to be > > proven wrong). It was on the feature design list at an early stage of the > > dev cycle (so that we could implement things like a multi-touch piano) but > > time went to the primary use case and no driver work was done exposing this > > data, as far as I can tell. There are some parameters exposed under > > /sys/module/zforce/parameters, but nothing like the light level data. > > Perhaps something to push for in the next cycle? > > > > Regards, > > --Gary > > > > > Certain apps could benefit from this - e.g. many of Neonode's own > > impressive demos could not be implemented using only the X11 events I get > > in Sugar. > > > > > > - Bert - > > > > > > ___ > > > 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 > > > part 2 text/plain 129 > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Neonode low-level access
bert wrote: > How can I get at low-level data from the XO-4's touch screen in > Linux? I'm thinking of the actual light levels of all the sensors > around the edges. access to more data is limited. the only events we get correlate pretty directly to the X events you already see -- i.e., motion and touch. it's possible to request other data, and i think all of those requests can be issued from either OFW or linux. for OFW, see http://wiki.laptop.org/go/XO_4_Touch_Testing for the watch-fss and watch-fll commands. i think there are more as well, but you're mainly interested in linux access. for linux, see the sysfs files under /sys/kernel/debug/zforce/. there are also a few tuneables under /sys/modules/zforce/parameters. most are self-explanatory, or are quickly explained by a glance at the driver. the driver's header file contains pretty much all the original information from the docs we got: http://dev.laptop.org/git/olpc-kernel/tree/drivers/input/touchscreen/zforce.h?h=arm-3.5 > > Certain apps could benefit from this - e.g. many of Neonode's own > impressive demos could not be implemented using only the X11 events > I get in Sugar. can you elaborate? paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: q7b04
there's another copy of the firmware in the root filesystem that's being checked for auto-updating, and it's out-of-date, and we changed the format. at the ok prompt, run: ok delete int:\boot\bootfw.zip ok delete int:\boot\bootfw4.zip only one of those two commands will be successful -- i believe the second one. (but since i can't remember for sure the name of the offending file, i'm suggesting you run both. :-) paul bert wrote: > Hi, > > I just flashed my 4B1 to q7b04 (from q7b01), it seemed to finish normally, > rebooted, now it's bricked - "Invalid Firmware image, powering off in 30 > secs". > > Any idea what could be wrong? The machine seemed to work fine before. > > Also, I gave away my serial adapter, can only get it back after the weekend, > is there another way to get it working again? > > - Bert - > > > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] 13.1.0 development build 8 released
simon wrote: > > Another show stopper for the XO-4 build is that all space is used. First > thing I had to do was to remove Wikipedia-* to get some space, oh well a > good candidate to test the no space left alert :) The 1.75 build has a > bit of space left. is this perhaps another failure of the rootfs to resize properly on first boot? paul =----- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Techteam] 13.1.0 devel build 5 released, for the XO-1, XO-1.5, XO-1.75 and XO-4
martin wrote:
> On Sun, Oct 7, 2012 at 6:56 PM, Peter Robinson wrote:
> > Not yet, all the layouts are in and gtk2 works now
>
> Installed, quick test. You're right, the ebook trigger isn't
> happening. And I cannot type with it -- Write won't show input from
> the OSK, home view search box won't show input from OSK.
>
> The touchscreen scale_{x,y} defaults are killing me. They make the UI
> _very_ awkward to use -- I average 2.5 touches before I can hit a
> moderately large button ("next", or the "stop" icon). This is because
> the offset the driver applies shifts in every spot of the screen, it's
> a devilish thing.
>
> Paul, can we crank those defaults way down? Or add a dampening / ramp
> up effect to the offset that is flat in most of the screen, but
> quickly ramps up near edges? (If you don't believe me, install OS5 and
> use Sugar with the touchscreen for a while).
as i said the other day, the kernel driver should either do no scaling
by default, or it should make every pixel on the screen touchable with
a "standard" pointing instrument (i.e., a stylus). the latter is what
it does now -- perhaps exaggerated. but any other midway decision
between those extremes (which i agree is probably the right thing)
constitutes policy, and therefore belongs at user level.
which is to say, i think the correct defaults belong in olpc-utils,
along with the countless other XO useablility tweaks that are already
there.
(once that change is firmly in place, i'll probably revert the driver to
default to no scaling at all.)
paul
>
> thanks!
>
>
>
> m
> --
> mar...@laptop.org -- Software Architect - OLPC
> - ask interesting questions
> - don't get distracted with shiny stuff - working code first
> - http://wiki.laptop.org/go/User:Martinlanghoff
=-
paul fox, p...@laptop.org
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
OLPC network service outage
sorry for the (very) short notice. OLPC's public facing servers, including dev.laptop.org, activation services, and laptop.org email, will be affected by the same outage bernie describes below. we're not reconfiguring anything, besides moving some machines physically, so hopefully the outage will be kept to a minimum. paul bernie wrote: > Date:Thu, 20 Sep 2012 00:26:10 -0400 > To: hos...@sugarlabs.org > From:Bernie Innocenti > Subject: [Sugar-devel] Sugar Labs service outage: Thu, Sep 20 9:30-12:30 EDT > > Tomorrow, Thursday 20 Sep 2012, between 9:30 and 12:30 eastern time, the > Media Lab sysadmins will reconfigure the rack in room E15-243. > > During the maintenance work, the following services hosted on > treehouse.sugarlabs.org may become temporarily unavailable: > > - git.sugarlabsa.org and all related services > - chat.sugarlabs.org > - jabber.sugarlabs.org > - meeting.sugarlabs.org > - network.sugarlabs.org > - obs.sugarlabs.org > - rt.sugarlabs.org > - schooltool.sugarlabs.org > - ns1.sugarlabs.org (primary nameserver for multiple domains) > - Various services related to ole.org > - Various services related to paraguayeduca.org > - Various services related to treehouse.su > - Others I might have missed > > We'll use this opportunity to rack our two new servers and prepare them > for production. > > -- > Bernie Innocenti > Sugar Labs Infrastructure Team > http://wiki.sugarlabs.org/go/Infrastructure_Team > > ___ > Sugar-devel mailing list > sugar-de...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Completely disable buildt-in WLAN
mikus wrote: > In 11.3.0 there still was file /sys/power/wlan-enabled, whose content if > set to '0' was supposed to disable wireless. > > Has that function gone the way of the dodo ? > it may be there on XO-1, but it's never been there on 1.5 or 1.75. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Completely disable buildt-in WLAN
kevin wrote:
> Folks:
>
> Is there a quick and dirty line I can maybe just put into a boot-time file
> that will totally disable the internal WLAN card on the XO 1, 1.5 and 1.75
> every time I boot until I manually remove that line? I dont want to
keeping the module from being loaded should do it. i think that
adding a line to /etc/modprobe.d/blacklist.conf that says:
blacklist libertas
will do.
there's some chance that (i can't remember) that libertas will be loaded
from the initrd, in which case you'll also need to do a
modprobe -r libertas_sdio
or
modprobe -r libertas_usb (on XO-1)
from somewhere like /etc/rc.local. i say "like" rc.local, because
that file doesn't exist in recent builds, because modern linux
designers have little respect at all for the great, and useful,
traditions of the past.
paul
"Those who do not understand Unix are condemned to reinvent it, poorly."
-- Henry Spencer
=-
paul fox, p...@laptop.org
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
Re: OLPC build creation failed
martin wrote: > > TBH, I have never seen any OS image builder / composer in the Linux > world that works cross platform. which isn't to say that we don't make extensive use of cross-compiling in development. i think all of our dev kernels are cross-compiled, and probably most of us use cross-tools wherever we can, if only to avoid the jump to a different build machine. coming from the embedded world (even embedded linux), where cross-development is a way of life, i was surprised how reliant distro development is on native builds. paul =----- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Trac slowness diagnosis
shep was just filing a ticket, and had no way of finding someone's trac nick, based on their real name. that reminded me that we could still use a page of some sort that lets one do that lookup. of course i have no idea how difficult that would be. even a link to a ticket whose description contained a current list would be a start. ;-) paul daniel wrote: > On Thu, Mar 29, 2012 at 4:30 PM, James Cameron wrote: > > I would prefer to switch now. > > Chris voted for this as well so I went ahead and made the change. Can > easily be changed back if it presents problems. > > Loading a tickets locally on the server went from taking 2.8s to now > taking 1.3s. > > Daniel > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Migrating XO-1.75 to device tree - upgrade considerations
daniel wrote: > Hi, > > We want to follow the upstream direction of dynamically driving > hardware detection by the firmware-provided device tree, rather than > hardcoding a board file into the kernel. > > We have in-development kernel and firmware versions that make this > move, but we need to do this in a way that doesn't disrupt existing > users on upgrade. > > These are the possible scenarios: > new = whats currently in development, DT > old = whats currently shipped as stable, non-DT > > 1. New kernel, new firmware: this is the easy case - in this scenario > we upgrade both components and we know that they work together since > we wrote tham that way. > > 2. New firmware, old kernel: This currently will not boot, because the > new firmware boots with a new /chosen/bootpath value which is not > recognised by the initramfs shipped with the old kernel. > However, it is not clear that we do need to support this case: the > requirement of running a new firmware on top of an old software base this is the case someone will be in if they install a new release, then re-install an old release. perhaps not something universally done, but is it really that "uncommon"? paul > is not common. And the only option we'd have of fixing it is putting > nasty hacks in the firmware, so if the need does arise in future, we > could produce new firmware versions with the required hacks included. > > 3. Old firmware, new kernel: This is a case we definitely have to care > about. When system updates are done in the field, it is not guaranteed > that electricity will be available upon the reboot in order to install > the updated firmware. So we need to keep this case working. (We know > this is an issue because we've pushed OS updates dependent on new > firmwares before, then we had to revert that upon realising the field > difficulties). > > > So #3 is the only case that needs our special attention at the present > time. The issue here is that the old firmware does not present a > good-enough device tree to the kernel, and the new kernel does not > have the old/static XO-1.75 board definitions. The system won't boot - > some corruption appears at the bottom of the screen, and nothing > appears over serial. > > Ideally we want a solution for this that will hold for the long term - > i.e. its something we'd ship for considerable years to come, not only > just for the next release, to provide a direct upgrade path from the > software releases of today to any release of the future. > > Options include: > 1. Ship the static board file in the kernel, or maybe a cut down version of > it. > I'm not so keen on this - we'd have to keep the non-upstream kernel > code around forever. > > 2. Append the XO-1.75 device tree to the kernel image. > This is my favourite option - while we would have to duplicate the DT > (once in the firmware, once in the kernel), at least they can be > direct copies rather than two different approaches to maintain. > > (can the kernel be made to use this only when a "good DT" is > unavailable? Maybe the definition of "good DT" is hard to define - I'm > referring to the fact that we already ship a DT, but not one that can > be used to get the system on its feet in the absence of a board file) > > 3. Somehow detect this case and print a warning message. > Not so keen on this myself - expressing this in kid-friendly language > seems challenging, then there's internationalisation and so on. > > > Any thoughts or points that I'm missing? > Thanks > Daniel > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: how to default to TOUCHPAD_MODE_PENTABLET?
walter wrote: > On Sun, Jul 29, 2012 at 7:48 AM, Joshua N Pritikin > wrote: > > In our climate, XO-1 pen tablet mode is usually more reliable than mouse > > mode. I want to start in pen pablet mode by default. For Sugar, I got > > this effect by changing the initialization in the frame's touchpad > > control. This only works for Sugar mode though. How do you suggest I > > change the default in Gnome mode? > > You could write a script to mimic the same behavior as in touchpad.py > > Wrtie to '/sys/devices/platform/i8042/serio1/hgpk_mode' > i think you can also set the initial default with a module parameter. something like this: options psmouse hgpk_mode=pentablet in /etc/modprobe.conf (or in some file under /etc/modprobe.d). i don't have an XO-1 handy to try this with, i'm afraid. paul > -walter > > > > > > -- > > Joshua N. Pritikin > > Department of Psychology > > University of Virginia > > Gilmer Hall 102; Charlottesville, VA 22903 > > http://people.virginia.edu/~jnp3bc > > > > ___ > > Devel mailing list > > Devel@lists.laptop.org > > http://lists.laptop.org/listinfo/devel > > > > -- > Walter Bender > Sugar Labs > http://www.sugarlabs.org > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Waking XO-1.75 with RTC
james wrote: > George Hunt wrote (on po...@lists.laptop.org): > > Does anyone have experience waking up an XO via the RTC? Manual > > entries for rtcwake make it sound pretty easy. But there's no real > > substitute for experience. > > rtcwake with a delta time works for me on XO-1.75, you can see a > rather technical example in /runin/runin-sus, but it boils down to > > sudo rtcwake --seconds 60 --mode mem > > I'm not sure if it works with an absolute time ... I doubt it, but > I've not had a moment to try it. We don't have a need for absolute > time wakeup in the OLPC OS builds. i'm not sure i've tried an absolute wakeup time either, but i know of no reason it shouldn't just work. as james implies, the complication for george's scheme is that our power management daemon (/usr/sbin/powerd -- it's a (large) shell script, so feel free to take a look) uses the RTC itself, so it's likely that a user's setting of the RTC will be lost in somewhat short order. i'm sure powerd could help make what you want to do easier than it is now. please let me know if you'd like to continue working on this. there's one more wakeup timer available, implemented as a delta timer in milliseconds (32 bits, or at least 31), that's in the EC. we don't use that during normal operations with powerd, so it might be useful. we've talked about having powerd use that, rather than the RTC, but there are some technical details that prevent that at the moment. paul > You can easily use a delta time sleep until the clock is close to > start of school day. > > The system will wake if there is another reason to; like keyboard, > touchpad, network, or battery state of charge change. This is another > good reason to use a delta time. > > The following is deeper detail than is needed: > > Sridhar Dhanapalan wrote (on po...@lists.laptop.org): > > Interesting idea. My understanding is that the XO-1.75 has two RTCs - > > not sure why. > > One is inside the CPU, but it is unpowered if the system is off. It > is used by rtcwake, and remains powered during suspend. Access to it > is fast. > > The other is external to the CPU and is powered even when the system > is off, using a battery, so that it keeps time. It cannot be used to > wake the system. Access to it is over a serial bus. This is the RTC > maintained by Open Firmware. > > CC: devel@lists.laptop.org 'cause this is a more general question than > power. > > -- > James Cameron > http://quozl.linux.org.au/ > ___ > Devel mailing list > Devel@lists.laptop.org > http://lists.laptop.org/listinfo/devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] How to disable "Authentication Required By Wireless Network" popup in Fedora 17
ajay wrote: > Hi Paul. > > Well, I am doing development on sugar-jhbuild F17. > > So, after I launch sugar-emulator, I wish to have the sugar > network-authentication popup pop up (if at all), and not the gnome one. ah. sugar vs. gnome. now that i understand your problem, i find i can be of no help whatsoever. sorry! paul > > In F14, doing "sudo killall nm-applet" served the purpose. Then, whenever I > launched sugar-emulator, only sugar network-authentication popup popped up > (if at all). No gnome popup popped up then :) > > > Could the same be achieved in F17? > > > Sorry for being unclear the last time around. > > > Thanks and Regards, > Ajay > > On Thu, Jun 21, 2012 at 8:07 AM, Paul Fox wrote: > > > > > ajay wrote: > > > Any ideas ? > > > Please, Please. > > > > i'm confused. when i get that dialog, it's because that network > > is secured, and requires wep or wpa authorization. > > > > what should happen instead? > > > > (or perhaps i'm completely misunderstanding you.) > > > > paul > > > > > > > > Regards, > > > Ajay > > > > > > On Wed, Jun 20, 2012 at 7:00 PM, Ajay Garg > > wrote: > > > > > > > Hi all. > > > > > > > > I am working on sugar on Fedora 17. > > > > However, when I click on a wireless-icon in the 'Neighborhood-View', > > I get > > > > the gnome-popup "Authentication Required By Wireless Network". > > > > > > > > How can I disable this gnome popup? > > > > > > > > On F14, doing "sudo killall nm-applet" is sufficient. > > > > However, on F17, doing "sudo killall nm-applet" isn't sufficient :( > > > > > > > > Any ideas please. I am really finding it irritating, that this > > gnome-popup > > > > is interfering with the sugar experience. > > > > > > > > > > > > Thanks and Regards, > > > > Ajay > > > > > > > part 2 text/plain 153 > > > ___ > > > Sugar-devel mailing list > > > sugar-de...@lists.sugarlabs.org > > > http://lists.sugarlabs.org/listinfo/sugar-devel > > > > =- > > paul fox, p...@laptop.org > > =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Sugar-devel] How to disable "Authentication Required By Wireless Network" popup in Fedora 17
ajay wrote: > Any ideas ? > Please, Please. i'm confused. when i get that dialog, it's because that network is secured, and requires wep or wpa authorization. what should happen instead? (or perhaps i'm completely misunderstanding you.) paul > > Regards, > Ajay > > On Wed, Jun 20, 2012 at 7:00 PM, Ajay Garg wrote: > > > Hi all. > > > > I am working on sugar on Fedora 17. > > However, when I click on a wireless-icon in the 'Neighborhood-View', I get > > the gnome-popup "Authentication Required By Wireless Network". > > > > How can I disable this gnome popup? > > > > On F14, doing "sudo killall nm-applet" is sufficient. > > However, on F17, doing "sudo killall nm-applet" isn't sufficient :( > > > > Any ideas please. I am really finding it irritating, that this gnome-popup > > is interfering with the sugar experience. > > > > > > Thanks and Regards, > > Ajay > > > part 2 text/plain 153 > ___ > Sugar-devel mailing list > sugar-de...@lists.sugarlabs.org > http://lists.sugarlabs.org/listinfo/sugar-devel =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Techteam] Announcing Q4D17 for XO-1.75
manuel wrote: > On Sat, Jun 16, 2012 at 12:23 AM, James Cameron wrote: > > http://wiki.laptop.org/go/OLPC_Firmware_q4d17 > > Hello, > > I'm new on this list and I have a question related with the new firmware. > > Should I do something on my XO 1.75 to get this firmware installed? > This is because I thought the firmware is updated after a "fs-update", > but I'm not completely sure. I have installed os14 on my XO 1.75 firmware is bundled with releases, and when it is, it will be installed automatically when you install the release. that's fine for many, many people. in this case, it will always upgrade, and never downgrade. automatic installation will never take you "backwards". you can also install firmware manually: put the .rom file on a USB stick, and type "flash u:\file.rom" at the 'ok' prompt. you might do this to help with testing, or because you know that the firmware fixes a known problem you're experiencing. when installing manually, you can do a downgrade. paul =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: [Testing] [OLPC New Zealand] Testing Summary, Auckland - 16 June 2012
daniel wrote: > On Sat, Jun 16, 2012 at 5:56 AM, Tom Parker wrote: > > Maze seems ok . 90 deg rotation leaves some of the maze off > > screen. When 180 rotation down arrow moves image upwards - > > anti-intuitive. are you talking about the arrow keys on the keypad? or the round set on the lower-left of the bezel (the "d-pad")? the d-pad has always rotated with the screen. but we've never rotated the action of the keyboard arrows -- there aren't very many programs one would want to use from the keyboard while rotated. we can revisit this, but it's never come up before. (and for completeness, this isn't just a 180 degree issue, right, but also an issue at 90 and 270?) paul > > Filed http://bugs.sugarlabs.org/ticket/3713 for the offscreen issue. > Not really sure what to do about the arrow keys issue - its an issue > we'll have in all activities. Will give it some thought. > > Thanks for the great testing - looking forward to the next report :) > > Daniel > ___ > Testing mailing list > test...@lists.laptop.org > http://lists.laptop.org/listinfo/testing =- paul fox, p...@laptop.org ___ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
Re: Kernel development setup for XO-1.75
martin wrote:
> { Maybe someone can polish it further and put it into a wikipage. Note
> that the process and tools change over time a bit... }
>
> Hi new kernel developer,
>
> Here are some hints, meant for a self-sufficient kernel developer to
> find her/his own way. Some you may know already :-)
>
> - You will want to be on devel@lists.laptop.org for general hacking
> questions. This is an open list, so no NDA topics. You will see build
> announcements there.
>
> - We also use irc -- #olpc-devel on OFTC
>
> - You need to know how to download and install a build (grab the zd
> file, look in the install instructions for "fs-update").
>
> - You will want to have your XO setup with a serial port - search our
> wiki for the Serial adapter page...
>
> - The kernel that _actually_ boots is in /bootpart/boot/vmlinuz, it
> then uses an initramfs that invokes dark magic before it invokes a
> "normal" userland. You can only boot into a usable system through this
> magic initramfs.
>
> Our current development practice is to provide a kernel via USB (or
> even WLAN) so
> that the XO ignores the one on the internal disk. Put the attached
> olpc.fth file in a FAT formatted USB, inside a "boot" directory. Then
> put a "zimage" file in the root of the USB disk.
[ alternatively, you can simply install your kernel in /bootpart/boot,
and adjust the vmlinuz symlink accordingly. if you do this, and
your kernel config is _not_ monolithic, then you'll need to have
put a copy of your modules under /usr/lib/modules. if you need
to make booting changes (i.e., adjust kernel commandline, etc), you'll
edit /bootpart/boot/olpc.fth. ]
>
> This olpc.fth file controls the boot process, you can tweak boot
> parameters in there, or tell it to boot a kernel fetched via http over
> wlan. It is written in Forth.
>
> - You'll want our git tree: git://dev.laptop.org/olpc-kernel -
> "master" there follows Linus' kernel. We are currently working on
> arm-3.0-wip
> for XO-1.75.
>
> - Our defconfig file is in arch/arm/configs/xo_175_defconfig. I
> normally copy it to .config and then perl -pi -e 's/=m/=y/' to make a
> monolithic kernel that Just Boots.
>
> - We currently crosscompile our kernels for development --
if you're running ubuntu/debian, you can simply
apt-get install gcc-arm-linux-gunabi
and set ARCH="arm" and CROSS_COMPILE="arm-linux-gnuabi-" before
running make as usual. otherwise, you'll want to untar, as described
below.
paul
> Untar http://dev.laptop.org/~cjb/gcc-4.6.0-from-x86_64-to-armv7.tar.bz2
> to /opt, then
>
> PATH=$PATH:/opt/crosstool/gcc-4.6.0/bin/
> make ARCH=arm CROSS_COMPILE=armv7-unknown-linux-gnueabi- target here>
>
> - We have an autobuilder that makes nice RPMs of the kernels based
> on our git branches. Once you have a well tested patch, spam someone
> in our team to get it into the official git repo so that it gets into
> our RPM'd kernels...
>
> This is merely a start.
>
>
>
> m
> --
> mar...@laptop.org -- Software Architect - OLPC
> - ask interesting questions
> - don't get distracted with shiny stuff - working code first
> - http://wiki.laptop.org/go/User:Martinlanghoff
>
>
> --
> mar...@laptop.org -- Software Architect - OLPC
> - ask interesting questions
> - don't get distracted with shiny stuff - working code first
> - http://wiki.laptop.org/go/User:Martinlanghoff
> part 3 text/plain 129
> ___
> Devel mailing list
> Devel@lists.laptop.org
> http://lists.laptop.org/listinfo/devel
=-
paul fox, p...@laptop.org
___
Devel mailing list
Devel@lists.laptop.org
http://lists.laptop.org/listinfo/devel
