| 01:08.14 | *** join/#maemo hurrian (~hurrian@unaffiliated/rikanee) |
| 01:22.05 | *** join/#maemo tm (~sinnlos@unaffiliated/tm) |
| 01:38.28 | *** join/#maemo keithzg__ (~keithzg@198-48-134-113.cpe.pppoe.ca) |
| 03:42.08 | *** join/#maemo hurrian_ (~hurrian@unaffiliated/rikanee) |
| 03:47.50 | *** join/#maemo pagurus (~user@i5387B1D8.versanet.de) |
| 04:18.40 | *** join/#maemo LauRoman|Alt (~LauRoman@5-14-80-39.residential.rdsnet.ro) |
| 04:36.37 | brolin_empey | DocScrutinizer05: Do you mean an address in a place referred to as China or do you mean an address written in a Chinese language? |
| 04:39.08 | brolin_empey | I guess English can be considered a Chinese language since it seems to be commonly used in the two Chinas. |
| 04:42.28 | brolin_empey | Well, a language of China but maybe not a Chinese language, maybe similar to the difference between, for example, a flag of Canada and a Canadian flag: the flag of British Columbia is a Canadian flag but it is not the flag of Canada. |
| 04:48.24 | *** join/#maemo hurrian_ (~hurrian@unaffiliated/rikanee) |
| 05:40.19 | *** join/#maemo spiiroin (~spiiroin@185.252.116.240) |
| 06:05.56 | Oksana | maps.google.com does work in Fennec, at least partially, but very slowly, at legendary slow pace of Fennec |
| 06:22.14 | *** join/#maemo dafox (~dafox@89.200.44.105) |
| 06:29.26 | sicelo | Oksana: the j2me Google Maps application works quite well and fast with phoneme/cvm. only it can't get gps coordinates, althought it manages to turn gps on |
| 06:52.38 | brolin_empey | Run Google Maps for Android on Maemo? |
| 06:53.39 | sicelo | how? |
| 06:56.49 | brolin_empey | sicelo: I do not remember the specifics but I think they were discussed in this channel, likely involving me, years ago. You need a kernel that includes some stuff used by Android (drivers?) and a GNU+Linux application whose name I forget that can run Android applications on GNU+Linux. |
| 07:01.49 | sicelo | ah |
| 07:04.59 | brolin_empey | I remember being interested in running Android applications on Maemo 5 in 2014 and maybe 2013 too but I never actually tried it because I switched to Android because my N900 user experience in Canada was too bad. |
| 07:08.39 | brolin_empey | My N900 has been running idle on my computer table at home for months by now but my N900 is so slow that it literally takes a few seconds between me sliding the switch on the side and something being drawn on the display. |
| 07:09.33 | brolin_empey | I mean sliding the switch on the side when the display was off. |
| 07:11.05 | *** join/#maemo hurrian_ (~hurrian@unaffiliated/rikanee) |
| 07:14.09 | brolin_empey | Partially incidentally: Does DirectFB still exist? I remember it from over a decade ago but have not heard of it for a long time by now. |
| 07:17.49 | luke-jr | things rarely cease to exist |
| 07:18.09 | luke-jr | digital things* |
| 07:19.40 | luke-jr | last commit was 3 years ago tho https://github.com/deniskropp/DirectFB |
| 07:20.10 | brolin_empey | http://digital.com/ is no longer used by DEC/Compaq/HP. ;-) |
| 07:24.05 | brolin_empey | luke-jr: In this case, I meant is the DirectFB project still active/supported/usable with current hardware and software. I was reading about DirectFB on en.wikipedia.org after I asked here. |
| 07:24.28 | luke-jr | brolin_empey: well, DirectFB can run in an X11 window, so.. |
| 07:25.04 | luke-jr | I wrote some software that uses it in 2014, and it still works :P |
| 07:28.02 | brolin_empey | OK but there are projects such as Mac-on-Linux that still exist but appear to be mostly inactive and no longer working with current software, in this case presumably because Mac-on-Linux became significantly less relevant after Apple switched from PowerPC to x86. |
| 07:31.46 | brolin_empey | That said, I do not know if it is still feasible to use a current GNU+Linux distribution on PowerPC because I believe Apple was the primary user of PowerPC for desktop/notebook computers. |
| 07:32.28 | luke-jr | Apple, those fools |
| 07:32.39 | luke-jr | brolin_empey: PPC is making a come back |
| 07:32.50 | luke-jr | brolin_empey: my new desktop is PPC |
| 07:33.05 | luke-jr | well, 1 year old now I guess, but still pretty bleeding edge |
| 07:33.40 | luke-jr | new enough to have driver issues still :p |
| 07:34.05 | brolin_empey | luke-jr: PowerPC or Power ISA but not PowerPC? |
| 07:34.21 | luke-jr | brolin_empey: Power ISA 3.0 |
| 07:34.27 | luke-jr | which is apparently still considered PowerPC |
| 07:36.13 | brolin_empey | What about XFree68? Yes, not XFree86. Is XFree68 still alive? I thought even Debian GNU+Linux dropped the m68k port. |
| 07:37.25 | luke-jr | XFree86 died before Maemo was a thing.. |
| 07:37.37 | luke-jr | never heard of XFree68 |
| 07:39.25 | brolin_empey | XFree86 continued for a while after the X.Org fork. XFree68 was XFree86 for m68k if I recall correctly, hence the name. |
| 08:38.20 | Oksana | brolin_empey: sicelo : apkenv needs to be compiled/packaged for N900. Last I remember, it's packaged for N9/or/Pandora but not N900? Should be trivial, but requires knowledge of Debian packaging, time and patience. |
| 08:44.03 | *** join/#maemo spiiroin (~spiiroin@185.252.116.240) |
| 08:49.14 | brolin_empey | https://www.linuxjournal.com/article/2090 |
| 08:49.14 | brolin_empey | âOne side effect of the UFB approach is virtually all Linux/m68k binaries are compatible with all Linux/m68k platforms. For example, the XFree68 server binary can operate all of the display hardware supported by Linux/m68k on both the Atari and Amiga. Even the kernel can be compiled to run on both Ataris and Amigas, and was distributed this way until the 2.0 series, when the number of devices needed for each OS made the combined kernel too large for users |
| 08:49.14 | brolin_empey | with only 4 MB of RAM. More programs supporting the UFB interface are forthcoming.â |
| 08:49.14 | brolin_empey | Apparently at least some of my speculation about binary compatibility between different computer platforms using the same ISA/CPU architecture was incorrect but this article is from 1997, by which point Commodore (the company) had died and Apple had already begun switching from m68k to PowerPC. The title of this article is kind of a misnomer at least in a literal sense because it says Linux runs on the 68000 but the body of the article then says Linux only |
| 08:49.14 | brolin_empey | runs on 68020 and higher. |
| 08:56.16 | brolin_empey | Oksana: N900 is the hardware, not a software environment. Apparently Android can run as the host OS with limitations on the N900 but I do not know why someone would want to do that compared to using, for example, an HTC myTouch 4G Slide that ships with Android. |
| 09:05.23 | *** join/#maemo jskarvad (jskarvad@redhat/jskarvad) |
| 09:14.43 | *** join/#maemo l_bratch (~l_bratch@2a06:5844:e:471::9980) |
| 09:20.16 | *** join/#maemo hurrian (~hurrian@unaffiliated/rikanee) |
| 09:41.56 | *** join/#maemo l_bratch (~l_bratch@2a06:5844:e:471::9980) |
| 09:54.49 | *** join/#maemo parazyd (~parazyd@devuan/developer/parazyd) |
| 09:56.35 | *** join/#maemo parazyd (~parazyd@devuan/developer/parazyd) |
| 09:58.19 | *** join/#maemo parazyd (~parazyd@devuan/developer/parazyd) |
| 10:03.30 | *** join/#maemo eMHa (~mh@p5089DD52.dip0.t-ipconnect.de) |
| 11:26.44 | *** join/#maemo parazyd (~parazyd@devuan/developer/parazyd) |
| 11:43.21 | *** join/#maemo parazyd (~parazyd@devuan/developer/parazyd) |
| 11:46.00 | *** join/#maemo rhn_mk1 (~rhn@unaffiliated/rhn) |
| 11:46.45 | rhn_mk1 | hi there! is the calendar GUI open source? I'd like to hack some |
| 11:47.46 | rhn_mk1 | also, bugs.maemo.org has an expired certificate |
| 12:10.50 | rhn_mk1 | there it is: https://github.com/gidzzz/qalendar |
| 12:11.06 | rhn_mk1 | a bit too complicated, but it seems to do support biweekly schedules |
| 12:46.12 | *** join/#maemo lukedashjr (~luke-jr@unaffiliated/luke-jr) |
| 12:54.29 | sicelo | yes, qalendar is nice |
| 12:57.05 | sicelo | so a few hours ago i found out that on Android, one can send the location using an SMS (no need to know what the coordinates are), and i like this for use with friends & family who are not bothered to understand GPS coordinates |
| 12:57.41 | sicelo | but then, google encodes the link, e.g. https://www.google.com/maps/place/@/data=!4m2!3m1!1s0x1ee8cedc944f8bcd:0x13f41fdb0b5f97ce |
| 13:01.33 | sicelo | you can get the GPS coordinates by using curl for example, and finding the part with /maps/preview/place/ |
| 13:01.42 | brolin_empey | If I recall correctly, âGPS coordinatesâ are actually WGS84 coordinates? |
| 13:02.24 | sicelo | just wondering if someone else has played with this before and found easy way to extract gps coordinates |
| 13:11.36 | buZz | brolin_empey: EPSG:4326 |
| 13:11.44 | buZz | aka WGS 84 |
| 13:17.29 | brolin_empey | buZz: OK. |
| 13:41.00 | rhn_mk1 | sicelo: not extract, but... https://osm.org/go/0GDiC7rp |
| 13:42.15 | rhn_mk1 | it also exposes https://en.wikipedia.org/wiki/Geo_URI_scheme |
| 13:56.36 | sicelo | thanks. sorry i think i didn't explain myself properly ... i need to be able to retreive the coordinates from the Google-formatted location. |
| 13:58.24 | sicelo | the idea is that someone using an android device sends their location via SMS, i find the latitude/longitude from their URL, and can feed that to Ovi Maps to find my way to them, for example |
| 14:00.28 | sicelo | these are the perks of using N900 as opposed to 'sane' modern devices :-) |
| 14:11.53 | rhn_mk1 | well I can't offer you a solution for your current workflow, but I can propose a workflow based on OSM and standards instead :) |
| 14:12.57 | rhn_mk1 | does anyone know what target rustc needs to compile for the N900? any pitfalls I should expect? |
| 14:14.40 | *** join/#maemo l_bratch (~l_bratch@2a06:5844:e:471::9980) |
| 14:17.45 | sicelo | rhn_mk1: i don't know if i'm missing something, but i can't see a connection between OSM and a location link formatted like https://www.google.com/maps/place/@/data=!4m2!3m1!1s0x1ee8cedc944f8bcd:0x13f41fdb0b5f97ce |
| 14:18.37 | rhn_mk1 | a link formatted like this: https://osm.org/go/0GDiC7rp provides the same service: it sends the location from one person to another |
| 14:19.36 | sicelo | i understand you a bit better now |
| 14:19.49 | sicelo | :-) |
| 14:24.40 | rhn_mk1 | I admit I might be a bit pushy about OSM ;) |
| 14:28.49 | sicelo | i love OSM, and have contributed a few times to the map |
| 14:40.21 | bencoh | rhn_mk1: assuming you're targetting maemo5, it should be armel/softfp iirc |
| 14:41.39 | rhn_mk1 | I'm going to try armv4t-unknown-linux-gnueabi, Debian's armel is v4t |
| 14:45.20 | brolin_empey | The N900 is ARMv7 if I recall correctly. |
| 14:46.09 | brolin_empey | I mean the Cortex A8 CPU used in the N900 is ARMv7. |
| 14:55.26 | brolin_empey | Wikipedia says that the Cortex A8 is ARMv7-A. |
| 14:59.03 | rhn_mk1 | that's a good thing, because Rust's armv4t cross-tolchain is not easily testable. I'll go up step by step |
| 15:02.04 | brolin_empey | The Samsung S3C2410A(L) and S3C2440 are ARMv4. |
| 15:04.07 | brolin_empey | Freescale i.MX283 is ARMv5. Original Raspberry Pi is ARMv6. |
| 15:26.32 | *** join/#maemo rhn (~rhn@unaffiliated/rhn) |
| 15:31.11 | *** join/#maemo Milhouse (~Milhouse@kodi/staff/milhouse) |
| 15:44.32 | *** join/#maemo Pali (~pali@Maemo/community/contributor/Pali) |
| 15:56.08 | *** join/#maemo dafox (~dafox@89.200.47.29) |
| 17:25.13 | *** join/#maemo Enrico_M_RX-51 (~Enrico_M_@5.170.68.211) |
| 17:27.29 | rhn | it was worth a try: "./rust-1.34.0-arm-unknown-linux-gnueabi/rustc/bin/rustc: /lib/libc.so.6: version `GLIBC_2.15' not found" |
| 17:27.34 | rhn | back to cross-compiling |
| 18:02.04 | *** join/#maemo daniel__ (~daniel@90.161.38.50) |
| 18:20.47 | *** join/#maemo daniel__ (~daniel@90.161.38.50) |
| 18:37.25 | *** join/#maemo Kabouik (~kabouik@2a01cb008023010021e2f0aac02c128d.ipv6.abo.wanadoo.fr) |
| 18:41.06 | *** join/#maemo Oksana_ (~Wikiwide@ppp121-44-80-201.bras1.syd7.internode.on.net) |
| 18:41.18 | *** join/#maemo Oksana_ (~Wikiwide@Maemo/community/ex-council/Wikiwide) |
| 19:07.34 | *** join/#maemo Vajb (~Vajb@85-76-144-82-nat.elisa-mobile.fi) |
| 21:26.40 | *** join/#maemo cyteen (~cyteen@cyteen42.plus.com) |
| 21:54.26 | *** join/#maemo florian_kc (~florian_k@Maemo/community/contributor/florian) |
| 22:48.45 | *** join/#maemo nslu2-log (~nslu2-log@23.141.224.193) |
| 23:11.22 | *** join/#maemo Kilroo (~Kilroo@173.94.24.151) |
| 23:26.49 | *** join/#maemo Zose (~Zose@95-105-238-89.dynamic.orange.sk) |
| 23:29.38 | *** join/#maemo Zose (~Zose@95-105-238-89.dynamic.orange.sk) |
| 23:31.26 | *** join/#maemo Zose (~Zose@95-105-238-89.dynamic.orange.sk) |
| 23:33.02 | *** join/#maemo Zose (~Zose@95-105-238-89.dynamic.orange.sk) |
| 23:35.55 | *** join/#maemo Zose (~Zose@95-105-238-89.dynamic.orange.sk) |
| 23:37.58 | *** join/#maemo Zose (~Zose@95-105-238-89.dynamic.orange.sk) |
| 23:42.32 | *** join/#maemo Zose (~Zose@95-105-238-89.dynamic.orange.sk) |