gcwnow / buildroot Goto Github PK

This behavior does not occur with the public 8-20-2014 firmware, only with newer unreleased beta firmware dated 2014-11-23. SDL 1.2 behaves the same as the old firmware. SDL 2.0 does not, however:

From the command line, use opkrun to run Nebuleon's SDL2.0 version of his input tester: 'opkrun -m jstester-2.gcw0.desktop input-test.opk' Alternatively, run a SDL2.0 app directly from the command line after issuing following command: echo Y > /sys/devices/platform/linkdev/alt_key_map

Any button presses, excluding the DPAD, will cause the following message to show on stdout:
'INFO: The key you just pressed is not recognized by SDL. To help get this fixed, please report this to the SDL mailing list [email protected] EVDEV KeyCode 3XX' Where 3XX corresponds to each unique button press.

Despite these messages, the alternate key-to-joy-event mapping is indeed functioning. If you disable the key-to-joy-event mapping, SDL does not report these errors and receives SDL_KEYUP/SDL_KEYDOWN events from the buttons, as normal, with no complaints of unrecognized evdev keycodes.

I was wondering, did your project write commit 6c2a690? If so, where did you find documentation on the MXU instructions? If not, where did you find the patch?

I've been looking for more information on the ISE, but I've only been able to find the Dingoonity wiki page, jzmedia.h in libjzcommon, mxu_as (that massive Bash script that filters assembly to replace MXU instructions with .word directives), and a few disparate mentions on mailing lists.

Under test firmware 2014-11-23, the g-sensor does not work, or at least does not work as before. From the command line, you can start the g-sensor module using 'gsensor --start' and see that its module gets loaded with 'lsmod'.

However, both SDL 1.2 and SDL2.0 only report 1 joystick available, whereas under the last public release, two would be reported and the G-sensor's reported name would be 'mxc6225'

It is easy to reproduce this behavior: simply try to run Nebuleon's SDL2.0 version of his input tester. Alternatively, run Neverball. Neither reports finding more than one joystick and neither finds the g-sensor. Also, none of the devices in /dev/input/ show anything when running 'cat' on them and moving the unit about. There also is no symlink created from /dev/input/gsensor to the device file, not that this in itself indicates a bug.

I end up having to manually download each Sourceforge tar archive, because the script no longer pulls the archive properly (downloads the webpage instead of the file is my guess).

Output error:

>>> p7zip 9.20.1 Downloading
--2015-04-19 21:36:18--  http://downloads.sourceforge.net/project/p7zip/p7zip/9.20.1/p7zip_9.20.1_src_all.tar.bz2
Resolving downloads.sourceforge.net (downloads.sourceforge.net)... 216.34.181.59
Connecting to downloads.sourceforge.net (downloads.sourceforge.net)|216.34.181.59|:80...  connected.
HTTP request sent, awaiting response... 307 Temporary Redirect
Location: http://sourceforge.net/projects/p7zip/files/p7zip/9.20.1/p7zip_9.20.1_src_all.tar.bz2/download?use_mirror=colocrossing [following]
--2015-04-19 21:36:18--  http://sourceforge.net/projects/p7zip/files/p7zip/9.20.1/p7zip_9.20.1_src_all.tar.bz2/download?use_mirror=colocrossing
Resolving sourceforge.net (sourceforge.net)... 216.34.181.60
Connecting to sourceforge.net (sourceforge.net)|216.34.181.60|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 14580 (14K) [text/html]
Saving to: ‘/home/larry/Downloads/NathanStuff/N64/buildroot/dl/p7zip_9.20.1_src_all.tar.bz2.tmp’

100%[======================================>] 14,580      --.-K/s   in 0.04s

2015-04-19 21:36:19 (335 KB/s) - ‘/home/larry/Downloads/NathanStuff/N64/buildroot/dl/p7zip_9.20.1_src_all.tar.bz2.tmp’ saved [14580/14580]

>>> p7zip 9.20.1 Extracting
bzcat /home/larry/Downloads/NathanStuff/N64/buildroot/dl/p7zip_9.20.1_src_all.tar.bz2 | tar --strip-components=1 -C /home/larry/Downloads/NathanStuff/N64/buildroot/output/build/p7zip-9.20.1  -xf -
bzcat: /home/larry/Downloads/NathanStuff/N64/buildroot/dl/p7zip_9.20.1_src_all.tar.bz2 is not a bzip2 file.
tar: This does not look like a tar archive
tar: Exiting with failure status due to previous errors
make: *** [/home/larry/Downloads/NathanStuff/N64/buildroot/output/build/p7zip-9.20.1/.stamp_extracted] Error 2

There have been 100's of these, and I am having to redownload every single one... *sigh

The RTC in my Zero is drifting at about +0.4-0.5 min / day -- more if I use it. I saw that there was some kind of RTC-related work in the last firmware release. Are there any more RTC fixes planned?

In test firmware dated 2014-11-23, I experienced random MOUSEMOTION events in my port of Neverball, which uses SDL 2.0. These occur about every 5 seconds or so if the unit is just left sitting running the program. If you move the analog joystick, the events are numerous and seem to coincide with the JOYAXISEVENTS the analog issues.

You can easily verify/reproduce the behavior by running the event-loop-sdl-2 binary in the bin/ folder of this small console-mode example program I put together to show the problem: https://github.com/senquack/event-loop-example

Please see issue description over here
https://lists.gnu.org/archive/html/bug-m4/2018-08/msg00000.html

Maybe
package/m4/m4.mk
7:M4_VERSION = 1.4.17 -> 1.4.19 ?

The title is self-explanatory. :)

If we have http://pyalsaaudio.sourceforge.net/ (in the same way there is PyGame support in https://github.com/gcwnow/buildroot/tree/opendingux-2012.08/package/python-pygame) we could record audio from Python.

With pyalsaaudio support , microphones testing could be added to https://bitbucket.org/clach04/hwtest/wiki/Home

It looks like you're using either shell calls or something else that needs special-character escaping in the new Connect utility. However it works, it doesn't with properly random WPA2 keys with special characters.

I finally got it working with my local network by finding the Connect settings under /media/data/local/home/.local/share/gcwconnect/networks , editing the file, and replacing the double quotes around the WPA2 key with single quotes.

Of course, anyone with single quotes in their WPA2 key is going to be out of luck.