IRC log for #qi-hardware on 20180430

00:11.22*** join/#qi-hardware zcrc (~pcercuei@190.184.215.189)
00:18.29*** join/#qi-hardware zcrc (~pcercuei@190.184.215.189)
00:18.32*** join/#qi-hardware sandeepkr (~sandeepkr@ec2-52-29-251-54.eu-central-1.compute.amazonaws.com)
00:25.12*** join/#qi-hardware infobot (ibot@rikers.org)
00:25.12*** topic/#qi-hardware is Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben/atusb 802.15.4 wireless, anelok and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs and http://irclog.whitequark.org/qi-hardware
00:25.12*** mode/#qi-hardware [+v infobot] by ChanServ
07:32.44*** join/#qi-hardware jwhitmore (~jwhitmore@109.78.225.104)
08:49.43*** join/#qi-hardware eintopf (~eintopf@unaffiliated/eintopf)
09:03.47*** join/#qi-hardware sb0 (~lekernel@59.152.213.90)
09:24.35*** join/#qi-hardware feabeaeadd (~feabeaead@gateway/tor-sasl/feabeaeadd)
09:24.48feabeaeaddHello
09:25.13feabeaeaddLong time Ben Nanonote user here
09:25.26feabeaeaddI am surprised to see so many people on this channel
09:25.42feabeaeaddI'm just checking out, out of curiosity
09:25.56feabeaeaddI thought Qi Hardware was dead and long gone
09:26.18feabeaeaddHow have things been doing for the last 7 years?
09:57.54wpwrak7 years already ? wow. time flies :)
10:01.37feabeaeaddYes, it does
10:04.09wpwrakwell, there's a wee bit of activity on the nanonote every now and then.
10:04.47wpwraki still have the anelok project. been very quiet for a while but now i found a new cpu to play with, the ingenic x1000. that should make things interesting again :)
10:22.38*** join/#qi-hardware feabeaeadd1 (~feabeaead@gateway/tor-sasl/feabeaeadd)
11:28.29*** join/#qi-hardware jwhitmore (~jwhitmore@109.78.225.104)
12:23.36feabeaeadd1I see wpwrak
12:23.58feabeaeadd1I don't have time to contribute to the nanonote :(
12:24.16feabeaeadd1But it would have been interesting to update all the software and the toolchain
12:24.37feabeaeadd1Considering that everything is still working with kernel 2.6 and gcc4
12:25.00feabeaeadd1There's a lot of improvement that has been done since then, it's probably worth it
12:25.12feabeaeadd1But I'm no kernel/gcc expert either.
12:28.08feabeaeadd1Although, on the electronic side, I don't know where to start, as I have zero knowledge in electronics whatsoever
12:28.34feabeaeadd1I know that capacitors hold charge, the bigger, the better. But that's about it! :P
12:51.36*** join/#qi-hardware paul_boddie (~paul_bodd@host-37-191-179-129.lynet.no)
13:00.05paul_boddieRecent NanoNote-related stuff: http://www.boddie.org.uk/paul/L4Re-Fiasco.OC.html
13:00.56paul_boddiewpwrak: Did you get a development board for the X1000 in the end?
13:02.26eintopfL4 Fiasco? waaahhhhhhhhh
13:04.38paul_boddie?
13:48.45paul_boddiefeabeaeadd: There is kernel renovation going on, but I haven't managed to get Paul C's work to run yet.
13:49.18paul_boddieThe pinctrl stuff seems OK, but I suspect other breakage.
13:56.21kyakwow, i didn't know something else can run on Ben apart from Linux
13:58.47paul_boddieI thought that someone must have ported something else, like a BSD or even Inferno, but maybe not.
13:59.23kyakoh, i remember now.. There was a guy, named Bas, and he had ab "Iris" project
14:00.08paul_boddieYes, Bas Wijnen made Iris available for the Ben and Trendtac/Letux 400.
14:00.35paul_boddieHe has been very helpful when I've asked him stupid questions about the hardware. :-)
14:01.01kyakwriting an OS from scratch for a capable hardware is such a big task..
14:01.20paul_boddieI previously had a simple payload that activated the screen, did some task switching, tested the keypad. Bas was really helpful about some of that.
14:03.28kyakfeabeaeadd1: by the way, it's not 2.6, it's 3.3.8 that was the kernel is the image released last :)
14:05.10paul_boddieMore recent kernels have worked. But things broke at 4.13, I think.
14:06.05kyakthey will eventually kick it out of upstream, if not already
14:07.44paul_boddieLinux kernel development is awful for that and many other reasons.
14:10.08feabeaeadd1I see. I've suspected something like that
14:12.13paul_boddieI don't see it necessarily going away, given that much of the Ingenic stuff might be upstream, but things may need to move to device tree support.
14:12.47feabeaeadd1paul_boddie: It's awful, but what makes it usable are the drivers, right? As far as I know, it's the only FOSS kernel that has that much support. Otherwise, there's probably other good FOSS kernels out there for UNIX-like OSs.
14:14.45paul_boddieThat's why I'm interested in alternatives to Linux plus the notion of generic drivers.
14:29.01feabeaeadd1I see
14:29.34feabeaeadd1I've been tinkering with OpenBSD recently, but I haven't looked much at their source code
14:30.26feabeaeadd1It's probably not suited for devices like the Dingoo
14:30.33feabeaeadd1Or is it? I don't know
14:31.21feabeaeadd1NetBSD should be(?) a safe bet in terms of portability and generic drivers
14:33.42paul_boddieI think it's NetBSD that provides the rump kernel stuff. That is quite interesting.
14:34.49paul_boddieSurely someone must have ported NetBSD to one of these devices. Rockbox was ported to the Dingoo and maybe the Ben, I think.
14:50.51paul_boddieI guess there's also RetroBSD and LiteBSD which even run on PIC32. But something more conventional/modern would be more feasible.
14:58.31*** join/#qi-hardware sb0 (~lekernel@138019142177.ctinets.com)
14:59.25wpwrakpaul_boddie: arrived last week, yes. they don't make the X1000 modules/boards anymore - they've now upgraded everything to X1000E (so, 64 MB of RAM).
15:04.23paul_boddieSounds exciting!
15:05.11paul_boddieI guess the X1000 is most closely related to the JZ4770/4780.
15:14.08wpwraki hope so, yes :) maybe m150 and such are an even closer match. alas, there's no programming manual for the x1000. but they publish a linux kernel. and there are PMs for the other cpus.
15:15.08wpwraksadly, usbboot from xburst-tools doesn't recognize it, and trying to patch and compile it ends with a ton of issues
15:15.30wpwrakso i don't know yet if usb booting is still the same
15:19.19paul_boddieI haven't tried xburst-tools with the CI20 which uses the JZ4780.
15:19.27paul_boddieBut this guy wrote his own tools: http://code.lardcave.net/2015/03/07/1/
15:20.10paul_boddieMaybe there are some clues in that.
15:24.21wpwrakah, let's see ...
15:36.59wpwrak"Unknown CPU with info X1000_v1" looks promising
15:37.32wpwrakcmopilation of the load binary fails. so anything past initial contact won't work. but that's already better than what i had so far :)
15:38.15wpwrak(ingenic provide a "cloner" for usb boot, too. but that one's closed, with a gui, and has very specific ideas about how things are organized)
15:45.06paul_boddieSounds a bit like Allwinner, from what I've heard, but I guess they need nice "easy" tools for the factories.
15:45.59paul_boddieI'd hate to have to maintain these programming tools. For PIC32, I found a nice Free Software suite that did the business.
15:49.34wpwrakthe USB uploader looks friendly enough :) https://github.com/nfd/ci20-os/blob/master/usbloader.py
15:50.17wpwraknow .. where's that TCSM in the x1000 ... it has a habit of moving around ...
15:57.31wpwrakseems to be the same on jz4780 and x1000. actually, M150 has it there, too. it's remapped. so that things is constant. okay, now let toggle some LED ...
16:03.18paul_boddieStuff appears and disappears, too. Although maybe they've settled on the basic peripherals now.
17:10.26*** join/#qi-hardware zcrc (~pcercuei@201.186.120.97)
17:49.22*** join/#qi-hardware jwhitmore (~jwhitmore@109.78.225.104)
20:56.07*** join/#qi-hardware _whitelogger (~whitelogg@uruz.whitequark.org)
20:56.07*** mode/#qi-hardware [+v _whitelogger] by ChanServ
22:23.06whitequarkDocScrutinizer51: wpwrak: I want to request a PID from openmoko
22:23.08whitequarkwho do I go to?
22:32.50*** join/#qi-hardware eintopf (~eintopf@unaffiliated/eintopf)
23:35.41*** join/#qi-hardware feabeaeadd1 (~feabeaead@gateway/tor-sasl/feabeaeadd)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.