DocScrutinizer05 has quit [Disconnected by services]
DocScrutinizer05 has joined #qi-hardware
xiangfu_ has joined #qi-hardware
xiangfu has quit [Ping timeout: 255 seconds]
kristianpaul has quit [Ping timeout: 248 seconds]
wolfspraul has quit [Ping timeout: 264 seconds]
ezdagor has joined #qi-hardware
<ezdagor>
Hi. I compiled the latest openwrt-xburst kernel, and i've noticed that the screen will turn white after 5 or so minutes. Not sure what is causing this behaviour.
jekhor has joined #qi-hardware
<viric>
white? oh.
<ezdagor>
Yeah. After there hasn't been any input for 5 or so minutes.
<ezdagor>
I'm thinking I missed a certain kernel option.
<viric>
ah, I guess it stops providing pixels to the screen
<ezdagor>
Well, I can press a key, and the screen goes back to how it should be.
<viric>
the screen should be disabled after 5 minutes
<viric>
I don't know the code around that though
<ezdagor>
Nod.
<kyak>
ezdagor: check the consoleblank kernel parameter
<kyak>
(in kernel command line i mean)
<ezdagor>
Where at?
<kyak>
cat /proc/cmdline
<ezdagor>
Ok.
<kyak>
fw_printenv/fw_setenv let you change that
<ezdagor>
consoleblank=30
<kyak>
does it blank after 30 seconds?
<ezdagor>
No.
<ezdagor>
There is also a "quiet" after that, too.
<kyak>
are you in console even?
<ezdagor>
fbterm
<kyak>
gmenu2x has it's own blanker
<kyak>
hm, can you try with ash?
<kyak>
might be a problem with fbterm, i guess
<ezdagor>
Waiting.
<kyak>
is your background white in fbterm?
<ezdagor>
No. It isn't.
<kyak>
that;s strange :)
<ezdagor>
Nod.
<ezdagor>
I'm just worried that the screen will be permanently "stuck."
<ezdagor>
Still waiting on ash.
<kyak>
something is wrong
<kyak>
it should just blank after 30 seconds
<ezdagor>
Nod.
<kyak>
are you running the latest image, except for the kernel you built yourself?
<ezdagor>
I'm using the Debian "Lenny" image.
<kyak>
what is your kernel version?
<ezdagor>
3.3.8
<kyak>
ok, it's the same here.. What's uboot version?
<kyak>
also, did you change the default kernel config?
<ezdagor>
Hmm. Not sure.
<ezdagor>
I changed a few options, yes.
<kyak>
how did you compile the kernel? using the openwrt toolchain?
<ezdagor>
Yes.
<kyak>
you might want to flash the latest uboot, and the latest kernel (all prebuilt). See if it works with your debian image well
<kyak>
then you should try to compile the kernel yourself, with default parameters
<ezdagor>
Nod. I was thinking about using the pre-built kernel.
<kyak>
then you can try to change some parameters :)
<ezdagor>
Nod.
<ezdagor>
There is no fw_prinenv/fw_setrenv program installed.
<kyak>
sure, it's provided by openwrt rootfs
<ezdagor>
Ah.
lekernel has joined #qi-hardware
<larsc>
ezdagor: it's a known bug
<larsc>
(known by me) ;)
<larsc>
ah, ok, not 3.9
jekhor has quit [Ping timeout: 252 seconds]
<apelete>
good morning
<apelete>
larsc: tested kernel 3.9 yesterday, it booted a jlime image just fine
<apelete>
larsc: noticed 2 problems though:
<apelete>
1/ cannot enter numbers on the keyboard. it seems Fn key does not work
<apelete>
2/ ethernet over usb does not work, interface usb0 does not show up with ifconfig
<apelete>
larsc: are these issues known or do you think they come from my setup ? (using an old uboot + jlime image. only replaced jlime 2.6.36 which works fine with qi kernel 3.9)
<larsc>
apelete: you need to load a special keymap I think
<larsc>
ethernet over usb works for me, but it could be a error in the config
<apelete>
larsc: I've been thinking about writing the glue code for the jz4740 SoC for the usb gadget driver (we talked about it a few days ago)
<larsc>
:)
<apelete>
larsc: still need some help with that ? do you mind if I try to actually write that piece of code ? (I will probably need some guidance on how to proceed)
<larsc>
Would be great if you could take care of this
<larsc>
If you have any questions just ask
<apelete>
larsc: nice :)
<apelete>
larsc: is there a place where you keep the qi kernel patches ?
<larsc>
well in the git repo
<lekernel>
sharism.cc still down (again...)
<apelete>
larsc: yeah, but how can I tell the patches that are alerady upstream from those that are not ?
<larsc>
apelete: git log v3.9..jz-3.9
<apelete>
I think I'll start by reading the qi usb gadget driver, and compare it to the mainline usb gagdet driver to try to understand what I really need to do
baba has joined #qi-hardware
porchaso0 has joined #qi-hardware
cod3r has quit [Ping timeout: 252 seconds]
<larsc>
apelete: the upstream driver is the musb driver, which can be found at drivers/usb/musb
<larsc>
the IP core is also used in a couple of other SoCs, e.g. the blackfin and a couple of TI SoCs
<larsc>
so there are a few examples of glue code
<larsc>
the main difference to the jz4740 is that the jz4740 only uses the gadget part of the driver
porchao has quit [Ping timeout: 246 seconds]
<larsc>
I actually wouldn't bother looking too much at the jz4740 gadget driver, since it's not the best piece of code anyway
<larsc>
yea, first device probded via devicetree
<apelete>
larsc: there's no v3.9 tag in the qi-kernel repo, what am I missing here ?
<qi-bot>
[commit] Werner Almesberger: ircstat/stat, ircstat/mlstat: print month/year only every 4th month (master) http://qi-hw.com/p/wernermisc/0508e23