| 00:45.10 | *** join/#qi-hardware aisa (~a@c-68-35-162-196.hsd1.nm.comcast.net) |
| 01:12.46 | *** join/#qi-hardware xiangfu (~xiangfu@fidelio.qi-hardware.com) |
| 01:55.02 | *** join/#qi-hardware freakazoid0223 (~matt@pool-71-246-26-142.phlapa.fios.verizon.net) |
| 02:02.26 | *** join/#qi-hardware nikescar (~nikescar@114.199.131.108) |
| 02:25.45 | *** join/#qi-hardware akiwiguy (~akiwiguy@unaffiliated/akiwiguy) |
| 02:25.48 | *** part/#qi-hardware akiwiguy (~akiwiguy@unaffiliated/akiwiguy) |
| 03:02.51 | *** join/#qi-hardware scientes (~scientes@unaffiliated/scientes) |
| 03:03.33 | *** join/#qi-hardware DocScrutinizer05 (~HaleBopp@openmoko/engineers/joerg) |
| 03:09.29 | qi-bot | [commit] Xiangfu: debian: regular update (master) http://qi-hw.com/p/fped/9ab9ae6 |
| 03:09.30 | qi-bot | [commit] Xiangfu: move debian/* to https://github.com/xiangfu/deb-pkg/ (master) http://qi-hw.com/p/fped/d59b472 |
| 03:19.56 | *** join/#qi-hardware uwe_ (~uwe_@dslb-088-064-209-125.pools.arcor-ip.net) |
| 04:06.12 | *** join/#qi-hardware heberth (~heberth@190.255.13.8) |
| 05:01.21 | kyak | mth: i see.. the same results i have. We'll see if 3.6 makes any difference for JZ4740 |
| 05:09.47 | *** join/#qi-hardware rejon (~rejon@d2-64.rb.sm.centurytel.net) |
| 05:20.36 | *** join/#qi-hardware guanucoluis (~luis@200.127.180.65) |
| 05:28.17 | *** join/#qi-hardware LunaVorax (~LunaVorax@ABordeaux-651-1-182-38.w109-214.abo.wanadoo.fr) |
| 05:47.41 | *** join/#qi-hardware kristianpaul (~kristianp@cl-50.mia-01.us.sixxs.net) |
| 05:47.42 | *** join/#qi-hardware kristianpaul (~kristianp@unaffiliated/kristianpaul) |
| 05:53.32 | LunaVorax | Does anyone knows here where I can buy a Neo Freerunner with a GTA04 board? |
| 05:56.24 | roh | LunaVorax: i think only here: http://www.handheld-linux.com/wiki.php?page=GTA04 |
| 05:56.52 | *** join/#qi-hardware scientes (~scientes@unaffiliated/scientes) |
| 06:00.53 | *** join/#qi-hardware kristianpaul (~kristianp@unaffiliated/kristianpaul) |
| 06:29.57 | *** join/#qi-hardware kristoffer (~kristoffe@c-b6dce555.010-30-6c6b7012.cust.bredbandsbolaget.se) |
| 06:36.20 | *** join/#qi-hardware jluis|work (~jpddb@2001:5c0:1000:a::1323) |
| 06:48.27 | *** join/#qi-hardware jekhor (~jek@46.53.195.142) |
| 07:11.07 | *** join/#qi-hardware jluis|work (~jpddb@83.247.136.72) |
| 07:39.51 | *** join/#qi-hardware kristianpaul (~kristianp@cl-50.mia-01.us.sixxs.net) |
| 07:39.51 | *** join/#qi-hardware kristianpaul (~kristianp@unaffiliated/kristianpaul) |
| 07:47.28 | *** join/#qi-hardware kristianpaul (~kristianp@cl-50.mia-01.us.sixxs.net) |
| 07:47.28 | *** join/#qi-hardware kristianpaul (~kristianp@unaffiliated/kristianpaul) |
| 08:57.19 | *** join/#qi-hardware jluis (~jluis@2001:5c0:1000:a::9ab) |
| 09:40.59 | *** join/#qi-hardware scientes (~scientes@unaffiliated/scientes) |
| 10:32.14 | *** join/#qi-hardware wej (~j@nl3x.mullvad.net) |
| 10:40.37 | mth | viric, larsc: this line was not integrated into mainline: "select SYS_SUPPORTS_ZBOOT_UART16550" |
| 10:40.56 | mth | is that no longer needed or should I keep a commit containing that one line? |
| 10:41.38 | mth | http://www.treewalker.org/temp/vmlinuz-leftover.patch |
| 10:41.47 | viric | ah no idea |
| 10:45.09 | *** join/#qi-hardware jekhor (~jek@178.120.89.103) |
| 10:49.53 | larsc | good question, any idea why it didn't make it? |
| 10:50.44 | mth | no idea, I just noticed that when cherry-picking all 3.5 commits into 3.6 this one didn't end up empty |
| 10:54.00 | larsc | the line is in the commit though, just at a different position |
| 10:54.22 | mth | ah, git failed to detect that then |
| 10:54.51 | larsc | I guess Ralf reordered it |
| 10:56.18 | mth | anyway, thanks for looking at it |
| 11:36.58 | *** join/#qi-hardware jluis (~jluis@2001:5c0:1000:a::2bf) |
| 11:54.37 | mth | larsc, kyak, xiangfu: I pushed the jz-3.6 branch to qi-kernel |
| 11:54.58 | mth | as always, tested on A320, builds for Nanonote but not tested there |
| 11:55.18 | mth | the board-qi_lb60.c might need an update for the pwm beeper |
| 11:56.20 | mth | see ad8f4827 for the update on board-a320.c for an example |
| 11:56.37 | mth | the pwm device is already added for the NN, but the new-style mapping is not |
| 12:34.50 | viric | the board has a pwm beeper? |
| 12:36.01 | *** join/#qi-hardware cladamw (~adamwang@host-174.163-235-182.cable.dynamic.kbtelecom.net) |
| 12:51.45 | mth | "static struct platform_device qi_lb60_pwm_beeper" says it does :) |
| 12:53.58 | viric | nice :) |
| 13:19.43 | whitequark | DocScrutinizer05: what do you think about Jolla? |
| 13:26.21 | larsc | mth: thanks |
| 13:26.40 | larsc | viric: yes. try to enter beep on the console |
| 13:30.43 | viric | but is that separate from the speaker? |
| 13:30.48 | viric | (I don't have the NN at hand) |
| 13:32.18 | xiangfu | mth, thanks. I will test it on nanonote. |
| 13:35.52 | larsc | viric: yes |
| 13:36.18 | larsc | there is a piezo |
| 13:40.55 | viric | ahh |
| 13:41.02 | viric | interesting :) |
| 14:08.07 | *** join/#qi-hardware Hoolxi (~Openfree@120.204.177.219) |
| 14:18.32 | *** join/#qi-hardware xiangfu (~xiangfu@123.114.250.8) |
| 14:23.51 | *** join/#qi-hardware aisa (~a@173-10-243-253-Albuquerque.hfc.comcastbusiness.net) |
| 14:27.37 | pabs3 | whitequark: yawn |
| 14:42.26 | *** join/#qi-hardware Freemor (~Freemor@ec2-174-129-226-140.compute-1.amazonaws.com) |
| 14:45.35 | *** join/#qi-hardware kristoffer (~kristoffe@c-b6dce555.010-30-6c6b7012.cust.bredbandsbolaget.se) |
| 15:00.14 | whitequark | pabs3: huh? |
| 15:05.23 | *** join/#qi-hardware paul_boddie (~paulbodd@hfaistos.uio.no) |
| 15:06.10 | paul_boddie | Does anyone want to answer a stupid Linux kernel programming question? |
| 15:12.58 | *** join/#qi-hardware urandom__ (~user@p54B0E772.dip.t-dialin.net) |
| 15:14.56 | kyak | mth: thanks! |
| 15:16.15 | paul_boddie | OK, well, I'll ask it anyway and see if anyone has any opinion. It's actually about that USB/IP kernel module I mentioned before. That module appears to obtain a socket from a process using its file descriptor table, and I've been trying to obtain a usable "struct file" instead using fget, in order to use it with a tty character device file. |
| 15:20.24 | *** join/#qi-hardware lekernel_ (~lekernel@199.254.238.201) |
| 15:21.27 | paul_boddie | So, is it possible to obtain a usable "struct file" and use it to write to a character device within the kernel using, say, vfs_write? I do the set_fs magic but still get EFAULT. |
| 15:28.54 | *** join/#qi-hardware lekernel_ (~lekernel@g231251063.adsl.alicedsl.de) |
| 15:31.43 | larsc | paul_boddie: yes ;) |
| 15:33.33 | kyak | mth: jz-3.6 boots with Nanonote :) |
| 15:34.32 | mth | does the beeper still work? |
| 15:36.12 | paul_boddie | It's weird because I do fget, which should give me the file object that I need to actually write something, and I do the set_fs(KERNEL_DS) stuff to stop the address validation, but I start to wonder whether there are memory allocation issues that I haven't thought about, even though the socket-based stuff appears to use stack-allocated memory and synchronous I/O. |
| 15:36.38 | kyak | the beeper doesn't work, but i didn't modify the board.c |
| 15:37.04 | larsc | kyak: it should work without modifing it |
| 15:37.05 | kyak | something must be wrong with config options.. proc is not mounted |
| 15:37.38 | larsc | kyak: your init is probably not /etc/preinit |
| 15:37.49 | paul_boddie | And it's quite hard to find a discussion about this on the Internet because everyone is wailing "Don't open files in the kernel!" (I'm not) and pointing to a 2005 article about doing bad things in the kernel. |
| 15:38.00 | viric | I never understood the openwrt game on the 'init' path |
| 15:38.10 | larsc | paul_boddie: what exactly are you trying to do? |
| 15:38.46 | kyak | larsc: should i patch the kernel to use /etc/preinit or modify the cmdline in uboot? |
| 15:38.57 | larsc | kyak: both is possible |
| 15:39.02 | larsc | and should work |
| 15:39.15 | larsc | if you have serial access to uboot it should be faster |
| 15:39.22 | viric | why are the openwrt people not using the usual init paths? |
| 15:39.39 | larsc | good question |
| 15:39.55 | viric | I find it annoying :) |
| 15:42.05 | paul_boddie | Doesn't the stock NanoNote bootloader specify /etc/preinit? |
| 15:42.44 | kyak | larsc: fixed the problem with init, still it doesn't beep |
| 15:43.24 | kyak | paul_boddie: interestingly, not. I guess it relies on the kernel patch |
| 15:44.05 | paul_boddie | kyak: I couldn't remember where the setting got applied, but I found that the Debian userland obviously wouldn't work without some preinit "glue". |
| 15:51.49 | kyak | larsc: after fixing init stuff, i don't need CONFIG_DEVTMPFS :) |
| 15:52.13 | *** join/#qi-hardware emeb (~ericb@ip72-201-79-123.ph.ph.cox.net) |
| 15:52.55 | larsc | kyak: what's the output of /sys/bus/platform/{devices,drivers}? |
| 15:54.03 | larsc | Is CONFIG_PWM_BEEPER enabled in your config? |
| 15:54.18 | kyak | http://dpaste.org/w4o0y/ |
| 15:54.39 | kyak | grep CONFIG_PWM_BEEPER .config returns nothing |
| 15:54.50 | larsc | there is the problem |
| 15:54.58 | kyak | btw, ash doesn't like curly brackets :) |
| 15:55.23 | larsc | I figured you'd be smart enough to decode what I meant ;) |
| 15:56.01 | kyak | now i'm smarter than ash, good --) |
| 15:56.14 | kyak | ok.. so where is CONFIG_PWM_BEEPER gone? |
| 15:56.23 | larsc | try to edit drivers/input/misc/Kconfig and replace HAVE_PWM with PWM |
| 15:59.25 | larsc | mth: did you put the PWM patches in jz-3.6? |
| 15:59.32 | kyak | now i have CONFIG_INPUT_PWM_BEEPER=y. Is this what we are lookign for? |
| 15:59.50 | larsc | yes |
| 16:00.13 | viric | input? |
| 16:00.46 | larsc | yes |
| 16:01.27 | kyak | yep, it beeps now |
| 16:01.55 | larsc | input is really a misnomer these days. it's more about hid, so it supports both hid input and output |
| 16:02.12 | larsc | but well you don't simply rename a subsystem |
| 16:02.53 | larsc | kyak: good |
| 16:04.41 | mth | larsc: yes, I added the commits that didn't make it into 3.6 |
| 16:06.03 | larsc | ok |
| 16:06.49 | larsc | the one modifying drivers/input/misc/Kconfig is missing ;) |
| 16:07.24 | larsc | https://patchwork.kernel.org/patch/1544851/ |
| 16:18.17 | paul_boddie | larsc: I'm trying to get the usbip driver to talk over a serial device instead of a socket. |
| 16:19.25 | larsc | so you want to do usb over serial? |
| 16:24.04 | paul_boddie | Well, if it works over TCP/IP, why not over something behaving like a serial line? |
| 16:24.23 | mth | larsc: we don't have "IS_ENABLED(CONFIG_PWM)" in include/linux/pwm.h, so perhaps another patch is missing too? |
| 16:24.37 | paul_boddie | I actually thought the modifications would be relatively trivial, but I think I must have underestimated the Linux kernel's capacity to infuriate again. |
| 16:29.57 | larsc | paul_boddie: I'd expect it to work to. where do you get the fd from, do you pass it in from userspace? |
| 16:32.25 | larsc | mth: https://patchwork.kernel.org/patch/1441841/ |
| 16:37.06 | qi-bot | [commit] Tushar Behera: pwm: Fix compilation error when CONFIG_PWM is not defined (jz-3.6) http://qi-hw.com/p/qi-kernel/7220711 |
| 16:37.06 | qi-bot | [commit] Thierry Reding: pwm: Get rid of HAVE_PWM (jz-3.6) http://qi-hw.com/p/qi-kernel/90bf225 |
| 16:38.31 | paul_boddie | So, the usbip driver does a scanf on some integers written to a sysfs file. It then does an fget to get a "struct file" and then tests for a socket before calling SOCKET_I on the inode of the file. |
| 16:38.32 | paul_boddie | http://lxr.free-electrons.com/source/drivers/staging/usbip/usbip_common.c?v=3.5#L399 |
| 16:40.11 | larsc | that's kind of crazy |
| 16:41.11 | qi-bot | [commit] Maarten ter Huurne: MIPS: JZ4740: qi_lb60: Update defconfig (jz-3.6) http://qi-hw.com/p/qi-kernel/6395c34 |
| 16:41.22 | paul_boddie | I can sort of understand the motivation for it, though. |
| 16:42.40 | larsc | but sysfs files are stateless while a fd is stateful |
| 16:43.36 | larsc | or does it lookup the socket the moment the sysfs file is written? |
| 16:44.26 | paul_boddie | http://lxr.free-electrons.com/source/drivers/staging/usbip/vhci_sysfs.c?v=3.5#L169 |
| 16:45.29 | paul_boddie | On being written. The socket is opened in user space and the sysfs file/attribute is used to tell the kernel/module to take over. |
| 16:45.48 | larsc | ok, i guess that could work, but still. and you kept the same behaviour and just skipped the socket part |
| 16:48.03 | paul_boddie | Yes, I use fget but don't do any "conversion" to a socket. I suspect that there's something in the socket handling that allows this module to use kernel-allocated memory because there's no set_fs stuff in that module at all. |
| 16:48.43 | paul_boddie | I'm open to better suggestions about how this could be done, but I understand how it probably came about. |
| 16:48.54 | larsc | I don't think you need set_fs if you are already in kernel space |
| 16:49.28 | larsc | -EFAULT would suggest that you don't have premission to read the memory area you want to write to the console |
| 16:49.34 | paul_boddie | There's precious little (coherent) documentation about this, at least on the Internet. |
| 16:50.01 | larsc | can you paste your diff somewhere? |
| 16:50.24 | paul_boddie | Yes, in fact before getting EFAULT, I found that I was actually causing an "oops" or backtrace, but I think that was because I was using __user pointers directly with kernel addresses. |
| 16:50.48 | paul_boddie | I'll try and paste a diff later on. Currently, I'm not where my diff actually is. :-) |
| 16:51.44 | larsc | __user is just a hint for the compiler |
| 16:52.23 | paul_boddie | I'm either missing something super-obvious or there's a more serious issue. |
| 16:57.17 | paul_boddie | What I found was that the vfs functions all seem to need __user pointers at some level, but in this case all work is being done in the kernel and there's no user space client. |
| 16:57.40 | *** join/#qi-hardware pcercuei (~paul@190.162.199.66) |
| 16:58.01 | paul_boddie | Maybe we should port the HURD to the NanoNote. :-) |
| 16:58.16 | *** join/#qi-hardware kyak (~kyak@95-26-121-16.broadband.corbina.ru) |
| 16:58.16 | *** join/#qi-hardware kyak (~kyak@unaffiliated/kyak) |
| 17:03.15 | DocScrutinizer05 | whitequark: (jolla) they don't get the catch to hire me - what can I say ;-P |
| 17:03.55 | DocScrutinizer05 | prolly they'll buy some cheap chinese phone and rebrand it ;-) |
| 17:05.47 | paul_boddie | Don't reveal Nokia's eventual business model to us! ;-) |
| 17:12.47 | *** join/#qi-hardware heberth (~heberth@190.255.11.196) |
| 17:24.54 | *** join/#qi-hardware freakazoid0223 (~matt@pool-71-246-26-142.phlapa.fios.verizon.net) |
| 17:27.05 | *** join/#qi-hardware wolfspraul (~wolfsprau@222.129.23.76) |
| 17:55.21 | paul_boddie | is back with his patches later on. |
| 17:55.28 | *** part/#qi-hardware paul_boddie (~paulbodd@hfaistos.uio.no) |
| 18:03.16 | *** join/#qi-hardware wej (~j@nl3x.mullvad.net) |
| 18:25.06 | *** join/#qi-hardware jluis (~jluis@195.Red-83-38-88.dynamicIP.rima-tde.net) |
| 19:03.06 | *** join/#qi-hardware lekernel_ (~lekernel@85.179.165.83) |
| 19:05.05 | *** part/#qi-hardware Freemor (~Freemor@ec2-174-129-226-140.compute-1.amazonaws.com) |
| 19:12.10 | *** join/#qi-hardware LunaVorax (~LunaVorax@ABordeaux-651-1-182-38.w109-214.abo.wanadoo.fr) |
| 19:57.57 | *** join/#qi-hardware kristianpaul (~kristianp@cl-50.mia-01.us.sixxs.net) |
| 19:57.57 | *** join/#qi-hardware kristianpaul (~kristianp@unaffiliated/kristianpaul) |
| 20:50.35 | *** join/#qi-hardware kristianpaul (~kristianp@unaffiliated/kristianpaul) |
| 21:03.11 | *** join/#qi-hardware jekhor (~jek@46.53.195.142) |
| 21:25.19 | *** join/#qi-hardware paul_boddie (~paulb@cm-84.215.225.75.getinternet.no) |
| 21:26.30 | paul_boddie | larsc: Finally uploaded the diff: http://en.qi-hardware.com/wiki/File:Usbip-socket-to-file.diff.txt |
| 21:32.00 | *** join/#qi-hardware kristianpaul (~kristianp@unaffiliated/kristianpaul) |
| 21:44.15 | *** join/#qi-hardware heberth (~heberth@190.6.162.167) |
| 21:44.57 | larsc | paul_boddie: looks pretty much ok to me |
| 21:45.25 | paul_boddie | There must be something really stupidly obvious I'm doing wrong, but I don't see it! |
| 21:45.29 | *** join/#qi-hardware Hoolxi (~Openfree@120.204.177.230) |
| 21:46.42 | paul_boddie | Maybe I should open a normal file and pass a descriptor for that. I did try opening the device file in the kernel itself, but that didn't change anything. |
| 22:21.43 | *** join/#qi-hardware LunaVorax_ (~LunaVorax@ABordeaux-651-1-143-44.w90-38.abo.wanadoo.fr) |
| 22:25.55 | paul_boddie | Just tried with a normal file, and that didn't fault, so maybe something is happening in the driver behind the serial device. |
| 23:08.33 | paul_boddie | Actually, I think a normal file doesn't seem to exercise the writing code, but it does attempt a read, gets zero bytes, and then the driver pronounces it a "disconnect". |
| 23:12.59 | paul_boddie | will look at this later. |
| 23:13.16 | *** part/#qi-hardware paul_boddie (~paulb@cm-84.215.225.75.getinternet.no) |
| 23:30.35 | *** join/#qi-hardware guanucoluis (~luis@2001:470:e450:0:225:56ff:fea1:2064) |
| 23:41.41 | pabs3 | whitequark: in reply to your question about Jolla. they do not seem interesting in any way |