Topic for #qi-hardware is now Copyleft hardware - http://qi-hardware.com | hardware hackers join here to discuss Ben NanoNote, atben / atusb 802.15.4 wireless, and other community driven hw projects | public logging at http://en.qi-hardware.com/irclogs
<wolfspraul>
kristianpaul: that's a nice link about hiqsdr.org - thanks!
<wolfspraul>
unfortunately I couldn't find an RSS feed to add to the planet right now, but I will definitely watch this project, from the distance
<wolfspraul>
they seem to be very serious about high-quality information, bom, etc.
<wolfspraul>
sources are GPL licensed, but overall the licensing and tools is messy, too bad
<wolfspraul>
but I couldn't find anything like -nc -nd or so, it's all just open and a bit messy
skynet-2000 [skynet-2000!~skynet-20@unaffiliated/skynet2000] has joined #qi-hardware
Ayla [Ayla!~paul@117.188.103.84.rev.sfr.net] has joined #qi-hardware
wej [wej!~j@m2.mullvad.net] has joined #qi-hardware
kristianpaul [kristianpaul!~kristianp@cl-498.udi-01.br.sixxs.net] has joined #qi-hardware
kristianpaul [kristianpaul!~kristianp@unaffiliated/kristianpaul] has joined #qi-hardware
wej [wej!~j@m2.mullvad.net] has joined #qi-hardware
Textmode [Textmode!~boneidle@adsl-syd-2-209.ozonline.com.au] has joined #qi-hardware
Textmode [Textmode!~boneidle@adsl-syd-2-209.ozonline.com.au] has joined #qi-hardware
Textmode [Textmode!~boneidle@adsl-syd-2-209.ozonline.com.au] has joined #qi-hardware
DocScrutinizer [DocScrutinizer!~halley@openmoko/engineers/joerg] has joined #qi-hardware
Textmode [Textmode!~boneidle@adsl-syd-2-209.ozonline.com.au] has joined #qi-hardware
kyak [kyak!~kyak@93-80-209-199.broadband.corbina.ru] has joined #qi-hardware
kyak [kyak!~kyak@unaffiliated/kyak] has joined #qi-hardware
jekhor [jekhor!~jek@vulture-nat-37.telecom.by] has joined #qi-hardware
rejon [rejon!~rejon@li382-141.members.linode.com] has joined #qi-hardware
skynet2000 [skynet2000!~skynet-20@unaffiliated/skynet2000] has joined #qi-hardware
rejon [rejon!~rejon@221.221.173.59] has joined #qi-hardware
rejon [rejon!~rejon@221.221.173.59] has joined #qi-hardware
kilae [kilae!~chatzilla@catv-161-018.tbwil.ch] has joined #qi-hardware
skynet-2000 [skynet-2000!~skynet-20@unaffiliated/skynet2000] has joined #qi-hardware
wej [wej!~j@m2.mullvad.net] has joined #qi-hardware
wej [wej!~j@m2.mullvad.net] has joined #qi-hardware
<viric>
so I imagine noone runs 2.6.37 here
<viric>
Does 3.0 suspend fine?
<viric>
ah it just suspended fine
<viric>
hm
<viric>
maybe I can't reproduce the crash again
<viric>
I could suspend twice, and then I tried to play a video and crashed
<viric>
where is dvdk?
<kyak>
!seen dvdk
<qi-bot>
kyak, dvdk (~dvdkhlng@g225040150.adsl.alicedsl.de) was last seen quitting #qi-hardware 1 week 6 days 13 hours 4 minutes ago (25.12. 23:29) stating "Remote host closed the connection" after spending 46 minutes there.
<viric>
1 week...
<viric>
ok
<kyak>
on vacation, probably :)
<viric>
ah, I remember as if rarely seeing him here these last months
<viric>
I've read his code... nice
<viric>
of course, I can't tell why it hangs :)
<viric>
(sometimes)
<viric>
kyak: can you try suspend with the usb cable connected?
<viric>
hm it somehow works.
<viric>
I think that when the nanonote is 'on' by more than 1h (let's say), then suspend doesn't work anymore
<kyak>
i don't suspend very often, but when i do, it usually works
<viric>
hm ok
<kyak>
i remember it crashed several time though
<viric>
you usually halt?
<viric>
in fact it boots fast. 2.6.37 gives a login prompt in 5 seconds from poweron
<viric>
a big improvement over 2.6.36, iirc
<viric>
kyak: if the virtual consoles on frame buffer are totally implemented by software in the nanonote, I don't think there should be a memory limit for glyphs
<kyak>
yeah, i usually halt or not switch off at all
<kyak>
i'm not sure where this limit comes from..
<viric>
you even are not sure of the limit
<viric>
kyak: how do you type a ` with your keyb?
<viric>
shift-comma types "
wolfspraul [wolfspraul!~wolfsprau@p5B0AEFDC.dip.t-dialin.net] has joined #qi-hardware
Textmode [Textmode!~boneidle@adsl-syd-2-209.ozonline.com.au] has joined #qi-hardware
urandom__ [urandom__!~user@p548A24E7.dip.t-dialin.net] has joined #qi-hardware
Ayla [Ayla!~paul@11.241.112.78.rev.sfr.net] has joined #qi-hardware
kristianpaul [kristianpaul!~kristianp@unaffiliated/kristianpaul] has joined #qi-hardware
kristianpaul [kristianpaul!~kristianp@unaffiliated/kristianpaul] has joined #qi-hardware
Ayla [Ayla!~paul@117.188.103.84.rev.sfr.net] has joined #qi-hardware
mstevens [mstevens!~mstevens@fsf/member/pdpc.active.mstevens] has joined #qi-hardware
mstevens_ [mstevens_!~mstevens@ceres.etla.org] has joined #qi-hardware
emeb [emeb!~ericb@ip72-223-81-94.ph.ph.cox.net] has joined #qi-hardware
mstevens [mstevens!~mstevens@fsf/member/pdpc.active.mstevens] has joined #qi-hardware
Ayla [Ayla!~paul@11.241.112.78.rev.sfr.net] has joined #qi-hardware
<mstevens>
fuloong progress - I can see the screen now
jekhor [jekhor!~jek@86.57.254.166] has joined #qi-hardware
<viric>
what fuloong?
<viric>
mstevens: my fuloong just got a black screen, when I booted for the first time linux 3.2
<viric>
mstevens: are you dealing with that
<viric>
?
<mstevens>
viric: I have just purchased a new fuloong, and am trying to install debian
<viric>
ok
<mstevens>
at first I couldn't see the installer
<viric>
why?
<mstevens>
but then I switched from DVI to a vga cable, and now I can at least see the installer
<viric>
ah, deep debugging
<viric>
:)
<viric>
mstevens: I know little the fuloong, but I ported NixOS to it..
<mstevens>
viric: someone on #fsf reckoned the DVI out doesn't work right until X starts
<mstevens>
viric: my current problem is that the debian wheezy installer doesn't have the right kernel modules
<mstevens>
no driver for the network card
<viric>
to achieve what?
<viric>
ah ok
<mstevens>
My current test is a combination of the "openrays" kernel the machine ships with, and the debian wheezy initrd
<viric>
:)
<mstevens>
bah, boot that kernel and it just goes straight into rays
<viric>
?
<mstevens>
I think maybe the root device is hardcoded and it's ignoring my initrd
<viric>
that'd be very strange
<viric>
I used tftp to boot what I wanted
<kristianpaul>
mstevens: i ran debian wheezy (with X patched) and no problem on my yeeloong
<mstevens>
kristianpaul: I can't get the installer to see the fuloong network card
<mstevens>
It seems to be a rtl 8169, which the netinst images don't seem to have drivers for
<kristianpaul>
wich yeeloong revision is yours?
<mstevens>
I have a fuloong, not a yeeloong
<kristianpaul>
ah !
<mstevens>
whatever they sell if you ordered one 2 weeks ago
<kristianpaul>
nope mine is kinda old..
<kristianpaul>
and is yeeloong
<mstevens>
I am attempting to extract the requisite driver from the full kernel package and stuff it into the initrd
<Ayla>
it should have pushed only the two commits for jz-3.2 x_x
<mth>
git will push every branch that has a remote equivalent
<Ayla>
okay, so what should I do now? ...
<mth>
you can set the ref head to an earlier commit for jz-3.1
<mth>
I don't know the syntax by heart though
<larsc>
git push -f qi jz-3.1~4:jz-3.1
<larsc>
where the 4 is the number of commits you want to go back
<Ayla>
ok, I type that?
jekhor [jekhor!~jek@vulture-nat-37.telecom.by] has joined #qi-hardware
<larsc>
you type that
<larsc>
or you could pass a specific revision instead of the jz-3.1~X
* Ayla
crosses fingers
<larsc>
which is 4adea3bca06ca in our case
<larsc>
one of your commits is still there
<Ayla>
that one was pushed in november
<larsc>
ah
<viric>
I thought only larsc touched the kernel
<Ayla>
thank you for your help, and sorry about that
<mstevens>
/me returns
<larsc>
viric: i've been a bit quiet in that regard in the last months
<viric>
ah ok
<viric>
so me.
<larsc>
Ayla and mth are working on the linux port for the dingoo which is a handheld console which uses the same SoC as the Nanonote
<mstevens>
cut out the grub stage, seems promising
<larsc>
hence we share the same kernel repo
<mstevens>
there's more hard drive activity, anyway
<viric>
mstevens: you use grub?
<viric>
larsc: ah ok
<mstevens>
viric: the wheezy installer puts it in as part of the boot process
<viric>
mstevens: ah ok
<viric>
I've never seen grub on the fuloong
<mstevens>
viric: I've told pmon to boot the kernel directly and it seems to be more successful. Although hasn't actually booted yet, so I can't be sure.
<viric>
larsc: do you know of any suspend problems?
<larsc>
no
<viric>
hm ok
<viric>
Sometimes it crashes here
<viric>
and the screen with the console keeps lighted, as fading to white
<viric>
but it does not reach full white.
<larsc>
thats normal if the lcd hasn't received a powerdown command but the SoC isn't sending any pixel data anymore
<viric>
ah
<viric>
bad.
<viric>
I've seen that three times today, and one time yesterday
<viric>
(on suspend)
<viric>
(on 2.6.37)
<qi-bot>
Jon Phillips: Via @qihardware qihardware: RT @chitlesh: package review of urjtag - to improve #milkymist support on#fedora #openso... http://t.co/RUl3lKaA ( 156093693932212224@rejon - 31s ago via Ping.fm )
<larsc>
can you resume normally in such a case, or has the whole system crashed?
<viric>
in one case I could resume
<viric>
in the other, crashed
<viric>
I mean
<viric>
4 times crashed, one could resume
<viric>
ha. right now I suspended (screen black), resumed, and crased.
<viric>
crashed
<viric>
the cursor blinks, but no key does anything
<mstevens>
hmm, constant drive activity, no boot
<viric>
larsc:after resume, the console managed to write 'g_ether gadget: high speed config #1: CDC Ethernet (ECM)
<viric>
larsc: I'm simply running "echo mem > /sys/power/state"
<Ayla>
viric: on Nanonote?
<viric>
yes
<Ayla>
I've been working on the suspend feature
<viric>
Ayla: 2.6.37 though
<Ayla>
my changes are on the Qi kernel, but you should upgrade to a more recent kernel
<viric>
I run vanilla + openwrt patches
<mstevens>
seems to be having problems loading the initrd image
<viric>
Ayla: so, what's the best to run on the nanonote now?
<Ayla>
I don't know, I don't have a nanonote :D
<viric>
umh :)
kristianpaul [kristianpaul!~kristianp@cl-498.udi-01.br.sixxs.net] has joined #qi-hardware
kristianpaul [kristianpaul!~kristianp@unaffiliated/kristianpaul] has joined #qi-hardware
<viric>
Ayla: is there cpuidle for the jz47?
<Ayla>
what do you mean by 'cpuidle'
<viric>
hm linux cpuidle
<viric>
going to low power active states
<larsc>
yes. we'll put the cpu into sleep state if it is idle
<viric>
sleep is that of suspend?
<larsc>
no
<viric>
I see: normal, doze, idle, sleep modes
<Ayla>
I believe it's not supported currently
<larsc>
the jz4740 has a special sleep instruction which will halt the cpu until the next interrupt
<larsc>
we use that when the cpu is idle
<viric>
hm ok
<Ayla>
ah, that's why it consumes much less power when idle
<viric>
hm the sleep instruction has different meanings depending on the state of some registers
<viric>
I think larsc means the manual 'idle mode', while suspend would be the manual 'sleep mode'
<larsc>
yes. it either suspends the cpu
<larsc>
or the whole SoC
<larsc>
correct
<viric>
there is also the 'doze mode', not used now, right?
<larsc>
yes
<viric>
ok
kristianpaul [kristianpaul!~kristianp@unaffiliated/kristianpaul] has joined #qi-hardware
<viric>
I don't see what advantadges can bring the doze mode...
<Ayla>
something great would be a working ondemand CPU governor
<viric>
I think the doze mode is about ignoring some clocks...
<viric>
so doze mode could be used to implement some cpufreq
<viric>
kind of.
valhalla [valhalla!~valhalla@81-174-23-109.dynamic.ngi.it] has joined #qi-hardware
<larsc>
dozemode looks like a extra divider for the cpu clock to me
<viric>
larsc: that's what I menat
<viric>
meant
<viric>
isn't that the closest to cpufreq?
<viric>
btw, how do you test your kernel modifications?
<viric>
do you use xbboot?
<larsc>
flash it and boot, don't know what you want to hear
<viric>
ah
<viric>
xbboot can "upload file at <path> to <address> then jump to <address>"
<viric>
Ayla: and you? Flash and boot?
<Ayla>
I boot from USB when I need to test
<viric>
ok
<viric>
do you use KGDB or something like that through the serial line?
<Ayla>
no
<viric>
never tried?
<Ayla>
I don't really need KGBD
<viric>
I like to do those kinds of things...
<viric>
Ayla: no? hm
valhalla [valhalla!~valhalla@81-174-23-109.dynamic.ngi.it] has joined #qi-hardware
<viric>
larsc: perf for the nanonote does not build, btw
<viric>
hm what is the serial port major,minor in the nanonote?
<viric>
what I am doing wrong? 'stty -F /dev/ttyS0 raw 57600'
<viric>
I run 'cat ttyS0&'
<viric>
and 'echo hola > ttyS0'
<viric>
crossing the tx/rx in the serial.
<viric>
I try both S0 and S1
jluis [jluis!~jluis@176.Red-81-38-165.dynamicIP.rima-tde.net] has joined #qi-hardware
<viric>
S1 even blocks on 'echo hola > ttyS1' now...
<viric>
weird.
<viric>
I thought that'd be trivial
<viric>
anyone alive, to tell me the major,minor of the serial port of the backwards of the nanonote?
<wolfspraul>
wpwrak: I'm looking at your bug report saying "pcbnew --plot doesn't pickup global clearance settings"
<viric>
ok, I checked that it's ttyS0... the nanonote sends fine, but does not receive.
<viric>
ARGH I've a mingetty at ttyS0
skynet-2000 [skynet-2000!~skynet-20@unaffiliated/skynet2000] has joined #qi-hardware
<viric>
which... looks irrelelant
<viric>
irrelevant
<wpwrak>
wolfspraul: hmm, now if i would remember it ... presumably worked around it, then swiftly reused the precious memory space :)
<viric>
nothing. I fail at the serial port.
<viric>
wpwrak: do you have a serial port connection for the nanonote? :)
<viric>
wpwrak: crossing tx and rx should allow me to get echo, no?
<wpwrak>
viric: echo from where to where ?
<wpwrak>
viric: i use idbg for the serial port
<viric>
ahh.
<viric>
so...
<viric>
I'm running: stty -F /dev/ttyS0 raw 57600
<viric>
then: while true; do echo hola; done > /dev/ttyS0 &
<viric>
then: cat /dev/ttyS0 &
<viric>
and cross the tx and rx pins
<viric>
I get nothing
<viric>
I've checked with a ftdi cable, and the nanonote sends well. But looks like not receiving anything
<wpwrak>
hmm, which set of TX/RX contacts are you using ? the ones near the battery or the ones at the front of the PCB ? the RX near the battery is reassigned to the keyboard, so you'd have to reassign it for UART use
<viric>
at the bottom of the battery
<viric>
labelled
<viric>
eh?
<viric>
either serial or keyboard?
<viric>
:)
<wpwrak>
yes
<viric>
how? an echo to some gpio thing?
<wpwrak>
RX is shared
<viric>
wpwrak: what page of the manual says that? :)
<viric>
how can I 'reassign' it?
<wpwrak>
page 5 of the schematics ? :) pin 72 (KEYIN8) right below TP75
<viric>
but
<viric>
'reassign' means a software operation, no
<viric>
?
<wpwrak>
or page 20 of jz4720_ds :)
<wpwrak>
(reassign) yes
<viric>
ahh
<viric>
what one?
<wpwrak>
the reassigning would be page 356 of jz4740_pm, PDFUN
<viric>
mh
<wpwrak>
you basically have to write a 1 << 26 to PDFUNC, then you may be able to RX
<viric>
:)
<wpwrak>
(not sure if there's anything else in the way)
<viric>
Can I do that with 'dd' and /dev/mem? :)
<wpwrak>
an easier approach would be to run a wire to the other set of TX/RX pins
<viric>
I wrote that to the qi wiki as well, on 'serial console'
<viric>
kristianpaul: what do you do with the nanonote serial port?
<viric>
program arduinos like david? :)
<viric>
!seen tuxbrain
<qi-bot>
viric, I found 6 matches to your query. These are the 5 most recent ones: tuxbrain_HxxHhzo, tuxbrain, tuxbrain_zzzzzz, tuxbrain_PASS, tuxbrain_WPAN. tuxbrain_HxxHhzo (~tuxbrain@95.61.34.233) was last seen quitting #milkymist 11 weeks 5 days 3 hours 15 minutes ago (18.10. 19:27) stating "Ping timeout: 256 seconds" after spending 23 hours there.
<viric>
long ago
jekhor [jekhor!~jek@vulture-nat-37.telecom.by] has joined #qi-hardware
<DocScrutinizer>
wow, that's cute
<kristianpaul>
viric: no
<kristianpaul>
viric: connect to gps receiver and posibly to a jeenode (not yet do)
<kristianpaul>
you edited the wiki, great !
<wolfspraul>
our under-loved wiki
emeb [emeb!~ericb@71-209-157-173.phnx.qwest.net] has joined #qi-hardware